If you upgraded from Panther then you’ll find a bunch of xinetd configuration scripts in /etc/xinetd.d/ but if you performed a clean installation, the directory will be empty. Tiger on a clean installation will use launchd to launch services while on an upgraded system, it will use xinetd. And the “service” script adapts itself accordingly. On my system (a clean install) - after I ran:
sudo service telnet start
There was no file called /etc/xinetd.d/telnet, but when I ran:
sudo launchctl list
The com.apple.telnetd daemon was running.
If you upgraded from Panther then you’ll find a bunch of xinetd configuration scripts in /etc/xinetd.d/ but if you performed a clean installation, the directory will be empty. Tiger on a clean installation will use launchd to launch services while on an upgraded system, it will use xinetd. And the “service” script adapts itself accordingly. On my system (a clean install) - after I ran:
sudo service telnet start
There was no file called /etc/xinetd.d/telnet, but when I ran:
sudo launchctl list
The com.apple.telnetd daemon was running.