Reply to post:

The D in Systemd is for Directories: Poettering says his creation will phone /home in future

R3sistance

"And when JournalD shits itself and stops forwarding? It happens."

That's hardly an excuse to not be sending logs to syslog however. Just because you're using syslog server doesn't mean you automatically stop also having local copies of the same said log files too.

"That's fine if you're working on a very local scale. It doesn't work nearly so nicely when you scale up to global scale. Don't get me wrong, it's a nice tool to have, but you don't want to have to rely on it alone.

It's also not much use if journald gets stuck and stops forwarding, or if your box is failing to boot in the first place."

Considering I work primarily in the global scale, no, it's definitely nicer in the global scale, more so when you can use something like Splunk or ELK to compare error logs from different servers. It's also nice when say /var goes read only but you still get logging occurring, cas /var can also go read only, it happens.

As for servers that have boot issues, if you're truly at a global scale then you'd probably just replace the server out. Drain everything it is doing to another server and get it diagnosed later, removed, replaced or re-installed. If you're at global scale, you should have decent higher availability in place after all. No point worrying about servers going bespoke because somebody came up with a cunning plan to fix some strange boot issue or having to worry if somebody really fixed the corrupted root file system/etc.

POST COMMENT House rules

Not a member of The Register? Create a new account here.

  • Enter your comment

  • Add an icon

Anonymous cowards cannot choose their icon