systemd: The Biggest Myths
|
|
|
Comments (3)
We can't switch it off permanently, it gets started again at some point. The ability to disable journald was on the todo list one year ago, but it is still mandatory. It's binary format is the problem, we can't read it with simpe tools . Why would I disable it ? Because I don't know what it can write that I can't read.
Have you tried "chmod -x"? And if it's on an ext2/3/4 FS, "chattr +i" to lock it into place.
@_gus
I did not even try after viewing this thread :
https://bbs.archlinux.org/viewtopic.php?id=149884
journald seems to be a backbone to systemd.
Even using 'none' as storage, it still writes its own journal.
I did not even try after viewing this thread :
https://bbs.archlinux.org/viewtopic.php?id=149884
journald seems to be a backbone to systemd.
Even using 'none' as storage, it still writes its own journal.
Post a comment
A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.
Your message:Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help
Sign up and post (it is free) or Log in and post
