crond generated errors in secure-log every night?!?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Anyone else seeing this error in their secure-log (and logwatch
generated emails) every day/night:
crond[8040]: pam_loginuid(crond:session): set_loginuid failed opening loginuid

I've been getting hundreds of them every day on my FC5-x86 box, and I
can't figure out why.  Googling turned up a few reports which were
solved by commenting out the following line in /etc/pam.d/login:
session    required     pam_loginuid.so

I tried that, but that didn't have any impact.

--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
L. Friedman                                    netllama@xxxxxxxxx
LlamaLand                       http://netllama.linux-sxs.org


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux