Hello list, How can I change the maximum core file size for processes which are started at system boot? Setting up /etc/profile to contain "ulimit -Sc unlimited" instead of "ulimit -Sc 0" does not do the job. It gives "unlimited" core file size for processes started after booting, for example logging on on the console, but not for processes which are started at booting time, for example sshd and gdm/xdm. The file /etc/security/limits.conf seems to have no effect either. So where can I set up a system-wide, also at boot time valid, maximum core file size of "unlimited"? Thanks in advance, Dominik. PS. This is required in the following scenario. The computers are employed to do parallel computations with lam-mpi. The procedure to start lam-mpi jobs is to create a daemon called "lamd" basically via ssh on every host where the parallel job is to be run on. The actual parallelized program is then started on every host by this lamd daemon. So for the parallelized program to dump a core file it is required that it inherits its maximum core file size (which should be unlimited) from the lamd daemon, which inherits it from the sshd daemon, which is started at system boot. As a side effect, as a developer, it would be fine anyway to get also core files just when running segfaulting programs under X, which is not the case as the terminal inherits its core file size from - whatever... the window manager, which is started by X, which is started by xdm/gdm which is started at boot time and thus as a maximum core file size of 0. --
On Thursday 19 February 2004 4:51 am, you wrote: If you are running SLP 9.0 it is complicated but I can send you directions. Do you have source? In 9.0 SuSE has coredumps disabled via /usr/bin/gpg-agent in package newpg-0.9.4-119 which is called from gdm and kdm at least. Please let me know if you are running 9.0 and have source. Best Regards. -- _/_/_/ Bob Pearson gottadoit@mailsnare.net _/_/_/ "The best way to get information on Usenet is not to ask a _/_/_/ question, but to post the wrong information." - Aahz' Law
Look in /etc/profile lines 77 to 91 for setting ulimit and associated parameters. On Thursday 19 February 2004 11:32, Bob Pearson wrote:
On Thursday 19 February 2004 4:51 am, you wrote:
If you are running SLP 9.0 it is complicated but I can send you directions. Do you have source? In 9.0 SuSE has coredumps disabled via /usr/bin/gpg-agent in package newpg-0.9.4-119 which is called from gdm and kdm at least. Please let me know if you are running 9.0 and have source.
Best Regards. -- _/_/_/ Bob Pearson gottadoit@mailsnare.net _/_/_/ "The best way to get information on Usenet is not to ask a _/_/_/ question, but to post the wrong information." - Aahz' Law
-- Best Regards David Barnes
Sorry - accidentally hit the send key part way through writing - I meant to say that I think you need to look for a different mechanism, as the ulimit parameter only appears to apply to processes started from the shell. (Really just expanding on what Bob has aready said.) On Thursday 19 February 2004 12:17, David Barnes wrote:
Look in /etc/profile lines 77 to 91 for setting ulimit and associated parameters.
On Thursday 19 February 2004 11:32, Bob Pearson wrote:
On Thursday 19 February 2004 4:51 am, you wrote:
If you are running SLP 9.0 it is complicated but I can send you directions. Do you have source? In 9.0 SuSE has coredumps disabled via /usr/bin/gpg-agent in package newpg-0.9.4-119 which is called from gdm and kdm at least. Please let me know if you are running 9.0 and have source.
Best Regards. -- _/_/_/ Bob Pearson gottadoit@mailsnare.net _/_/_/ "The best way to get information on Usenet is not to ask a _/_/_/ question, but to post the wrong information." - Aahz' Law
-- Best Regards
David Barnes
-- Best Regards David Barnes
On Thursday 19 February 2004 7:17 am, David Barnes wrote:
Look in /etc/profile lines 77 to 91 for setting ulimit and associated parameters.
This has no effect in SLP 9.0 i386 though you also need to do it once you fix gpg-agent. gpg-agent turns off coredumps and is a direct process ancestor of KDE and GNOME. A non-root process may only decrease the hard limit size and gpg-agent sets it to zero so coredumps are disabled. I have a source code fix that I have not had any feedback from the GNU package maintainers nor SuSE. I'll provide the source code fix to those that ask. It is NOT supported by SuSE. -- _/_/_/ Bob Pearson gottadoit@mailsnare.net _/_/_/ "The best way to get information on Usenet is not to ask a _/_/_/ question, but to post the wrong information." - Aahz' Law
Yes, this is SuSE 9.0 i386 running here. I would be very happy if you could send me a source patch of make it otherwise available. Is this gpg-agent stuff also responsible for sshd to have core dump file size of 0? Thanks, Dominik. On Thu, Feb 19, 2004 at 08:31:39AM -0500, Bob Pearson wrote:
On Thursday 19 February 2004 7:17 am, David Barnes wrote:
Look in /etc/profile lines 77 to 91 for setting ulimit and associated parameters.
This has no effect in SLP 9.0 i386 though you also need to do it once you fix gpg-agent. gpg-agent turns off coredumps and is a direct process ancestor of KDE and GNOME. A non-root process may only decrease the hard limit size and gpg-agent sets it to zero so coredumps are disabled. I have a source code fix that I have not had any feedback from the GNU package maintainers nor SuSE. I'll provide the source code fix to those that ask. It is NOT supported by SuSE. -- _/_/_/ Bob Pearson gottadoit@mailsnare.net _/_/_/ "The best way to get information on Usenet is not to ask a _/_/_/ question, but to post the wrong information." - Aahz' Law
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
--
On Thursday 19 February 2004 8:44 am, Dominik Epple wrote:
Yes, this is SuSE 9.0 i386 running here. I would be very happy if you could send me a source patch of make it otherwise available.
Is this gpg-agent stuff also responsible for sshd to have core dump file size of 0?
That I don't know but the fix should not affect that. There is good reason why one may not want a sshd coredump around because cryptographically sensitive information may be in the coredump. It will take me a few minutes to write this up and then I e-mail my patch. -- _/_/_/ Bob Pearson gottadoit@mailsnare.net _/_/_/ "The best way to get information on Usenet is not to ask a _/_/_/ question, but to post the wrong information." - Aahz' Law
Bob, First, let me thank you for the patch and your comments. On Thu, Feb 19, 2004 at 09:04:31AM -0500, Bob Pearson wrote:
That I don't know but the fix should not affect that. There is good reason why one may not want a sshd coredump around because cryptographically sensitive information may be in the coredump.
Agreed. But I _need_ coredumps from sshd-started processes. And since they inherit their maximum core file size from sshd... Technically, sshd could set its own maximum core dump file size to 0, but those from the clients to >0? Don't know - but sshd started processes can dump core, see below. Actually, the behaviour of sshd is very strange. If logged on as ordinary user in X, opening a shell, getting root via "su -" and doing # ulimit -c unlimited # ulimit -Sc unlimited # /etc/init.d/sshd restart starts a sshd server which prevents clients from creating core dumps in spite of "ulimit -c" saying "unlimited"! Who does understand that? % ssh localhost ulimit -c 0 % ssh localhost Devel/FPU/a.out % ls -l core /bin/ls: core: No such file or directory But, it can be shown that core dumps from sshd started processes are perfectly possible if logging on as root on the console and restarting sshd from there: # ulimit -c unlimited # ulimit -Sc unlimited # /etc/init.d/sshd restart % ssh axion01 ulimit -c unlimited % ssh axion01 Devel/FPU/a.out % ls -l core -rw------- 1 epple rei 53248 2004-02-19 15:39 core % date Thu Feb 19 15:39:15 CET 2004 % gdb Devel/FPU/a.out core [snip] Core was generated by `Devel/FPU/a.out'. Program terminated with signal 8, Arithmetic exception. [snip] % So, please, If anyone understands that, can he explain it? And tell me how to change the system to make the sshd daemon which is started at boot time having a maximum core dump file size of "unlimited" so that its clients can dump core? Regards, Dominik.
Dominik Epple
Agreed. But I _need_ coredumps from sshd-started processes. And since they inherit their maximum core file size from sshd...
I don't have time to study the problem but can't you just start those processes via a wrapper which sets the limit? -- A.M.
participants (4)
-
Alexandr Malusek -
Bob Pearson -
David Barnes -
Dominik Epple