Package: bsdutils
Version: 1:2.33.2-0.1
Severity: normal
I was debugging a dhclient-script hook when I noticed this in the
journal
Nov 14 09:31:23 debian olaf[3598]:
/etc/dhcp/dhclient-exit-hooks.d/local-static-route returned non-zero exit
status 1
THe issue is not with the non-zero exit status, that's my fault and has
been fixed, but the process name had me scratch my head. I would have
expected `dhclient-script` (which sources the hook) or `dhclient` which
run the `dhclient-script`, *not* my username.
BTW, my username was used because I'd been running ifup/ifdown via sudo
for testing purposes. When I restarted networking.service, the username
changed to `root`.
Also, simply running `logger` from the command-line will reproduce this.
$ logger 'Hello World!'
$ journalctl -n 1 2>/dev/null
-- Logs begin at Wed 2019-11-06 16:20:35 JST, end at Thy 2019-11-14 09:37:18
JST. --
Nov 14 09:37:18 debian olaf[2001]: Hello World!
In this case I would have expected the process to be `bash`, the shell
from which I ran the `logger` command, not my username.
I don't know if using the username instead of the parent process name is
intended behaviour or not but if it is a note in the manual page would
be nice. If it is not intended behaviour, it ought to be fixed.
Hope this helps,
--
Olaf Meeuwissen, LPIC-2 FLOSS Engineer -- EPSON AVASYS CORPORATION
Free Software Foundation Associate Member since 2004-01-27
Support Free Software https://my.fsf.org/donate
Join the Free Software Foundation https://my.fsf.org/join
