[Centos] CentOS 3.1: sshd and pam /etc/security/limits.conf file descriptor settings problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



--=-0GeDYuo7zYuwVj6ti/Jk
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

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 <=3D 1024.

Why won't ssh allow users to have more than 1024 file descriptors???

Many thanks!
-Sean

--=-0GeDYuo7zYuwVj6ti/Jk
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQBBRhfYJ+mhQaC9R8URAlDAAJ9Pn5pTCyIgWVoDMo55uwel158G4QCfXIfa
9xnaBJT+44VMgxKvtHjbPcw=
=ecYO
-----END PGP SIGNATURE-----

--=-0GeDYuo7zYuwVj6ti/Jk--



[Index of Archives]     [CentOS]     [CentOS Announce]     [CentOS Development]     [CentOS ARM Devel]     [CentOS Docs]     [CentOS Virtualization]     [Carrier Grade Linux]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Linux USB]
  Powered by Linux