Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the '10.4: Force use of launchd for upgraded installs' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.4: Force use of launchd for upgraded installs
Authored by: SentientToad on May 16, '05 06:28:48AM
You can disable xinetd altogether by disabling its plist entry for launchd. The easiest way to do this is

sudo launchctl unload -w /System/Library/LaunchDaemons/org.xinetd.xinetd.plist
This adds

     <key>Disabled</key>
          <true/>
to the plist file as well as unloading xinetd.

Now launchd won't start it on system boot. To re-enable it,


sudo launchctl load -w /System/Library/LaunchDaemons/


[ Reply to This | # ]
Oops, typo ...
Authored by: SentientToad on May 16, '05 06:30:39AM
To re-enable type

sudo launchctl load -w /System/Library/LaunchDaemons/org.xinetd.xinetd.plist


[ Reply to This | # ]
10.4: Force use of launchd for upgraded installs
Authored by: johnts on May 16, '05 12:19:32PM

I just tried this. When I entered the command, the xinetd daemon did go away, but when I went to try and FTP into my system, i got an error. I turned off and back on FTP (and remote login) and was able to log in.

However. xinetd is running again. Entering the launchctl command now returns:

No such process

and yet ps -ax| grep xin shows:

474 ?? Ss 0:00.03 /usr/sbin/xinetd -pidfile /var/run/xinetd.pid

The .plist for xinetd does show the Disabled key is in there.



[ Reply to This | # ]
10.4: Force use of launchd for upgraded installs
Authored by: johnts on May 16, '05 12:22:44PM

Hm. Maybe I just misunderstood. When I stop the FTP or remote login service, xinetd does go away.

I guess xinetd is needed for those services, it's just not running all the time to control other services.



[ Reply to This | # ]
10.4: Force use of launchd for upgraded installs
Authored by: geohar on May 16, '05 01:25:45PM

For sure, but you _still_ need to remove the contents of /etc/xinetd.d/ in order that system prefs uses launchd, rather than xinetd. Simply disabling xinetd will not work.

Additionally, it's probably worth noting that xinetd will not run unless something is put into /etc/xinetd.d (launchd watches for this and launches it - beacause launchd is actually used to launch xinetd!!).

As xinetd doesn't run unless there's something in the directory for it to run on, it's probably worth leaving it 'enabled' in it's launchd plist - that way, if an installer puts something there, it'll run fine. The rest will still use launchd, because their /etc/xinetd.d/ entries will be missing.



[ Reply to This | # ]