Hi once again,
We have recently turned on the /var/adm/sialog so that we can track failed
logins. We have been having problems with DU3.2g disabling terminals, which
ofcourse stops users from logging in. Since turning it on I have now found
that hundreds of times every day we are getting the message
Failure to authenticate session for (null) on /dev/ttyp1
or
Failure to authenticate session for on /dev/ttyp2
This causes DU3.2g to disable /dev/ttyp1 which is the first tty that DU
tries to allocate to someone when they login.
I have absolutely no idea why we are getting these messages, or where to
start looking. Can anyone shed some light on this for me? Any help would be
greatly appreciated.
TIA
Glenn.
B&D Australia - The garage door people.
.
,--_|\ Glenn Newbery Email : glenn_at_bnd.com.au
/ B&D \ Systems Manager Voice : +612 9722 5631
\_,--\_/ Fax : +612 9772 3830
v
Received on Fri Sep 04 1998 - 00:16:10 NZST