Note: This article pertains to Mac OS X Server versions 1.x, which were released prior to May 2001.
AppleFileServer runs over either TCP or AppleTalk and requires that TCP and/or AppleTalk be configured on the system.
The processes that show AppleFileServer is active are AppleFileServer and AdminWebServer.
AppleFileServer runs from a PIPE out of the AdminWebServer server (an HTTP server) and once running shows up in a process:
ps ax |grep AppleF
632 ? I 0:00 AppleFileServer /tmp/afpserver_PIPE
639 ? S 0:00 AppleFileServer /tmp/afpserver_PIPE
AdminWebServer appears in the process list as well:
ps ax |grep Admin
557 ? S 0:00 /usr/libexec/AdminWebServer -f
/System/Library/RemoteAdminServer/Configuration/apache.conf
559 ? I 0:00 /usr/libexec/AdminWebServer -f
/System/Library/RemoteAdminServer/Configuration/apache.conf
560 ? I 0:00 /usr/libexec/AdminWebServer -f
/System/Library/RemoteAdminServer/Configuration/apache.conf
566 ? I 0:00 /System/Library/RemoteAdminServer/FastCGI/RemoteAdminServer
Notice that the final process listed is the FastCGI which executes the remote administration of the AppleFileServer.
Remember that in the process viewer, the AdminWebServer processes show up as 'apache' EXACTLY like the HTTP server that is serving files on port 80.