mgetty + glibc-2 : Bad entry in /var/run/utmp

• Messages sorted by:[ date ][ thread ][ subject ][ author ]

>>>>> Andreas Steffan writes:

 > Hi
 > I installed glibc-2 as the default C-library (--prefix=/usr), and moved
 > libc with it's header files to nonstandard paths, so I can still use it
 > if I want.
 > I noticed, that the format of the utmp-entries changed and therefore
 > recompiled everything that uses /var/run/utmp
 > (sysvinit,util-linux-2.6,pppd ...) with glibc-2 to avoid /var/run/utmp
 > getting messed up.
 > I also noticed, that the latest mgetty ( 1.1.6-May05 ) linked against
 > glibc works, but still screws up /var/run/utmp.
 > Im sure that it is mgetty screwing up /var/run/utmp since innwatch (from
 > inn-1.5.1) immediatly starts complaining about /var/run/utmp after
 > someone successfully logs on via dialup.
I'm not sure about mgetty being the problem. mgetty uses AFAIK
properly utmp (see file utmp.c).
Which program is started by mgetty if someone logs into your machine?
login might also mess up utmp and needs to be recompiled.

On my machine (running mgetty 1.1.1 and glibc2) I don't have utmp
problems anymore.

Andreas
-- 
 Andreas Jaeger aj@arthur.rhein-neckar.de jaeger@informatik.uni-kl.de
 Altenwoogstr. 31 67655 Kaiserslautern, Germany
 Phone +49 631 3403051 Fax/Modem +49 631 3403052
 http://www.student.uni-kl.de/~ajaeger/
.