summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorHannes Reinecke <hare@suse.de>2011-06-21 11:23:02 +0200
committerMike Christie <michaelc@cs.wisc.edu>2011-06-26 17:36:50 -0500
commite5bd9130d5d35cbdce04f04e156bde82a0641583 (patch)
tree43994202d0d4f0bf0cd9de1230219f70951bb358 /doc
parent406a7f3074c12757f0db75fc297ef10d2bcc6002 (diff)
downloadopen-iscsi-e5bd9130d5d35cbdce04f04e156bde82a0641583.tar.gz
iscsid sends SIGTERM to PID 0
Occasionally iscisd will send a SIGTERM to pid 0, causing all sorts of weird things. Problem is that pid == 0 is a valid return value for log_init(), so that all routines only check for pid < 0. However, as the signal handler is inherited from the parent, even the logging thread has a signal handler installed, for which the internal pid is always '0'. So when a SIGTERM is send to the logging thread, it'll forward the signal to PID 0. References: bnc#589064 Signed-off-by: Hannes Reinecke <hare@suse.de>
Diffstat (limited to 'doc')
0 files changed, 0 insertions, 0 deletions