Hi Chris, Chris Hofstaedtler writes:
> Control: tags -1 upstream wontfix > > * Meeuwissen Olaf <[email protected]> [191114 10:24]: > [..] >> 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. > > logger(1) clearly documents this: > The default tag is the name of the user logged in on the terminal > (or a user name based on effective user ID). Sorry. I completely missed this until you pointed it out :-( > It also says other things that are recommended when running logger > from a shell script (like dhclient-script), i.e. to pass --id=$$(PPID). In addition or instead of that, use of the --tag option would have prevented this bug report. Guess I should submit a wishlist report against isc-dhcp-client then. > logger itself does no magic to determine its parent process, and I > don't see how it could do that in a meaningful way without a > backwards incompatible change. I don't the backward incompatibility issue but seeing that the behaviour is documented, this report can be closed. Thanks for the quick feedback, -- 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
