[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: TUX processes WON"T DIE! : Are we running windows Danny?

Nicholas, your problem is that tux hangs on YOUR machine, and after that you
cannot stop it with the standard "tux stop"
i have experienced that in prevous version (read the 100% cpu bug) threads,
which seems to be solved now.

and as to stopping tux, the rc file simply runs

/usr/sbin/tux --stop

nothing platform specific there

----- Original Message -----
From: "Nicholas Tang" <ntang@mail.communityconnect.com>
To: <tux-list@redhat.com>
Sent: Tuesday, June 18, 2002 7:30 PM
Subject: Re: TUX processes WON"T DIE! : Are we running windows Danny?

> I posted last week about a similar (or perhaps the same) problem: even
> using "tux stop" won't stop tux, and the only way to manage it is to do
> a "reboot -f" (i.e. a forced reboot) which is an ugly way to stop or
> restart a webserver.
> I've also found that tux freezes up periodically, and requires that the
> entire system be rebooted.
> Nicholas
> On Tue, 2002-06-18 at 12:53, Alex Kramarov wrote:
> > You are messing with kernel processes - it's like trying to kill the
> > journal processes. I also cannot kill tux worker threads on my machine,
> > although this is the first time i wanted to do that - just to check .
> > use /etc/init.d/tux start/stop - this is the only way to control tux, as
> > as i know.
> >
> > > I am experimenting with tux on a 'linux-from-scratch' build.
> > >
> > > I don't expect everything to work right-away
> > > ( TUX is very redhat-specific, but I've hacked it into working on
> > Slackware 8.0 ) but I am not sure I want to bother continuing because
> > processes
> > > WON'T DIE.
> > >
> > > Once I've started TUX, figured out it isn't working, and made
> > ( my standard development cycle ) I try to restart or kill TUX, and it
> > DIE, won't HUP, will not GO AWAY unless I restart the machine.  If I
> > this kind of instability I'd run Windows.  These processes are not
> > ( according to ps ) but kill -anything has NO effect on them.
> > > '/proc/PID/status' says 'disk-sleep'.
> > > Is there a fix for this?
> > > I won't run anything that doesn't go away when root says "die."

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index] []