Note: This article pertains to Mac OS X Server versions 1.x, which were released prior to May 2001.
The startup process for the AppleFileServer begins with AdminWebServer. AdminWebServer is started at boot by inetd if the server is configured for AppleFileServer. The configuration is checked and AdminWebServer started with the script '/etc/startup/1600_AppleShare' which checks for the configuration in hostconfig as well as NetInfo.
cat /etc/startup/1600_AppleShare
#!/bin/sh
. /etc/rc.common
CheckForNetwork
if [ "${NETWORKUP}" = "-NO-" ]; then exit; fi
##
# Start the AFP Server
##
if [ "${AFPSERVER:=-NO-}" = "-YES-" ]; then
ConsoleMessage "Starting AppleShare server"
echo "Starting the AdminWebServer server"
/usr/sbin/AdminWebServerctl start
fi
If AppleFileServer's NetInfo property is set to start AppleFileServer at startup, the AdminWebServer server starts a single process of AppleFileServer (the "parent process") which does not serve files. That single parent process generates the second process (the "child process") which actually performs the file serving.
ps ax |grep AppleF
632 ? I 0:00 AppleFileServer /tmp/afpserver_PIPE
639 ? S 0:00 AppleFileServer /tmp/afpserver_PIPE
ps al 632
F UID PID PPID CP PRI BASE VSIZE RSIZE WCHAN STAT TT TIME COMMAND
4 0 632 1 0 10 10 6.19M 368K 0 I ? 0:00
AppleFileServer /tmp/afpserver_PIPE
ps al 639
F UID PID PPID CP PRI BASE VSIZE RSIZE WCHAN STAT TT TIME COMMAND
4 0 639 632 0 10 10 38.6M 2.05M 0 S ? 0:00
AppleFileServer /tmp/afpserver_PIPE
To administer the AppleFileServer, the AdminWebServer server is used again. Connecting to the server on port 311 (http://servername:311) connects to the AdminWebServer server (using a FastCGI). The settings added by AdminWebServer, along with other configuration settings for the AppleFileServer, are stored in the NetInfo database.