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

[Ricardo M. Correia]

FWIW, yesterday I've also experienced loss of stderr messages in a service
I was trying to debug. In this case, it might have been either because the
process exited immediately afterwards or because of rate limiting, I don't
know which.

I've also always experienced HDD thrashing issues on machines which have
large journals (although for me, the command usually completes in 30-60
seconds or so, but it's still rather slower than "tail").

Just to give some more info, I'm using ZFS as my root filesystem on most of
my machines and also, for some reason, on the machines where I've been
using NixOS for a longer time journalctl complains about corrupted journals
when I use "journalctl --verify", even though my fully checksummed ZFS
filesystems never complained about a checksum error and I never noticed
corruption in any other part of the system.



On Tue, Sep 2, 2014 at 2:53 PM, Michael Raskin <7c6f434c at mail.ru> wrote:

> >I would like to add I absolutely love systemd, as it provides proper
> >dependency management, helping immensely for more dynamic setups where
> >hardware changes should trigger services reconfiguration, or for
> >changing services/vpn/routing based on wifi access point and more.
> >It's really nice that - when configured well - things just work, no
> >matter if you're booting, restarting some service or switching to a new
> >configuration. No more subtle timing errors or things that need manual
> >restarts in edgy situations. Systemd's "state manager" is extremely
> >capable. And extremely fast compared to oldschool linear scripts.
>
> Unfortunately, making SystemD _not_ do something is harder than making
> it do something. It would be irrelevant if it didn't become bigger with
> time, but deconfiguring new functionality is sometimes needed.
>
> >If we ever want to move to some other init system, I think this will
> >be easier than the upstart->systemd move. That move was mostly
> >complicated by the fact that upstart just didn't have most config
> >settings and abstractions, so stuff for run-as-user and daemonization
> >logic was put into a bash script. That had to be extracted into
>
> If we migrate to a new init system, we will have (for example) to
> rewrite all the dependencies.
>
>
>
> _______________________________________________
> nix-dev mailing list
> nix-dev at lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.science.uu.nl/pipermail/nix-dev/attachments/20140902/80a0dbc4/attachment.html