| Main Archive Page > Month Archives > engarde-users archives |
Re: Problem with xinetd starting up
From: Bryon Hargis <b_hargis_at_nospam>Date: Wed May 30 2001 - 21:09:49 GMT
To: engarde-users@engardelinux.org
Yes, it is on in 3/4/5 and there is an entry in that log saying it succeded,
as it also shows on the screen. This is the stock xinetd.
----Original Message Follows----
From: "Ryan W. Maple" <ryan@guardiandigital.com>
Reply-To: engarde-users@engardelinux.org
To: engarde-users@engardelinux.org
Subject: Re: Problem with xinetd starting up
Date: Wed, 30 May 2001 16:52:31 -0400 (EDT)
Byron,
After you reboot, do you see anything in /var/log/boot.log saying xinetd even tried to startup?
Do a /sbin/chkconfig --list and make sure that xinetd has "3:on" and not "3:off".
Also, is this the stock xinetd or the one in /pub/people/ryan?
-r
+-- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --+ Ryan W. Maple "Finality is A Good Thing." -- Dave Wreski Guardian Digital, Inc. ryan@guardiandigital.com +-- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --+
On Wed, 30 May 2001, Bryon Hargis wrote:
> Ok, heres the deal. I added xinetd using
>
> chkconfig --add xinetd
>
> so that it would start automatically when it loaded
>
> This started up xinetd fine for a while, but then I messed with tripwire.
> At that point, my webmail stopped working. After hours of work, I found
> that even though it said it was succesful in startup, my webmail will not
> work unless I go in after everything has started up, and type
>
> /etc/init.d/xinetd restart
>
> At that point, webmail will work fine. I have tried removing xinetd from
> the startup, rebooting without it, then adding it, then rebooting again
to
> see if adding it again after being bootup once without it would fix
> something. It did not. TO get webmail to work, I have to manually
restart
> xinetd after the computer boots up, even though it says its already
running.
> All I can think of, is its starting before something else that it wants
to
> have already running. Is there a way to push it to the end of the
startup
> sequence. Right now it happens in the middle of runlevel 3. Also, this
> problem only occurs in secure mode, in standard mode, it works fine after
> booting up, with no problems.
To unsubscribe email engarde-users-request@engardelinux.org with "unsubscribe" in the subject of the message. _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com
To unsubscribe email engarde-users-request@engardelinux.org with "unsubscribe" in the subject of the message.