On 20 Sep 2004, at 18:46, Kenn Humborg wrote:
>> 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?
>> Have you tried restarting sshd? I think it _shouldn't_ work, but
> it's easy to try.
As I may have mentioned :-) I did, and it didn't. But then a little
thought struggled to the surface, and I had a look at sshd_config and
changed UsePAM from no to yes. Made all the difference in the world :-)
So thanks very much K & K - I should have posted this to ILUG hours ago.
Niall
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!
