← Back to team overview

touch-packages team mailing list archive

[Bug 65244] Re: ulimits not set according to /etc/security/limits.conf for root - update documentation

 

I have added configurations in /etc/security/limits.conf
*               soft    core    unlimited
root            soft    core    unlimited

then after, i have given a process crash, kill -s SEGV <mysql_id>. I got
a core dump file for mysql.

But after this if i start the service by "service mysql start"(service
is getting start). Then if I give crash i'm not able to get core dump
file and I have checked "ulimit -c" which is 0. why is it happening?

In the same case instead of "service mysql start" if I give "service
mysql restart", then if I give crash i'm able to get core dump file.

As a workaround i have added "ulimit -c unlimited" to "start" section of
/etc/init.d/mysql, then the core dump file is created in both the
scenarios.

But how to configure "ulimit -c unlimited" in the "start" section of
each and every service that is present in /etc/init.d(like prescript
before executing start) . Or is there any way to resolve this.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/65244

Title:
  ulimits not set according to /etc/security/limits.conf for root -
  update documentation

Status in “pam” package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: libpam-modules

  Hello, I am desperately trying to allow root big or unlimited
  coredumps. I set "* soft core 102400" and "* hard core 102400" in
  /etc/security/limits.conf to no avail, after root login over ssh, I
  still get the stubborn answer "# ulimit -c" → "0". I don't know if
  this is a bug in pam itself; it works OK for other users.

  I also tried to add pam_limits.so to /etc/pam.d/common-session,
  nothing happens. The same result when putting "ulimit -c unlimited"
  into /etc/environment.

  If this is not a bug in PAM but only my inability to find the right solution, please consider it a documentation bug report. It prevent us from debugging crashing gdm daemon (see 
  http://bugzilla.gnome.org/show_bug.cgi?id=357632 and https://launchpad.net/bugs/62139)

  
  Thanks, Vaclav Smilauer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/65244/+subscriptions