Skip to main content
14 events
when toggle format what by license comment
Feb 9, 2024 at 22:01 answer added coyfish timeline score: 3
Mar 1, 2021 at 17:27 comment added Charlie Parker but why does SIGTERM happen? how do I debug why my python script is exiting with that?
Sep 1, 2018 at 1:30 comment added Sparkette Also, ^C is SIGINT, not SIGTERM, and that would exit with a code of 130.
May 23, 2017 at 21:12 answer added Stéphane Chazelas timeline score: 24
S May 23, 2017 at 17:12 history suggested codeforester CC BY-SA 3.0
Casing in title.
May 23, 2017 at 16:27 review Suggested edits
S May 23, 2017 at 17:12
Mar 31, 2011 at 8:21 vote accept michelemarcon
Mar 30, 2011 at 18:58 answer added Gilles 'SO- stop being evil' timeline score: 40
Mar 30, 2011 at 18:36 comment added Gilles 'SO- stop being evil' You are! The return code 0 means a normal exit. If there was a SIGTERM, $? would be set to 143 (128 + signal number).
Mar 30, 2011 at 7:05 comment added michelemarcon Very unlikely; however, all I know is the return code (0) which is the same that I get when I terminate the process with ^C (SIGTERM). Maybe I'm overlooking something?
Mar 29, 2011 at 22:48 comment added shellter Posix documentation indicates SIGTERM is strictly a user level event. Is it possible someone else was able to kill your server program?
Mar 29, 2011 at 8:14 comment added michelemarcon It is reading and writing to a serial line, and is responding to UDP and TCP requests. I have wrapped the execution on a bash script and therefore I know the exit code.
Mar 28, 2011 at 17:57 comment added Gilles 'SO- stop being evil' I can't think of any case when the kernel or a standard tool would send SIGTERM to a random process. What can you tell us about what the program is doing and how it's started? How did you find out about the program's exit status? Can you reproduce the problem? Do you have logs you can check?
Mar 28, 2011 at 14:31 history asked michelemarcon CC BY-SA 2.5