]> git.ipfire.org Git - thirdparty/util-linux.git/commit
projects / thirdparty / util-linux.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: c630ad7) | patch
su: don't use kill(0, ...) when propagate signal
authorKarel Zak <kzak@redhat.com>
Mon, 17 Feb 2014 12:22:30 +0000 (13:22 +0100)
committerKarel Zak <kzak@redhat.com>
Wed, 23 Apr 2014 08:54:31 +0000 (10:54 +0200)
commit6592ccc4a7397d5a4a6945e3d89d559bbfcea018
treee5cdf3005fce96eb4ff34faac34909443e49aa62tree | snapshot
parentc630ad744050e3e918620e20455e70bd7ab20cfccommit | diff
su: don't use kill(0, ...) when propagate signal

The current code uses kill(0, caught_signal) after regular
signal cleanup and before exit (all just to make shells happy).

Unfortunately, kill(0, ...) is a bad idea. It seems better to use
kill(getpid(), ...) otherwise we kill our parent process too.

Addresses: https://bugzilla.redhat.com/show_bug.cgi?id=1063887
Signed-off-by: Karel Zak <kzak@redhat.com>
login-utils/su-common.c diff | blob | blame | history
Unnamed repository; edit this file 'description' to name the repository.