> If SAK is killing *init* something else weird is going on, it has nothing to do
with where the X server is.
SAK kills *all* processes on tty1, including all daemons, including init.
Quote from kernel/Documentation/SAK.txt:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
On the PC keyboard, SAK kills all applications which have /dev/console opened. Unfortunately this includes a number of things which you don't actually want killed.
This is because these applications are incorrectly holding /dev/console open. Be sure to complain to your Linux distributor about this!
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> If SAK is killing *init* something else weird is going on, it has nothing to do
with where the X server is.
SAK kills *all* processes on tty1, including all daemons, including init.
Quote from kernel/ Documentation/ SAK.txt: =-=-=-= -=-=-=- =-=-=-= -=-=-=- =-=-=-= -=-=-=-
-=-=-=-
On the PC keyboard, SAK kills all applications which have /dev/console opened. Unfortunately this includes a number of things which you don't actually want killed.
This is because these applications are incorrectly holding /dev/console open. Be sure to complain to your Linux distributor about this! =-=-=-= -=-=-=- =-=-=-= -=-=-=- =-=-=-= -=-=-=-
-=-=-=-
[vlisivka@apollo 1]$ sudo fuser -v /dev/console
USER PID ACCESS COMMAND
root 1258 F.... rsyslogd
USER PID ACCESS COMMAND
/dev/console: root 1 F.... init
[vlisivka@apollo 1]$ sudo fuser -v /dev/tty1
/dev/tty1: root 1878 F.... Xorg
SAK on tty1 will kill Xorg and /sbin/init with rsyslogd.