I am getting a lot of the following types of error in my secure log on a CentOS 5.4 server:
crond: pam_loginuid(crond:session): set_loginuid failed opening loginuid sshd: pam_loginuid(sshd:session): set_loginuid failed opening loginuid
I've seen discussion of this being caused when using a non-standard kernel without the correct CONFIG_AUDIT and CONFIG_AUDITSYSCALL options set. Where this is the case, it is advised to comment out some lines in the pam.d config files.
I am running a Virtual Private Server where I need to use the kernel provided by the supplier. Is there a way to find out what options they used to configure the kernel? I want to verify if the above is the cause.
If this turns out not to be the cause, what are the risk of disabling pam_loginuid for crond and sshd?