wrt the kernel ignoring the crashdump helper for SIGQUIT,
it should be ignoring anyway as `ulimit -c 0` was set!
I.E. there seems to be an ubuntu specific bug here in that
the apport helper (or whatever is in /proc/sys/kernel/core_pattern)
is called even when one does `ulimit -c 0`
I tested Fedora 7 (2.6.21-1.3194.fc7), and this does not happen.
I tested Feisty (2.6.20-16-generic), and this does happen.
Does ubuntu have its own patches pertaining to /proc/sys/kernel/core_pattern
as I didn't notice any related fedora or upstream patches subsequent to 2.6.20?
Note ignoring the signal in apport does not suffice for me,
since I need the script in which Ctrl-\ is entered to respond immediately,
and starting the python interpreter and parsing the script
will be a significant delay (even though python 2.5 is much better in this regard).
wrt the kernel ignoring the crashdump helper for SIGQUIT, kernel/ core_pattern)
it should be ignoring anyway as `ulimit -c 0` was set!
I.E. there seems to be an ubuntu specific bug here in that
the apport helper (or whatever is in /proc/sys/
is called even when one does `ulimit -c 0`
I tested Fedora 7 (2.6.21- 1.3194. fc7), and this does not happen. 16-generic) , and this does happen.
I tested Feisty (2.6.20-
Does ubuntu have its own patches pertaining to /proc/sys/ kernel/ core_pattern
as I didn't notice any related fedora or upstream patches subsequent to 2.6.20?
One can reproduce by doing:
[root@f7]# echo "|/bin/true" > /proc/sys/ kernel/ core_pattern
[root@f7]# ulimit -c 0
[root@f7]# cat #hit Ctrl-\ now
Quit
[root@feisty]# echo "|/bin/true" > /proc/sys/ kernel/ core_pattern
[root@feisty]# ulimit -c 0
[root@feisty]# cat #hit Ctrl-\ now
Quit (core dumped)
Note ignoring the signal in apport does not suffice for me,
since I need the script in which Ctrl-\ is entered to respond immediately,
and starting the python interpreter and parsing the script
will be a significant delay (even though python 2.5 is much better in this regard).
cheers,
Pádraig.