From: Petr Baudis <pasky@pasky.ji.cz>
To: VDA <VDA@port.imtp.ilyichevsk.odessa.ua>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SAK killing daemons
Date: Wed, 15 Aug 2001 10:44:13 +0200 [thread overview]
Message-ID: <20010815104413.B13330@pasky.ji.cz> (raw)
In-Reply-To: <509636476.20010815112514@port.imtp.ilyichevsk.odessa.ua>
In-Reply-To: <509636476.20010815112514@port.imtp.ilyichevsk.odessa.ua>; from VDA@port.imtp.ilyichevsk.odessa.ua on Wed, Aug 15, 2001 at 11:25:14AM +0300
> I noticed that when I press SAK on virtual console #1
> on my Linux box, some daemons die horribly (SIGKILLed)
> and some are unaffected. This does not happen on other consoles.
>
> I suppose dying daemons did not detach fully from controlling tty. And
> since they were launched from virtual console #1 upon system startup,
> SAK killed them.
>
> Daemons dying upon SAK: syslogd mysqld top* logger*
> Daemons surviving SAK: klogd gpm dhcpcd inetd automount
>
> * these are not daemons, but I intend them to run continuously.
> logger directs mysqld output to syslog, and I keep top on console #10:
> su user0 -c "top s </dev/tty10 >/dev/tty10 &"
>
> Also I see '?' in TTY column in 'ps -AH e' output for all these
> daemons (both dying and surviving), so ps does not provide any hint...
>
> Does anybody knows a way to write a helper script to detach
> misbehaving daemons (or any normal process like top) from tty on startup?
> BTW, do syslogd needs fixing to be immune to SAK like klogd?
>
> Please CC me. I'm not on the list.
Try running the dying daemons by setsid utility (man 1 setsid, man 2 setsid),
it can help maybe. And try to modify that su -c command to:
su user0 -c "top s" </dev/tty/10 >/dev/tty10 2>/dev/tty10 &
that could help also.
--
Petr "Pasky" Baudis
. .
#define BITCOUNT(x) (((BX_(x)+(BX_(x)>>4)) & 0x0F0F0F0F) % 255)
#define BX_(x) ((x) - (((x)>>1)&0x77777777) \
- (((x)>>2)&0x33333333) \
- (((x)>>3)&0x11111111))
-- really weird C code to count the number of bits in a word
. .
My public PGP key is on: http://pasky.ji.cz/~pasky/pubkey.txt
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS d- s++:++ a--- C+++ UL++++$ 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------
next prev parent reply other threads:[~2001-08-15 8:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-15 8:25 VDA
2001-08-15 8:44 ` Petr Baudis [this message]
2001-08-15 11:47 ` VDA
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010815104413.B13330@pasky.ji.cz \
--to=pasky@pasky.ji.cz \
--cc=VDA@port.imtp.ilyichevsk.odessa.ua \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®