diff options
author | Mattias Andrée <maandree@member.fsf.org> | 2015-12-19 15:34:50 +0100 |
---|---|---|
committer | Mattias Andrée <maandree@member.fsf.org> | 2015-12-19 15:34:50 +0100 |
commit | c9b2863e7e7331f381a587756a403cbb6b19e115 (patch) | |
tree | 9a69a654d02c31b036dd6da2ffd84072e79be054 /doc | |
parent | update news (diff) | |
download | sleeping-getty-c9b2863e7e7331f381a587756a403cbb6b19e115.tar.gz sleeping-getty-c9b2863e7e7331f381a587756a403cbb6b19e115.tar.bz2 sleeping-getty-c9b2863e7e7331f381a587756a403cbb6b19e115.tar.xz |
doc: does not acquire the tty
Signed-off-by: Mattias Andrée <maandree@member.fsf.org>
Diffstat (limited to 'doc')
-rw-r--r-- | doc/info/chap/invoking.texinfo | 16 | ||||
-rw-r--r-- | doc/man/sleeping-getty.8 | 25 |
2 files changed, 35 insertions, 6 deletions
diff --git a/doc/info/chap/invoking.texinfo b/doc/info/chap/invoking.texinfo index f0a51ec..008c883 100644 --- a/doc/info/chap/invoking.texinfo +++ b/doc/info/chap/invoking.texinfo @@ -37,7 +37,17 @@ which is Gates of Tartaros on @file{/dev/tty15} with the environment variable @env{TERM} set to @command{linux}. -Note that sleeping-getty works on VT:s, not TTY:s. -It cannot wait for a serial console to become, -active, only virtual terminals. +Note that @command{sleeping-getty} works on +VT:s, not TTY:s. It cannot wait for a serial +console to become, active, only virtual terminals. + +Also note, @command{sleeping-getty} does not acquire +the TTY. That would be a waste of CPU cycles. This +means, if naïvely used, that if you start your +computer, log in on @file{tty1}, and start @command{X}, +and have @command{startx} configured to start @command{X} +on the next available VT. @command{X} will start on +VT@tie{}2. This is probably not want you want. Instead +you should edit startx to ensure that a VT lower than +a preferred number (customarily 7) will not be used. diff --git a/doc/man/sleeping-getty.8 b/doc/man/sleeping-getty.8 index a40772c..f20ed92 100644 --- a/doc/man/sleeping-getty.8 +++ b/doc/man/sleeping-getty.8 @@ -24,10 +24,29 @@ works on VT:s, not TTY:s. It cannot wait for a serial console to become, active, only virtual terminals. .SH EXAMPLE .nf -/sbin/\fBsleeping-getty\fP \fI15\fP /sbin/got tty\fI15\fP TERM=linux -/sbin/\fBsleeping-getty\fP \fI16\fP /sbin/got tty\fI16\fP TERM=linux -/sbin/\fBsleeping-getty\fP \fI20\fP /sbin/agetty -8 -s 38400 tty\fI20\fP linux +/sbin/\fBsleeping\-getty\fP \fI15\fP /sbin/got tty\fI15\fP TERM=linux +/sbin/\fBsleeping\-getty\fP \fI16\fP /sbin/got tty\fI16\fP TERM=linux +/sbin/\fBsleeping\-getty\fP \fI20\fP /sbin/agetty -8 -s 38400 tty\fI20\fP linux .fi +.SH NOTES +.B sleeping\-getty +does not acquire the TTY. That would be a waste of CPU cycles. +This means, if naïvely used, that if you start your computer, +log in on +.BR tty1 , +and start +.BR X , +and have +.B startx +configured to start +.B X +on the next available VT. +.B X +will start on VT\ 2. This is probably not want you want. +Instead you should edit +.B startx +to ensure that a VT lower than a preferred number +(customarily 7) will not be used. .SH RATIONALE It is nice to have a score or two of TTY:s available. However, starting them, can require some unnecessary CPU time and will |