Stories
Slash Boxes
Comments

SoylentNews is people

Seven Part Post on Supervisors and Init Systems

posted by Fnord666 on Thursday August 10 2017, @12:18AM   Printer-friendly
from the not-the-PHB dept.

canopic jug writes:

Frew Schmidt has written seven posts on init systems and supervisors. He covers both basic and advanced supervisors, and what they do including some more unusual options.

Original Submission

 
This discussion has been archived. No new comments can be posted.
Seven Part Post on Supervisors and Init Systems | Log In/Create an Account | Top | 18 comments | Search Discussion
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

  • (Score: 5, Informative) by ledow on Thursday August 10 2017, @12:31PM (1 child)

    by ledow (5567) on Thursday August 10 2017, @12:31PM (#551590) Homepage

    Irony:

    All the systemd functionality could be achieved with shellscripts, without even having to change the SysVInit style of things. Everything. From the process control to the cgroups functionality to everything.

    But, apparently, it all had to be executables... erm... because.

    And now we have init system binaries running their own DNS resolver (badly) because of it.

    The thing I love - systemd was supposed to ensure that, when you wanted to use DNS - for, say, mapping a network location to boot from - you could use any resolver and systemd was supposed to make sure that everything it required would be up and ready by the time you needed it. That was kind of the whole point of it. So why systemd required its OWN DNS resolver, rather than make sure the system one was up and ready, I can't really fathom.

    Starting Score:    1  point
    Moderation   +3  
       Insightful=1, Informative=2, Total=3
    Extra 'Informative' Modifier   0  
    Karma-Bonus Modifier   +1  
    Total Score:   5  

  • (Score: 2) by VLM on Thursday August 10 2017, @06:13PM

    by VLM (445) on Thursday August 10 2017, @06:13PM (#551781)

    init system binaries running their own DNS resolver (badly)

    They have noobs in charge of systemd, typical inner platform effect. They'll have an entire kernel embedded in there before ya know it. Noobs...

    you could use any resolver and systemd was supposed to make sure that everything it required would be up and ready by the time you needed it.

    I changed some DNS server ips at home and on some static configured ubuntu images I had a huge battle with resolvconf and/or systemd over resolv.conf and the online advice from years old blogs simply no longer works. What a nightmare. In the old days you'd edit the text file /etc/resolv.conf and it just works every time, but that is complicated into not working now, and reinstalling ubuntu is the simplest way to change a DNS server IP address on a static configured machine. I did work around it eventually without reinstalling, I think I deleted and recreated the file and then chattr'd it immutable or something. What a piece of shit of an operating system that you can't even trust text editor changes to work. "Systemd, now making windows easier to admin than MS windows..."