Name

atinit - halt, start, or restart AppleTalk services

Synopsis

/usr/etc/appletalk/atinit action

Description

The atinit program manages startup and shutdown of FullPress AppleTalk services. It is normally invoked by the server's startup scripts (see the SYSTEM ADMINISTRATION HINTS section for details) at system boot time.

The action argument may be any one of the following:

halt

stops all AppleTalk servers running on the UNIX system.

start

starts all the servers and commands listed in /usr/etc/appletalk/services (described below). The command atinit start is usually found in the system startup file. It should be run only at boot time, as it invokes initialization scripts as well as AppleTalk servers.

restart

halts all AppleTalk servers, and then starts them again without running initialization scripts or starting utilities that are not AppleTalk servers.

The action argument may also be specified in uppercase. Using atinit with no arguments results in an error message.

Whenever new AppleTalk services are added, the file /usr/etc/appletalk/services should be edited to include the full pathname of each added AppleTalk server and any arguments required when it is invoked. atinit will truncate the at_log file when the action is start (but not restart) to keep the log file from getting excessively large. The last log file is kept in at_log.old.

System Administration Hints

The system administrator must ensure that all FullPress based services, including third party applications, do not duplicate tasks performed by atinit. For example, the Name Binding Protocol Daemon nbpd(8) is controlled by atinit, and must not be managed by other initialization scripts or secondary references in the startup scripts.

After customizing the /usr/etc/appletalk/services file, test your configuration by starting, halting, and restarting AppleTalk services. Make sure each server is executed (the atinit program displays the name of each server as it is invoked). Once you have tested atinit from the command line, it is a good idea to review the system startup scripts to make sure AppleTalk services will be invoked at system boot time. On SGIs and SUNs running Solaris (SunOS 5.2 or later) they are in /etc/init.d, with symbolic links from /etc/rc2.d and /etc/rc0.d. For HP-UX 10.X the startup files are just like SGIs, except the top-level directory is /sbin. On SunOS (5.1 or earlier) AppleTalk is started from /etc/rc.local. On HP-UX 9.X , it's /etc/rc. If possible, reboot your system and observe that all AppleTalk services come up cleanly.

Files

/usr/etc/appletalk/services

list containing full pathnames of all AppleTalk daemons installed on the system. On SGIs and Solaris this file really lives in /usr/adm/appletalk, and there is only a symbolic link in /usr/etc/appletalk.

/usr/etc/appletalk

default location for AppleTalk server daemons

/usr/etc/appletalk/nbpd

name binding protocol daemon

/usr/etc/appletalk/epd

echo protocol daemon

/usr/adm/appletalk/nbpreg_pids

process numbers of locally registered AppleTalk services

See Also

rc(8) , nbpd(8) , epd(8) , atservers(1)

---