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]:
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
warn isn't valid.
I know that now; looks like I mistook the Apache logging level names for
the Linux ones. I don't understand why an invalid log level would
generate an 'access denied' message instead of something more sensible,
like 'invalid log level'.
Have you restarted systemd either
After even more Google searching, I found the command
systemd-analyze set-log-level warn
Running this as root, I got:
Failed to issue method call: Access denied
Strangely, I can run it with 'notice' instead of 'warn', and it silently
completes - probably meaning it's already set to notice.
I have a near-stock installation of Fedora 21, and am experiencing the
systemd log flood mentioned previously
(https://lists.fedoraproject.org/pipermail/fedora-server-list/2014-May/001126.html).
How do I get systemd to stop putting massive amounts of information into
/var/log/messages for
