I've been using ISPConfig, a very good software to handle an small ISP, for 
quite a while. We inherit a couple thousand users from the closure of another 
partner. Since they had marginal traffic but a lot of legacy sites we used a 
dedicated web server with ubuntu 12.04 LTS LAMP and the standard ISPConfig 
setup.
ISPConfig configures an user for every web and a group for every client. The 
apache user belongs to every "client" group. I think this is the real life 
situation you were looking for in order to reproduce the bug.
ISPConfig has a php cron script which is used for internal tasks between main 
server and their slaves. One of the things the script does is checking there is 
no other instance running. The php code invokes "ps ax" and then searches for 
itself in the results.
It got us a little while to realize what was happening. Finally we disabled the 
cron process, so we were able to keep the system stable though not synchronized 
to user's petitions. After googling for several days since April 28th I started 
to see the launchpad bug report.

As you can imagine, the fix does not work for us (I wouldn't boring you
if so). We can agree that we have so many groups for a user to belong to
(exactly 1556) ... that our setup is a bit weird... that system limits
must be somewhere... and so on. But in any case I think "ps" should be
protected against issuing SEGV. We will be reviewing our configuration,
of course, but wouldn't it be right to avoid the SEGV?

We can provide if required strace, example /etc/group and
/proc/apache/stat files and, of course, testing as needed.

Thanks in advance

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1174444

Title:
  ps segfault when users have large numbers of group memberships (procps
  3.2.8)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to