Bug 86263 - Documentation and default logind.conf are inconsistent
Summary: Documentation and default logind.conf are inconsistent
Status: RESOLVED FIXED
Alias: None
Product: systemd
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: All All
: medium normal
Assignee: systemd-bugs
QA Contact: systemd-bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-13 18:48 UTC by come.bernigaud
Modified: 2014-11-23 00:54 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description come.bernigaud 2014-11-13 18:48:19 UTC
http://cgit.freedesktop.org/systemd/systemd/tree/man/logind.conf.xml?id=v217
http://cgit.freedesktop.org/systemd/systemd/tree/src/login/logind.conf?id=v217
As you can see documentation is speaking about on/off while the default configuration file contains yes/no.

Which is it?
Comment 1 Lennart Poettering 2014-11-13 19:04:38 UTC
Either. We accept "yes", "on", "1", "true" as positive booleans and "no", "off", "0", "false" as negative booleans whenever there's a boolean to parse. This is documented at a variety of places (for example systemd.unit(5)), but not specifically for logind.conf. 

I can see that it would be helpful to explain this in logind.conf(5) too, but I also kinda like keeping things short and avoid beeing too redundant.
Comment 2 come.bernigaud 2014-11-14 10:48:05 UTC
Could you adapt either default logind.conf or the man page so that the same values are used in both? It was troubling for me having different informations in both places.
It’s a good thing that all are accepted.

An other solution would be to have in the documentation something like «these are boolean, see systemd.unit(5) for more information» to avoid redundance and be sure people have all information about boolean handling.
Comment 3 Zbigniew Jedrzejewski-Szmek 2014-11-23 00:54:56 UTC
http://cgit.freedesktop.org/systemd/systemd/commit/?id=6e3157c5e6


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.