On 03/31/2015 08:48 AM, Andy Hairston wrote:
Finally found out that I was using the wrong syntax for the set-log-level command. (Why did it say 'access denied' instead of 'bad syntax???) Changing the log level all the way to emerg still had no effect. And in my logs during reboot, I'm seeing this message: systemd[1]: [/etc/systemd/system.conf:11] Invalid log level'warn': Operation not permitted even though /etc/systemd/system.conf doesn't contain LogLevel=warn (anymore) - it has LogLevel=emerg!
Note that the valid values for "LogLevel=" are "emerg", "alert", "crit", "err", "warning", "notice", "info", and "debug". "warn" isn't valid.
Why isn't systemd reading the CURRENT /etc/systemd/system.conf file? Why does the command line setting seem to have no effect? Is systemd this hopelessly broken?
Have you restarted systemd either by sending it a SIGHUP or doing "systemctl daemon-reload"? ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@xxxxxxxxxxxxxx - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - If it's stupid and it works...it ain't stupid! - ---------------------------------------------------------------------- -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
