On Tue, 17 Dec 2002, Jason Gauthier wrote:
If you try to catch SIG_KILL, errno after signal(3) will be set to
EINVAL:
ERRORS
Signal() will fail and no action will take place if one of the following
occur:
[EINVAL] Sig is not a valid signal number.
[EINVAL] An attempt is made to ignore or supply a handler for
SIGKILL or SIGSTOP.
$ uname -sr
FreeBSD 4.6-STABLE
> You can catch SIGKILL, but you can't stop it or ignore it.
> Basically, has your crashing you might be able to get a little info out of
> it.
>
>
>
>
> > -----Original Message-----
> > From: Alexey V. Antipovsky [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, December 17, 2002 8:59 AM
> > To: [email protected]
> > Subject: Re: SIGKILL
> >
> >
> > signal(3):
> > [skip]
> > Except for the *SIGKILL* and SIGSTOP signals, the
> > signal() function allows for a signal to be caught, to be
> > ignored, or to
> > generate an interrupt.
> >
> >
> > On Tue, 17 Dec 2002, Tony Kuiper wrote:
> >
> > > Oh, my bad. Sorry, I completely misunderstood.
> > > Have you tried intercepting SIGKILL via a call (or calls) to
> > > signal(...)? It would be interesting to abort() there to
> > get a stack dump.
> > > (or possibly fork() and abort() the child to keep the main
> > running?) I
> > > personally wouldn't try to allow the mud to continue
> > running after it
> > > receives a SIGKILL, especially if the mud is running on
> > someone else's
> > > machine and they don't want it doing what it is! (CPU
> > usage, disk space,
> > > etc...) :-)
> > >
> > > Tony
> > >
> > > ----- Original Message -----
> > > From: "Chad Simmons" <[EMAIL PROTECTED]>
> > > To: <[email protected]>
> > > Sent: Monday, December 16, 2002 5:00 PM
> > > Subject: Re: SIGKILL
> > >
> > >
> > > >
> > > > --- Tony Kuiper <[EMAIL PROTECTED]> wrote:
> > > > > Try waiting until the mud is locked, then attach to
> > the process with
> > > > > gdb. This will allow you to see where it's "locking"
> > and diagnose the
> > > > > problem from there. :-)
> > > > >
> > > > > Tony
> > > >
> > > >
> > > > The probram isn't locked.. It's being killed.
> > > >
> > > >
> > > > > ----- Original Message -----
> > > > > From: "Adrian Allen" <[EMAIL PROTECTED]>
> > > > > To: <[email protected]>
> > > > > Sent: Monday, December 16, 2002 4:15 AM
> > > > > Subject: SIGKILL
> > > > >
> > > > >
> > > > > > Sometimes within less than a minute of booting the
> > mud it will just
> > > > > > stop running. I had no idea why until tonight I was
> > using gdb to
> > > > > > debug an area file and after I had the bugs worked
> > out it happened
> > > > > > I remember seeing this one other time using gdb and I
> > know its not
> > > > > > caused by the bug in my area file, having a door
> > reset to a null exit
> > > > > > and then fixing it wouldnt cause this. Its something
> > else. Any ideas?
> > > > > >
> > > > > >
> > > > > > Program terminated with signal SIGKILL, Killed.
> > > >
> > > >
> > > > The only people on a *nix system who can send a kill
> > signal to your
> > > program is
> > > > you, or the admin. So unless you have some automated
> > script that is
> > > killing it,
> > > > I'd say to consult with your admin and find out why your
> > program is being
> > > > killed.
> > > >
> > > > ~Kender
> > > >
> > > > =====
> > > > -----BEGIN GEEK CODE BLOCK-----
> > > > Version 3.1
> > > > GCS/L/C/O d-(+) s++: a-- C+++$>++++ UBLS++++$
> > > > P+++(--)$ L+++>++++ E--- W+>++$ N !o K? w(--) !O
> > > > M- !V PS+ PE(++) Y+ PGP->+ t+ 5 X+() R(+) tv+@
> > > > b++(+++) !DI+++ D G(-) e>+++$ h---() r+++ y+++
> > > > ------END GEEK CODE BLOCK------
> > > >
> > > > __________________________________________________
> > > > Do you Yahoo!?
> > > > Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
> > > > http://mailplus.yahoo.com
> > > >
> > > > --
> > > > ROM mailing list
> > > > [email protected]
> > > > http://www.rom.org/cgi-bin/mailman/listinfo/rom
> > > >
> > >
> > >
> >
> >
> > --
> > ROM mailing list
> > [email protected]
> > http://www.rom.org/cgi-bin/mailman/listinfo/rom
> >
>
