| 2012-10-26 19:17:10 |
Ryan Finnie |
description |
The console TTYs are not being logged to utmp/wtmp, which is normally what a getty is responsible for doing. In Finnix's case, bashlogin (a bash script itself) handles most of the getty functionality.
There doesn't appear to be a scriptable utility for manipulating utmp/wtmp. The utempter utility (libutempter0 package) comes close, but only seems to deal with utmp/wtmp for new PTYs. This utility could be forked and modified to deal with arbitrary TTYs. |
The console TTYs are not being logged to utmp/wtmp, which is normally what a getty is responsible for doing. In Finnix's case, bashlogin (a bash script itself) handles most of the getty functionality.
There doesn't appear to be a suitable scriptable utility for manipulating utmp/wtmp. runit provides a badly-named utmpset program, which is only responsible for clearing a utmp entry, not setting. The utempter utility (libutempter0 package) comes close, but only seems to deal with utmp/wtmp for new PTYs. This utility could be forked and modified to deal with arbitrary TTYs. |
|
