[Bug 382096] Re: syslog(3) doesn't cover openlog()'s ident being NULL
Ralph Corderoy
ralph at inputplus.co.uk
Tue Apr 17 21:50:14 UTC 2012
** Changed in: manpages (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to manpages in Ubuntu.
https://bugs.launchpad.net/bugs/382096
Title:
syslog(3) doesn't cover openlog()'s ident being NULL
Status in “manpages” package in Ubuntu:
Confirmed
Bug description:
Ubuntu 9.04, manpages-dev 3.15-1.
syslog(3) documents openlog(ident, option, facility). It doesn't
describe what happens if openlog is passed NULL as an ident. It does
say that syslog itself will do this if syslog is called without
openlog having been called previously. So, either I can pass NULL to
openlog myself, or syslog may do so, but what will that do in terms of
the data logged?
Empirically, it seems the basename of argv[0] will be used. This
should be documented.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/manpages/+bug/382096/+subscriptions
More information about the foundations-bugs
mailing list