-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Nicolas Fran�ois schrieb:
>> That the version after I can fix the su-Problem >> myself. Befor the fix the last line was: >> session required pam_limits.so > You can maybe keep pam_limits "required" if you tune > /etc/security/limits.conf. I had try that. But I suprise it did not work. > You should have something like: > pam_limits[...]:setrlimit limit #... failed: Operation not permitted;... > in your vserver logs Yes, I have that in my logs. > On a vserver, you may not be able to set an unlimited limit (-1 value), > which may be the failure cause (looking on google, it seems that on a > vserver, you can limit NPROC and RSS; pam_limit may not be able to set > limits higher than these values). Only NPROC sound limited. But on every test I get an error mesage with soft=-1 hard=-1 . But in the limits.conf I set something else. - -- Mit freundlichen Gr�ssen, Martin Wodrich -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (MingW32) iD8DBQFCkwOafymBmdFa7LcRApMXAKCcr07u9ftp5sXhdT2a3X25zhFVYgCg43i7 YJFpqUoUEhL/vliIM907cUA= =2AZy -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
