niload(8) [opendarwin man page]
NILOAD(8) System Manager's Manual NILOAD(8) NAME
niload - load text or flat-file-format data into NetInfo SYNOPSIS
niload [ -v ] [ -d ] [ -m ] [ -p ] [ -t ] { -r directory | format } domain DESCRIPTION
niload loads information from standard input into the given NetInfo domain. If format is specified, the input is interpreted according to the flat-file file format of the same name. The allowed values for format are aliases, bootparams, bootptab, exports, fstab, group, hosts, networks, passwd, printcap, protocols, rpc, and services. If -r directory is specified instead of a flat-file file format, the input is interpreted as "raw" NetInfo data, as generated by nidump -r, and loaded into directory. Note that this operation will delete and replace the entire NetInfo subtree at the specified directory. Any existing records in this subtree will be lost. niload overwrites entries in the existing directory with those given in the input. Entries that are in the directory aren't deleted if they don't exist in the input, unless the -d option is specified. niload must be run as superuser on the master NetInfo server for the given domain, unless one specifies the -p option, which allows one to run from anywhere in the network. OPTIONS
-v Verbose. Prints details of records as they are updated (flat-file formats only). -d Delete entries which are in the directory, but not in the input. -m Merge properties and values. Existing properties will be preserved in the database if they are not present in the input. For exam- ple, if a user record has a "picture" property, loading a passwd-format record for this user will preserve the property. Property values are also merged. -p Prompt for the root password of the given domain so that one can run from other locations in the network besides the master. -t Interpret the domain as a tagged domain. For example, "trotter/network" refers to the database tagged "network" on the machine "trotter". The machine name can be an actual name or an IP address. -r Load entries in "raw" format, as generated by nidump -r. The first argument should be the path of a NetInfo directory into which the information is loaded. Since the input often specifies properties (including "name") at its topmost level, the directory you specify may be renamed as a result of this operation. If the directory you specify does not exist, it will be created. EXAMPLES
"niload passwd . < /etc/passwd" loads the local /etc/passwd file into the local NetInfo database. "niload -d -r /locations ." replaces the contents of /locations in the local domain with input given in nidump "raw" format. SEE ALSO
nidump(8), niutil(8), netinfo(5), aliases(5), bootparams(5), bootptab(5), exports(5), fstab(5), group(5), hosts(5), networks(5), passwd(5), printcap(5), protocols(5), rpc(5), services(5) Apple Computer, Inc. December 22, 1992 NILOAD(8)
Check Out this Related Man Page
NETINFO(5) AFS File Reference NETINFO(5) NAME
NetInfo - Defines machine interfaces to register with AFS servers DESCRIPTION
There are two NetInfo files, one for an AFS client and one for an AFS File Server or database server. The AFS client NetInfo file specifies the IP addresses that the client should register with the File Servers it connects to. The server NetInfo file specifies what interfaces should be registered with AFS Database Servers or used to talk to other database servers. Client NetInfo The client NetInfo file lists the IP addresses of one or more of the local machine's network interfaces. If it exists in the /etc/openafs directory when the Cache Manager initializes, the Cache Manager uses its contents as the basis for a list of local interfaces. Otherwise, the Cache Manager uses the list of interfaces configured with the operating system. It then removes from the list any addresses that appear in the /etc/openafs/NetRestrict file, if it exists. The Cache Manager records the resulting list in kernel memory. The first time it establishes a connection to a File Server, it registers the list with the File Server. The File Server uses the addresses when it initiates a remote procedure call (RPC) to the Cache Manager (as opposed to responding to an RPC sent by the Cache Manager). There are two common circumstances in which the File Server initiates RPCs: when it breaks callbacks and when it pings the client machine to verify that the Cache Manager is still accessible. The NetInfo file is in ASCII format. One of the machine's IP addresses appears on each line, in dotted decimal format. The File Server initially uses the address that appears first in the list. The order of the remaining addresses is not significant: if an RPC to the first interface fails, the File Server simultaneously sends RPCs to all of the other interfaces in the list. Whichever interface replies first is the one to which the File Server then sends pings and RPCs to break callbacks. To prohibit the Cache Manager absolutely from using one or more addresses, list them in the NetRestrict file. To display the addresses the Cache Manager is currently registering with File Servers, use the fs getclientaddrs command. To replace the current list of interfaces with a new one between reboots of the client machine, use the fs setclientaddrs command. Server NetInfo The server NetInfo file, if present in the /var/lib/openafs/local directory, defines the following: o On a file server machine, the local interfaces that the File Server (fileserver process) can register in the Volume Location Database (VLDB) at initialization time. o On a database server machine, the local interfaces that the Ubik database synchronization library uses when communicating with the database server processes running on other database server machines. If the NetInfo file exists when the File Server initializes, the File Server uses its contents as the basis for a list of interfaces to register in the VLDB. Otherwise, it uses the list of network interfaces configured with the operating system. It then removes from the list any addresses that appear in the /var/lib/openafs/local/NetRestrict file, if it exists. The File Server records the resulting list in the /var/lib/openafs/local/sysid file and registers the interfaces in the VLDB. The database server processes use a similar procedure when initializing, to determine which interfaces to use for communication with the peer processes on other database machines in the cell. The NetInfo file is in ASCII format. One of the machine's IP addresses appears on each line, in dotted decimal format. The order of the addresses is not significant. Optionally, the File Server can be forced to use an IP address that does not belong to one of the server interfaces. To do this, add a line to the NetInfo file with the IP address prefixed with "f" and a space. This is useful when the File Server is on the internal side of a NAT firewall. To display the File Server interface addresses registered in the VLDB, use the vos listaddrs command. EXAMPLES
If the File Server is on the internal side of a NAT firewall, where it serves internal clients using the IP address 192.168.1.123 and external clients using the IP address 10.1.1.321, then the NetInfo file should contain the following: 192.168.1.123 f 10.1.1.321 SEE ALSO
NetRestrict(5), sysid(5), vldb.DB0(5), fileserver(8), fs_getclientaddrs(1), fs_setclientaddrs(1), vos_listaddrs(1) COPYRIGHT
IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved. This documentation is covered by the IBM Public License Version 1.0. It was converted from HTML to POD by software written by Chas Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell. OpenAFS 2012-03-26 NETINFO(5)