"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 by sending it a SIGHUP or doing
"systemctl daemon-reload"? Yes, and rebooted the machine. Multiple times. No effect - I'm still getting the "Invalid log level'warn'" message during boot even though 'warn' is no longer in system.conf.
Not sure if it's at all related, but the error message is in a section of log/messages with bogus timestamps - 4 hours before the real time. (Boot logs start off with the right time, says "Journal stopped", then "journal: Runtime journal is using 4.0M (max allowed..." with the bogus time, couple of pages of log entries with the bogus time, then repeats "Journal stopped" w/ bogus time, then "journal: Runtime..." with the correct one again.)
1. Why isn't systemd using the current version of the config file - even after systemctl daemon-reload, systemctl daemon-reexec, and reboots?
2. How do I get systemd to stop filling my log files with Starting Paths. Reached target Paths. Starting Timers. Reached target Timers. Starting Sockets. Reached target Socket etc.?
-
Andy Hairston