Switch to SpeakEasy.net DSL

The Modular Manual Browser

Home Page
Manual: (OSF1-V5.1-alpha)
Apropos / Subsearch:
optional field

makedbm(8)							   makedbm(8)


  makedbm - Makes a Network Information	Service	(NIS) dbm file


  /var/yp/makedbm [-i yp_input_file] [-s yp_secure_name] [-a method] [-o
  yp_output_name] [-d yp_domain_name] [-m yp_master_name] infile outfile

  /var/yp/makedbm [-u dbmfilename]


  -a method
      Specifies	that NIS maps are to be	stored in one of the following for-

      b	  btree	-- Recommended when creating and maintaining very large	maps.

      d	  dbm/ndbm -- For backward compatibility.  This	is the default.

      h	  hash -- A potentially	quicker	method for managing small maps.

  -i  Creates a	special	entry with the key yp_input_file.

  -s  Creates a	special	entry with the key yp_secure_file. This	causes the
      makedbm command to write a secure	map.  The key value ypserver looks
      for YP_SECURE.

  -o  Creates a	special	entry with the key yp_output_name.

  -d  Creates a	special	entry with the key yp_domain_name.

  -m  Creates a	special	entry with the key yp_master_name. If no master	host
      name is specified, yp_master_name	will be	set to the local host name.

  -u  Undoes a dbm file. That is, prints out a dbm file	one entry per line,
      with a single space separating keys from values.


  The makedbm command takes the	file specified by the argument infile and
  converts it to a single file or a pair of files in dbm(3), btree(3), or
  hash(3) format. The dbm(3) files are stored as outfile.pag and outfile.dir.
  The btree(3) files are stored	as outfile.btree. Each line of the input file
  is converted to a single dbm record. All characters up to the	first tab or
  space	form the key, and the rest of the line is defined as the key's asso-
  ciated data. If a line ends with a backslash (\), the	data for that record
  is continued onto the	next line. It is left for the Network Information
  Service (NIS)	clients	to interpret the number	sign (#); makedbm does not
  treat	it as a	comment	character.  The	infile parameter can be	a hyphen (-),
  in which case	makedbm	reads the standard input.

  The makedbm command is meant to be used in generating	database files for
  NIS. The makedbm command generates a special entry with the key
  yp_last_modified, which is the date of infile.


  You must use the same	database format	for each map in	a domain. In addi-
  tion,	a server serving multiple NIS domains must use the same	database for-
  mat for all domains.

  Although a Tru64 UNIX	NIS server that	takes advantage	of btree files will
  be able to store very	large maps, NIS	slave servers that lack	this feature
  might	have a much smaller limit on the number	of map entries they can	han-
  dle.	It may not be possible to distribute very large	maps from a Tru64
  UNIX NIS master server to a slave server that	lacks support for very large
  maps.	 NIS clients are not affected by these enhancements.


   1.  The following example shows how a combination of	commands can be	used
       to make the NIS dbm files passwd.byname.pag and passwd.byname.dir from
       the /etc/passwd file.  The percent sign (%) signifies the system
	    % awk 'BEGIN { FS =	":"; OFS = "\t"; }
	     { print $1, $0 }' /etc/passwd >> ptmp
	    % makedbm ptmp passwd.byname
	    % rm ptmp

       The awk command creates the file	ptmp which is in a form	usable by
       makedbm.	The makedbm command uses the ptmp file to create the database
       files. The rm command removes the ptmp file.

   2.  The following is	an example of the makedb command used with the btree
       format database routine to store	NIS maps.
	    makedbm -a b ...


  Commands: yppasswd(1), ypmake(8)

  Functions: btree(3), dbm(3), dbopen(3), hash(3), ndbm(3)