[Nix-dev] Will there be a systemd replacement at any time inthefuture?

[Michael Raskin]

>>> It did not. There was no way with Upstart to get the log output of a service.
>> 
>> In NixOS the problem wasn't noticeable…
>
>Again, the logging situation with systemd is vastly superior than it was with
>Upstart. With Upstart you simply couldn't do something like "systemctl status
>foo.service" and see the most recent log messages of a service. Or do
>"journalctl --since yesterday -p err" to see important recent messages. And so on...

Observed situation is _worse_ for me. 

I cannot do ```systemctl status sshd``` because I need to manage 
fragmentation manually for this to ever finish.

Using grep and tail does work, journalctl is simply too slow to use.

Also, any situation where part of logs is lost in the same situation,
is _not_ vastly superior to a situation where logs were strangely 
distributed but not lost.

>> Logging of output was implemented in a way that didn't require an edit
>> to every jobs and the logs looked the same as all the other logs on the
>> system…
>
>What is the "edit to every job" that you refer to? Also, it's only with the

I cannot understand how to edit vsftpd job in a way that ensures that in
case I specify incorrect configuration and vsftpd correctly exists after
sending a description of the problem to stderr I can retrieve the error
message. 

Obviously, if there is a workaround for this systemd journalling 
property, it would be nice to apply it once for all the services…

>journal that logs can be accessed consistently, rather than being scattered
>across a zillion files, each in a different format.

I always prefer any somehow usable text files to a binary format that
requires _more_ I/O for filtering. I thought is has been a few years 
since I/O is more expensive than CPU cycles.

>I'm simply not seeing the journal issues you seem to run into constantly. Did
>you make an issue for them?

For what? For journald trashing HDD like crazy? Wasn't it always common 
knowledge?

For losing logs you showed me a link that shows it is a known problem
with no known solution. I asked around a few times on IRC and got the
same impression minus the link. 

I don't see _what_ can be done on NixOS level — as you confirmed, 
upstream is aware and is not going to fix it.