| 1 |
On Friday, December 15, 2017 4:05:41 AM CET Kai Krakow wrote: |
| 2 |
> Am Thu, 14 Dec 2017 08:54:59 +0100 schrieb J. Roeleveld: |
| 3 |
> >> Some historical correctnesses about Canek: |
| 4 |
> >> |
| 5 |
> >> - He has been here for years - He has contributed here for years - He |
| 6 |
> >> supports systemd and has offered more help and explanation about |
| 7 |
> >> systemd to it's users on this list than any other single person, bar |
| 8 |
> >> none - He has never, not once, slagged off SysV Init, OpenRC or any |
| 9 |
> >> other init system, ot the creators or the users - He has never posted |
| 10 |
> >> rude or inflamatory comments about anyone arguing against him - He has |
| 11 |
> >> never resorted to ad-hominem and never posted any knee jerk opinions |
| 12 |
> >> about any other poster wrt their stance on init systems |
| 13 |
> > |
| 14 |
> > +1 I may not agree with Canek on all things: |
| 15 |
> > - I do dislike systemd, especially on Centos where disabling services |
| 16 |
> > doesn't always work past a reboot |
| 17 |
> |
| 18 |
> Well, I think you're falling the pitfall expecting "disable" makes a unit |
| 19 |
> unstartable. That is not the case. Disabling a unit only removes it from |
| 20 |
> the list of units starting on your own intent. It can still be pulled it |
| 21 |
> as a (required) dependency. |
| 22 |
|
| 23 |
Makes sense |
| 24 |
|
| 25 |
> If you really want it never being started, you need to mask the unit. |
| 26 |
> It's then no longer visible to the dependency resolver as if it were not |
| 27 |
> installed at all. |
| 28 |
|
| 29 |
This is not listed anywhere easy to find in google. |
| 30 |
|
| 31 |
> The verbs disable and enable are arguably a bit misleading, while the |
| 32 |
> verbs mask and unmask are not really obvious. But if you think of it, it |
| 33 |
> actually makes sense. |
| 34 |
|
| 35 |
Actually, it doesn't. But lets not discuss naming conventions. A lot of tools |
| 36 |
have ones where I fail to see the logic. |
| 37 |
It's a shame that option is not easily findable. And not knowing it exists, |
| 38 |
means checking man-pages and googling for them doesn't happen either. |
| 39 |
|
| 40 |
> If you "rc-update del" a service, you wouldn't |
| 41 |
> prevent it from being started neither, just because OpenRC is still able |
| 42 |
> to pull it in as a dependency. |
| 43 |
|
| 44 |
True, except with OpenRC, all the config is located together. Not mostly in / |
| 45 |
usr/.... somewhere with overrides in /etc/... |
| 46 |
I dislike all tools that split their config in this way. |
| 47 |
|
| 48 |
> So it's actually not an argument for why you'd dislike systemd. ;-) |
| 49 |
|
| 50 |
The lack of easily findable documentation on how to stop a service from |
| 51 |
starting, even as a dependency, is a reason. (not singularly against systemd). |
| 52 |
Systemd, however, has an alternative. |
| 53 |
|
| 54 |
-- |
| 55 |
Joost |
Archives