[Bug 938669] Re: upstart jobs do not respect /etc/security/limits.conf

Steve Langasek steve.langasek at canonical.com
Sun Sep 9 10:07:44 UTC 2012

It's by design that upstart does not look at /etc/security/limits.conf
for system jobs.  PAM settings are only applied to user sessions, not to
system services.

As Alexander comments, we do want to apply PAM limits to user jobs,
something which is currently not implemented; but that's not what this
bug report is about, so closing.

** Changed in: upstart (Ubuntu)
       Status: Triaged => Invalid

** Changed in: upstart
       Status: New => Invalid

You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to upstart in Ubuntu.

  upstart jobs do not respect /etc/security/limits.conf

Status in CUPS - Common Unix Printing System:
Status in Upstart:
Status in “upstart” package in Ubuntu:

Bug description:
  I run a terminalserver under Ubuntu 11.10 (oneiric) and CUPS
  1.5.0-8ubuntu6. Unfortunately i get "Max clients reached, holding new
  connections..." error.

  I try to increase the MaxClients value to 8192 in /etc/cups/cupsd.conf
  (and LogLevel to debug) but CUPS reduces this to 1/3 of file
  descriptor limit from the system with is by default 1024:

  I [22/Feb/2012:12:02:37 +0100] Using default TempDir of /var/spool/cups/tmp...
  I [22/Feb/2012:12:02:37 +0100] MaxClients limited to 1/3 (341) of the file descriptor limit (1024)...
  I [22/Feb/2012:12:02:37 +0100] Configured for up to 341 clients.

  Also i try to set higher file descriptor limit in /etc/security/limits.conf
  root hard nofile 64000
  root soft nofile 64000

  and also add "session required pam_limits.so" to /etc/pam.d/common-
  session but CUPS set still MaxClients to 341.

  Ulimit seams to works fine:
  root at ts:~# ulimit -n

  Before i upgrade to Oneiric i have same configuration on Ubuntu 10.04
  Lucid and CUPS 1.4.3-1ubuntu1 with works fine.

  This seams to by a similar bug to:

  Lets me know if you need some more information.

  BR Pawel

To manage notifications about this bug go to:

More information about the foundations-bugs mailing list