cnid_metad — start cnid_dbd daemons on request
cnid_metad waits for requests from afpd to start up instances of the cnid_dbd daemon. It keeps track of the status of a cnid_dbd instance once started and will restart it if necessary. cnid_metad is normally started at boot time from /etc/rc or equivalent and runs until shutdown. afpd needs to be configured with the -cnidserver option in afpd.conf in order to access cnid_metad. It is possible to run more than one instance of cnid_metad on the same machine if different values for the interface and/or port are specified with the -h and -p options.
cnid_metad will remain in the foreground and will also leave the standard input, standard output and standard error file descriptors open. Useful for debugging.
Use hostname as the network interface for requests as opposed to the default localhost .
Use port as the port number for reqests. Default is 4700.
Switch to the userid of user before serving requests. This userid will be inherited by all cnid_dbd daemon processes started.
Switch to the groupid of group before serving requests. This groupid will be inherited by all cnid_dbd daemon processes started. Both user and group must be specified as strings.
Use cnid_dbd pathname as the pathname of the executeable of the cnid_dbd daemon. The default is /usr/sbin/cnid_dbd.
The number of cnid_dbd subprocecesses is currently limited to 128. This restriction will be lifted in the future.
cnid_metad does not block or catch any signals apart from SIGPIPE. It will therefore exit on most signals received. This will also cause all instances of cnid_dbd's started by that cnid_metad to exit gracefully. Since state about and IPC access to the subprocesses is only maintained in memory by cnid_metad this is desired behaviour. As soon as cnid_metad is restarted afpd processes will transparently reconnect.