syslog(3) doesn't cover openlog()'s ident being NULL
Bug #382096 reported by
Ralph Corderoy
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
manpages (Ubuntu) |
Fix Released
|
Low
|
Unassigned |
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.
tags: | added: manpage |
Changed in manpages (Ubuntu): | |
importance: | Undecided → Low |
Changed in manpages (Ubuntu): | |
status: | New → Confirmed |
To post a comment you must log in.
Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. I have classified this bug as a bug in manpages.
When reporting bugs in the future please use apport, either via the appropriate application's "Help -> Report a Problem" menu or using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https:/ /wiki.ubuntu. com/ReportingBu gs.