[ILUG] Setting limits in SuSE 9.1

[Niall O Broin]

On 20 Sep 2004, at 17:54, Kieran.Tully AT acm.org wrote:

> On Mon, 20 Sep 2004 16:54:37 +0100, Niall O Broin <niall at linux.ie> 
> wrote:
>
>> ls -lu seems to indicate that neither  /etc/security/limits.conf  nor 
>> /lib/
>> security/pam_limits.so  are being read and lsof doesn't show 
>> /lib/security/
>> pam_limits.so to be opened by any process, although quite a few other 
>> /lib/
>> security/pam_XXXX.so files are.
>>
>> Do any of you have an idea what I might be missing here ?
>
> ls and lsof suggest PAM isn't being applied to your process.
> (Obviously it won't apply to daemons started up by init scripts.).
>
> Does it work If you logon at the console?

Yes, yes it does - hurrah!

> Are you connecting over ssh? Did you set /etc/pam.d/sshd too?

Yes I am, and I did.

The desired system is remote and hence being accessed by ssh. My test 
box is local running the same OS. I tried logging into the text box via 
kdm and it didn't work. But inspired by Kieran, I tried logging on on a 
console (on the test box) and it DID work. Then I ssh'ed to the test 
box and that worked too. Then I fixed /etc/pam.d/xdm and it now works 
via a kdm login.

So, the test box works fine :-)

The production box, however, which has the same OS and the same setup 
(AFAICT) does not. One critical distinction is that the test box has 
been rebooted since the changes were made to the config files, whereas 
the production box (unsurprisingly) has not. However, /etc/pam.d/sshd 
has not been changed (it already had   session  required  
pam_limits.so) so the only file that had been changed was 
/etc/security/limits.conf but that surely must be read for every login 
anyway, in case it has been changed? So I don't think that a reboot 
should be necessary, should it?



Niall