[Centos] CentOS 3.1: sshd and pam /etc/security/limits.conf file descriptor settings problem
Sean Staats
sstaats at questia.comMon Sep 13 21:57:44 UTC 2004
- Previous message: [Centos] Upgrading Fedora Core 1 to CentOS
- Next message: [Centos] CentOS 3.1: sshd and pam /etc/security/limits.conf file descriptor settings problem
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Why can't non-uid 0 users have more than 1024 file descriptors when logging in via ssh? I'm trying to allow a user to have a hard limit of 8192 file descriptors(system defaults to 1024) via the following setting in /etc/security/limits.conf: jdoe hard nofile 8192 But when jdoe logs in via ssh and does 'ulimit -Hn' he gets '1024' as a response. If he tries to set it with 'ulimit -Hn 8192' he gets an 'Operation not permitted' error. If jdoe instead telnets to the box, he gets the hard limit of 8192 file descriptors. Here is what happens when I set the hard limit to 512 in limits.conf: jdoe hard nofile 512 When jdoe logs in via ssh, he gets a hard limit of 512 file descriptors. The same goes for telnet. So ssh is certainly reading the limits.conf file and applying the settings, so long as nofile <= 1024. Why won't ssh allow users to have more than 1024 file descriptors??? Many thanks! -Sean -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://lists.centos.org/pipermail/centos/attachments/20040913/04023946/attachment.sig>
- Previous message: [Centos] Upgrading Fedora Core 1 to CentOS
- Next message: [Centos] CentOS 3.1: sshd and pam /etc/security/limits.conf file descriptor settings problem
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the CentOS mailing list