On Mon, 15 Nov 2010 23:29:01 +0100 Nicolas François <[email protected]> wrote:
> > I did not reproduce this. > Could you check if there are some information logged in /var/log/syslog or > /var/log/auth.log. > > It might be that login is more strict regarding having an entry in UTMP > before it is started, which might not be the case with the autologin > method you are using. > > There might also be output indicating why login failed. You may have to > block your script at the end (e.g. with 'read') or you can redirect > login's stdout and stderr. > I can't get any output at all. It seems the login program does not even execute. For example, after logging in as root using an older version (4.1.3.1) of login, when I manually execute "login -f <user>" with the newer login, the command hangs. There is no response and I need to do Ctl-C to regain control. Using the older login (4.1.3.1) allows the command "login -f <user>" to execute normally. I have been searching and also cannot find any reports that reproduce this problem. It could be just a peculiarity of my configuration somehow. Until I can do some more debugging, I'll just use login from shadow-4.1.3.1. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
