Re:GNU Mcron
by userbinator on Saturday May 05, 2018 @01:00PM
(#17002622)
Another 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-Jun...
What 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.
[dead]
This 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 and follow the rules from now on.
Re:GNU Mcron
by userbinator on Saturday May 05, 2018 @01:23PM
(#17002726)
Wow. Perhaps you should read through this and then reconsider who is "technically illiterate":
Re:GNU Mcron
by wereHamster on Saturday May 05, 2018 @12:58PM
(#17002608)
> the poster is citing well documented historical evidence
I don't see any of that citation. Or evidence.
For evidence, use the source Luke ;) systemd has plenty of reinvention evidences...
What 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.
Re:GNU Mcron
by parenthephobia on Saturday May 05, 2018 @02:58PM
(#17003211)
oddjob isn't part of systemd and doesn't use systemd.
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