5 ms·
Do you have substantive feedback about the systemd timer implementation, or are you just here to shitpost?
by otterley 9y ago
Do you have substantive feedback about the systemd timer implementation, or are you just here to shitpost?
- nimbius 9y agono, the poster is citing well documented historical evidence that systemd reinventions of traditional posix compliant unix/BSD/Linux services arrive as a horrendously complex mess of overcomplicated code. take oddjobd for example, which supplants pam_mkhomedir.so in creating a users home directory on first login. oddjob is its own standalone daemon running constantly, while pam_mkhomedir is invoked only as necessary. oddjob needs dbus and systemd to complete what in many systems is just a simple mkhomedir && chown user:grp $homedir. its now fully dependent on the most fundamental building blocks of your OS to do one simple thing. this also assumes the user doesnt have a home directory...which...many do. in most commercial infrastructure if you suggest installing oddjobd to handle the potential for a user to log in without their home youll be laughed out of the chat. oddjobd forces organizations back into the 1980s and NIS based implementations of federated authentication where you had to go to a new user machine, or an account creation machine first if you dont want to run yet another idle daemon on your machine
- wereHamster 9y ago> the poster is citing well documented historical evidence I don't see any of that citation. Or evidence.
- dig1 9y agoFor evidence, use the source Luke ;) systemd has plenty of reinvention evidences...
- userbinator 9y agoAnother memorable example is systemd's DNS resolver which somehow has to involve XML parsing/unparsing just for a simple hostname lookup: https://lists.dns-oarc.net/pipermail/dns-operations/2016-June/014966.html https://lists.dns-oarc.net/pipermail/dns-operations/2016-Jun...
- yrro 9y agoWhat a load of technically illiterate nonsense.
- userbinator 9y agoWow. Perhaps you should read through this and then reconsider who is "technically illiterate": https://news.ycombinator.com/item?id=14652787 https://news.ycombinator.com/item?id=14652787
- dang 9y agoThis breaks the site guidelines badly, particularly the ones about civility and avoiding shallow dismissals. We ban accounts that post like this (regardless of how wrong someone else might be), so please read https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html and follow the rules from now on.
- otterley 9y agoWhat does systemd-resolved have to do with systemd's timer implementation? It's possible to agree that the resolver implementation is problematic, while other parts of the ecosystem are reasonably good.
- otterley 9y agoWhat does this have to do with systemd, exactly? This sounds like a rant that is only tangentially related, and demonstrates that you don't know why oddjobd exists (specifically to provide an encapsulated means by which unprivileged processes can safely perform privileged operations). Just because you deem something overly complicated doesn't mean that it doesn't serve a practical purpose.
- deleted 9y ago[deleted]
- parenthephobia 9y agooddjob isn't part of systemd and doesn't use systemd.
- DC-3 9y agoTheir point is a valid one though. I don't really think the init process is the right place for timers.
- derefr 9y agoMaybe you've never tried to optimize an OS for battery life on mobile devices, then. There needs to be one place that timers happen—ideally the kernel, but a "userland kernel adjunct" like systemd is fine too—in order to be able to coalesce all the timers on the system (except for real-time ones) along some granularity scale. You don't want to go to all the effort to spin up a CPU core to schedule a (cron) process thread, just to find out it has no work to do. Ideally, if you're going to check the time at all, you just want it done in one thread running on one core, so that the rest of the cores can stay asleep and you never have to spend energy context-switching when idle. That being said, systemd isn't quite the right architecture for getting down to a "tickless everything" system. That'd be something more like WinNT's kernel timer object API, where the kernel sends an event to your window's or service's message inbox to wake you up when the timer is done; or macOS's "Grand Central Dispatch", where any native code (including non-Foundation POSIX code!) can pass scheduling control of any async block through a Mach trap over to one central scheduling process, which coalesces both timers and the runtimes of async events in general so that all background CPU activity happens in bursts with idles in between.
- theamk 9y agoIn my cronjob, I like to log the target process output, and ensure that only one timer jobs runs at a time, and apply resource limits, and have an easy way to know if the job is still running. Right now, I am doing this all with a mess of shell scripts (flock + logger + echo calls + pgrep). This is fragile and ugly. Since systemd provides all of the above easily, a better approach will be one-off systemd jobs. In this case, my crontab entries would be a trivial -- "1 3 * * * root systemctl start cronjob1". This only requires scheduling functionality -- background execution, env vars, email notification and other things no longer matter. From there, it is just one small step to move scheduling into the init process itself -- after all, compared to what other things init does, scheduling is both simple and safe.
- liveoneggs 9y agosystemd is attempting to take over unix just like gnome has always been trying to turn linux into GNOME-OS. It's all just a matter of having people with no taste given too much influence.
- qbrass 9y agoThe main code contributor to both projects is Red Hat.
- liveoneggs 9y agoexactly. Ever used jboss? :)
- deleted 9y ago[deleted]