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.
-- Best regards, VDA mailto:VDA@port.imtp.ilyichevsk.odessa.ua
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/