Additional info: If i comment out the lines for fgetty on tty1, tty2 and tty3 in /etc/inittab and uncomment the lines for getty in the same file, i can login on tty1,2,3 using nis account. So the problem is definitely with fgetty checkpassword. (Same behaviour is also observed for the ubuntu machine.)
Arvind > Package: fgetty > Version 0.6-4 > > My debian machine is a nis-client. When i try to login using a nis username > and > passwd on tty1, it says: > checkpassword: wrong password > This started happening recently after i did an 'apt-get dist-upgrade', so i > think this might be happening with the upgraded version of fgetty. Earlier i > could login using nis accounts on tty1. (And i have not installed a separate > checkpassword package, so it is the one shipped with fgetty) Note that on > xdm, i > can login using nis accounts, so it is not a nis configuration problem. Have > attached the contents of /etc/inittab below. > > Thanks and regards, > Arvind > > ps: am facing a similar problem on a ubuntu machine using fgetty > > ************************************************************************ > [EMAIL PROTECTED]:/auto/home2/arvind$ uname -a > Linux orion 2.6.17-2-686-bigmem #1 SMP Wed Sep 13 17:57:21 UTC 2006 i686 > GNU/Linux > > > [EMAIL PROTECTED]:/auto/home2/arvind$ cat /etc/inittab > > # /etc/inittab: init(8) configuration. > # $Id: inittab,v 1.91 2002/01/25 13:35:21 miquels Exp $ > > # The default runlevel. > id:5:initdefault: > > # Boot-time system configuration/initialization script. > # This is run first except when booting in emergency (-b) mode. > si::sysinit:/etc/init.d/rcS > > # What to do in single-user mode. > ~~:S:wait:/sbin/sulogin > > # /etc/init.d executes the S and K scripts upon change > # of runlevel. > # > # Runlevel 0 is halt. > # Runlevel 1 is single-user. > # Runlevels 2-5 are multi-user. > # Runlevel 6 is reboot. > > l0:0:wait:/etc/init.d/rc 0 > l1:1:wait:/etc/init.d/rc 1 > l2:2:wait:/etc/init.d/rc 2 > l3:3:wait:/etc/init.d/rc 3 > l4:4:wait:/etc/init.d/rc 4 > l5:5:wait:/etc/init.d/rc 5 > l6:6:wait:/etc/init.d/rc 6 > # Normally not reached, but fallthrough in case of emergency. > z6:6:respawn:/sbin/sulogin > > # What to do when CTRL-ALT-DEL is pressed. > ca:12345:ctrlaltdel:/sbin/shutdown -t1 -a -r now > > # Action on special keypress (ALT-UpArrow). > #kb::kbrequest:/bin/echo "Keyboard Request--edit /etc/inittab to let this > work." > > # What to do when the power fails/returns. > pf::powerwait:/etc/init.d/powerfail start > pn::powerfailnow:/etc/init.d/powerfail now > po::powerokwait:/etc/init.d/powerfail stop > > # /sbin/getty invocations for the runlevels. > # > # The "id" field MUST be the same as the last > # characters of the device (after "tty"). > # > # Format: > # <id>:<runlevels>:<action>:<process> > # > # Note that on most Debian systems tty7 is used by the X Window System, > # so if you want to add more getty's go ahead but skip tty7 if you run X. > # > #1:2345:respawn:/sbin/getty 38400 tty1 > #2:2345:respawn:/sbin/getty 38400 tty2 > #3:2345:respawn:/sbin/getty 38400 tty3 > #4:2345:respawn:/sbin/getty 38400 tty4 > #5:2345:respawn:/sbin/getty 38400 tty5 > #6:2345:respawn:/sbin/getty 38400 tty6 > 1:2345:respawn:/sbin/fgetty tty1 > 2:2345:respawn:/sbin/fgetty tty2 > 3:2345:respawn:/sbin/fgetty tty3 > #4:2345:respawn:/sbin/fgetty tty4 > #5:2345:respawn:/sbin/fgetty tty5 > #6:2345:respawn:/sbin/fgetty tty6 > > # Example how to put a getty on a serial line (for a terminal) > # > #T0:23:respawn:/sbin/getty -L ttyS0 9600 vt100 > #T1:23:respawn:/sbin/getty -L ttyS1 9600 vt100 > > # Example how to put a getty on a modem line. > # > #T3:23:respawn:/sbin/mgetty -x0 -s 57600 ttyS3 >
