On 20/02/2020 13:08, Carlos E. R. wrote:
On 20/02/2020 16.00, Anton Aylward wrote:
On 20/02/2020 02:21, Per Jessen wrote:
You just create a service unit.
+1
I don't know why so many people find this scary.
Well, editing /etc/init.d/boot.local is easier, and it is a supported method with no date for disappearance.
No and No. As far as reasons not to use service units go. No, functional programming isn't easier than declarative programming. Service units can do many things that the shell programming approach could not, (see the systemd.directives man page for some examples) and make the structure of the dependencies VERY clear. No, you are wrong to imply that the systemd approach is not displacing the the SysVinit approach. It has. Running # find /etc -name '*local*' returns many things on my Leap15.1 system but not boot.local In fact the archaic /etc/init.d/ has no files at all. oh, wait, sorry, there is /etc/init.d/systemd-journald which is ### BEGIN INIT INFO # Provides: syslog # Required-Start: $null # Required-Stop: $null # Default-Start: 2 3 5 # Default-Stop: # Short-Description: compat wrapper for journald # Description: compat wrapper for journald ### END INIT INFO If I want a boot.local I have to put it there manually, but since I'm running systemd I can just as easily manually put a service unit there instead. As the man page says: /etc/systemd/system is for the local configuration -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org