Hello mysql mailing list readers, Secure Attention Key is supposed to kill all processes on current console. Usually init respawns new getty. This way I can be sure that login prompt I see is not mimicked by password collecting program. I like this idea a lot. I noticed that when I press Secure Attention Key on virtual console #1 on my Linux box, some daemons die horribly (SIGKILLed) (including mysqld) 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. My mysqld is started by this command: su mysql -c "/usr/sbin/mysqld --socket=/tmp/mysql.sock --skip-networking 2>&1 | logger &" Daemons dying upon SAK: syslogd mysqld top* logger* Daemons surviving SAK: klogd gpm dhcpcd * 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 &" Does anybody knows a way to write a helper script to detach misbehaving daemons from tty on startup? -- Best regards, VDA mailto:[EMAIL PROTECTED] --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
