[systemd-bugs] [Bug 76935] Do not parse "debug" command line parameter
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Sat Apr 5 23:24:31 PDT 2014
https://bugs.freedesktop.org/show_bug.cgi?id=76935
--- Comment #22 from David Strauss <david at davidstrauss.net> ---
There seems to be quite a lot of misunderstanding here. systemd has used
"debug" to set its own level to debug for quite some time, at least v208, which
is from mid-2013.
The issue causing the acute pain was an broken assertion, a bug that should
have been fixed before the thread on LKML even started. No one claimed that
assertion failure wasn't a bug, and no one hesitated to fix it (see comment
#17). So, "debug" should already be usable without also setting
systemd.log_level, which should have fully worked around the issue even with
the assertion bug.
In short, if everything was fine for you as of weeks or months ago, it should
already be back to being fine.
The question now is the semantics of the kernel command line, specifically the
scope which "debug" affects. I've personally given the +1 to Greg's patch,
which would switch it to "systemd.debug", but there isn't consensus to do that.
The primary argument against the namespacing is catering to end users trying to
troubleshoot who are unfamiliar with the kernel/udev/systemd split of
responsibilities. Obviously, the counter-argument is to namespace in order to
fully isolate systemd's debug mode from the kernel's (without requiring
systemd.log_level) and avoid a similar assertion bug affecting developers the
same way.
Because this is now a discussion about what *intended* functionality should be,
most discussion is happening on the mailing list in the thread started by
Greg's patch. I encourage you to post there if you would like to contribute. If
you're merely going to flame, especially in a way showing that you don't
understand the assertion fix vs. debug option distinction, then please find
somewhere else to post outside of systemd Bugzilla and the mailing list.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20140406/7ae21098/attachment.html>
More information about the systemd-bugs
mailing list