3 ms·
Did you try systemd? My biggest problems with it is that a) it's written by macho C programmers, who couldn't produce anything secure even if their lives depend
by zzzcpan 8y ago
Did you try systemd? My biggest problems with it is that a) it's written by macho C programmers, who couldn't produce anything secure even if their lives dependent on it and b) it's not unixy, i.e. not defining protocols and not letting everyone implement their own supervisors and their own behaviors and c) it's too sloppy wrt changing files on disk, making it really hard to keep control over that.
But I do believe we still need to move towards supervision trees, just not with systemd.
- taylodl 8y agoI've used systemd and I'll still continue using systemd at work where we use RHEL, because our decision to use RHEL isn't going to change any time soon, if ever. But on my own devices? No. That's not to say systemd doesn't have some good points, it does. It's good at being an init system - the problem is it's gone on and taken over so much more. It's like kudzu. We wanted some greenery but damn! Now it's everywhere! But, it appears the Linux community overall likes it. Which is their prerogative. I don't, which is mine. I look at it like an amicable divorce. I'm leaving Linux, but there's still visitations (work). I wish the community the best.
- the_why_of_y 8y agoAgree about a) [but: doesn't that rather contradict "it's not unixy"... ]. Regarding b), what do you mean exactly? If you're talking about cgroups, you can delegate part of the hierarchy to a supervisor process via the Delegate= directive, as documented at https://systemd.io/CGROUP_DELEGATION https://systemd.io/CGROUP_DELEGATION