Alec wrote: > Anything in dmesg? I know one way to get past it ( without > solving the bug, which is the real issue here ) is to just remove the > local script from running, since it's empty. It doesn't have to be > run. However, also check /var/log/message and anywhere else you might > have some juicy logs. > >> >> -- >> [email protected] mailing list >> >> > > > -- > Alec Warner > Spartasoft Secretary ( spartasoft.msu.edu ) > Junior Computer Science > Michigan State University > [EMAIL PROTECTED]
Hi Alec, Interesting comment. Here's some feedback. 1. Nothing from dmesg that I could detect. 2. Some /var/log/message entries that might be significant, I'll leave the analysis to you. At the tail end of the log I see this, leaving out the date and hostname boilerplate: login[1174]: PAM pam_putenv: delete non-existent entry; REMOTEHOST PAM-env[1174]: Unknown PAM_ITEM: <DISPLAY> login[1174]: PAM pam_putenv: delete non-existent entry; DISPLAY PAM-env[1174]: Unknown PAM_ITEM: <XAUTHORITY> login[1174]: PAM pam_putenv: delete non-existent entry; XAUTHORITY login(pam_unix)[1174]: session opened for user root by (uid=0) Thoughts? You think this problem is a bug, a pam bug, perhaps? jlowell -- [email protected] mailing list
