jmsellens@watmath.waterloo.edu (09/30/89)
From: John M Sellens <jmsellens> It was empty, dated Sept 13, seemed to be preventing logins. I went looking for the Sun login source. On orchid I looked at /usr/source/longnames/_bin/login/login.c and /usr/src/bin/login.c - both only allow root logins if /etc/nologins exists. Maybe /bin/login got rdisted from somewhere else and killed the one on lily that allowed us in? /etc/nologins should not have been empty in any case. But Guy says that lily would still let him in and so I don't understand why. I don't know which login we were actually using - it pointed to the longnames package. I couldn't find anything weird in the passwd file.
gamiddleton@watmath.waterloo.edu (09/30/89)
From: Guy Middleton <gamiddleton> We were running the one from 30 May, which is now in lily:/software/longnames/bin/login.old. There should be a /etc/nologins file. I don't know what changed. I copied login from orchid to lily (the copy that is there now), but that didn't help.
accwai@maytag.waterloo.edu (Andy Wai) (09/30/89)
In article <29606@watmath.waterloo.edu> jmsellens@watmath.waterloo.edu writes: >From: John M Sellens <jmsellens> > >[...] >Maybe /bin/login got rdisted from somewhere else and killed the one >on lily that allowed us in? /etc/nologins should not have been >empty in any case. But Guy says that lily would still let him in >and so I don't understand why. [...] I put the nologin back and lily no longer allow me to login. Presumably, something erase the old /bin/login. Anyway, taking out the /etc/nologin is bad news, so I took the source under orchid:/usr/source/longnames and put in the operator hack (4 lines of change). The new login is installed under /usr/bin as a real file, and the source is still on my lily account. This is only temporary. I'll do the real installation Monday. Andy
jmsellens@watdragon.waterloo.edu (John M. Sellens) (10/01/89)
In article <549@maytag.waterloo.edu> accwai@maytag.waterloo.edu (Andy Wai) writes: >I put the nologin back and lily no longer allow me to login. Presumably, >something erase the old /bin/login. Anyway, taking out the /etc/nologin >is bad news, so I took the source under orchid:/usr/source/longnames and >put in the operator hack (4 lines of change). It should probably print the /etc/nologin file whether or not it's about to let you in. I just tried it and I didn't see the contents of /etc/nologin. >The new login is installed under /usr/bin as a real file, and the source >is still on my lily account. This is only temporary. I'll do the real >installation Monday. So if the longnames package was distributed from orchid, then this new login program would get clobbered and stuck in vendor and we'd be back not being able to login. Bad idea.