1 |
On Monday, 6 November 2017 23:11:44 GMT Rich Freeman wrote: |
2 |
> On Mon, Nov 6, 2017 at 10:45 AM, Ian Zimmerman <itz@××××××××××××.org> wrote: |
3 |
> > On 2017-11-05 17:17, Rich Freeman wrote: |
4 |
> >> Distros will always have to do integration work, and that is fine. |
5 |
> >> That is the role of a distro. And sometimes distros have to roll |
6 |
> >> their own tools when they just aren't available. Once upon a time |
7 |
> >> service managers fell into that category. Now this is less the case. |
8 |
> > |
9 |
> > What's a service manager? |
10 |
> |
11 |
> Easiest way to explain it is to give examples. Openrc, systemd, |
12 |
> runit, and upstart are all service managers. I'd argue that sysvinit |
13 |
> is also a service manager but nobody really uses it as one unless you |
14 |
> count getty as a service. |
15 |
> |
16 |
> A service manager is a program used to manage the daemons running on a |
17 |
> system. |
18 |
> > Is making cron care about missed jobs service |
19 |
> > management, but running daily/weekly/monthly jobs isn't? |
20 |
> |
21 |
> Cron is generally not considered a service manager though there is |
22 |
> some overlap since it does manage jobs. I wouldn't make any |
23 |
> distinction in this regard to how it handles missed jobs. Those are |
24 |
> just features that a cron implementation can have or lack. |
25 |
> |
26 |
> It is like arguing about whether sh, dash, or bash are shells on the |
27 |
> basis of the features they provide. They're all shells, but at the |
28 |
> same time we can acknowledge that they have different feature sets. |
29 |
|
30 |
Apologies for prolonging this exhaustive and exhausting thread, but what is |
31 |
the Gentoo suggested cron application for a non-24-7 desktop these days? I'm |
32 |
still using sys-process/vixie-cron because I guess that's what was de rigueur |
33 |
at the time I installed this system, although on other desktop PCs I run sys- |
34 |
process/cronie. |
35 |
|
36 |
-- |
37 |
Regards, |
38 |
Mick |