-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Roger Leigh schrieb:
>>> myself. Befor the fix the last line was: >>> session required pam_limits.so > It wasn't obvious earlier that the problem was pam_limits.so. That > may well be a problem: on my system, I've always made that required, > and it always worked. > Just a thought: are there any syntax errors in > /etc/security/limits.conf? No, there only one active line in the limits.conf . That line is a line for corefile-Limits. And thats all. I think the only thing that isn?t fine is that some defaults arent kompatible with a vserver from my hoster. My logfiles of some services are full of ugly messages "setrlimit(RLIMIT_NPROC) failed: Operation not permitted" That messages where in the logs not the whole time I have the vserver. It cames one day, and are now everytime. So I think, the only problem is a limit of vserver-hosting. - -- Mit freundlichen Gr�ssen, Martin Wodrich -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (MingW32) iD8DBQFCkL+afymBmdFa7LcRAvtWAKDUbMNUQ28S4ZEKHr5cMaPcr4ywfgCgzLGk t58zG6Hea8qm5OCihLTP6Tc= =4LEe -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
