Lawrence D'Oliveiro <ldo@nz.invalid> wrote:
> On 23 Apr 2024 17:16:02 GMT, Andrzej Matuch wrote:
>
>> On Tue, 23 Apr 2024 15:50:08 +0000, candycanearter07 wrote:
>>
>>> I don't get why, but systemd hate is pretty common.
>>
>> Because it removes some of the control users have over the services run
>> on their system.
>
> I don?t see why. It gives you very fine-grained control.
>
> For example, with sysvinit, if you don?t like the existing sysvinit
> script, you have to write an entire new one (perhaps copying/pasting from
> the existing one). With systemd, you can create ?drop-in? unit files that
> modify an existing config without replacing it completely. Much less work
> for small changes.

One thing you can't do with Systemd is write a simple shell script that
runs when the system finishes booting, without having to learn any of
the ins and outs of Systemd. Some distros used to have a unit file to
run /etc/rc.local like SysVInit does, but it wasn't guaranteed to run
last, so it wasn't even really equivalent to a real /etc/rc.local.
But it was often good enough.

So of course they got rid of it, so now if you want something to run
at boot, you have to figure out how to write and install a unit file.
Or, just install FreeBSD, which might actually be easier.

On Sun, 19 May 2024 09:37:28 -0000 (UTC), Sebastian wrote:

> One thing you can't do with Systemd is write a simple shell script that
> runs when the system finishes booting, without having to learn any of
> the ins and outs of Systemd.

Sure you can. Just have a “WantedBy” dependency in your service definition
on whichever target represents the state you want the script to run in,
e.g. “multi-user.target” for normal system operation.

Lawrence D'Oliveiro <ldo@nz.invalid> wrote at 05:56 this Tuesday (GMT):
> On Sun, 19 May 2024 09:37:28 -0000 (UTC), Sebastian wrote:
>
>> One thing you can't do with Systemd is write a simple shell script that
>> runs when the system finishes booting, without having to learn any of
>> the ins and outs of Systemd.
>
> Sure you can. Just have a “WantedBy” dependency in your service definition
> on whichever target represents the state you want the script to run in,
> e.g. “multi-user.target” for normal system operation.

Or use @reboot in your crontab.
--
user <candycane> is generated from /dev/urandom

On Tue, 25 Jun 2024 05:56:19 -0000 (UTC), Lawrence D'Oliveiro wrote:

> On Sun, 19 May 2024 09:37:28 -0000 (UTC), Sebastian wrote:
>
>> One thing you can't do with Systemd is write a simple shell script that
>> runs when the system finishes booting, without having to learn any of
>> the ins and outs of Systemd.
>
> Sure you can. Just have a “WantedBy” dependency in your service
> definition on whichever target represents the state you want the script
> to run in,
> e.g. “multi-user.target” for normal system operation.

Figuring out which "target" is the right one, and then how to write
a "WantedBy dependency" would constitute "learning any of the ins and outs
of Systemd". It's way more involved than the process of using
/etc/rc.local is on a SysVInit system.

On Tue, 25 Jun 2024 06:10:03 -0000 (UTC), candycanearter07 wrote:

> Lawrence D'Oliveiro <ldo@nz.invalid> wrote at 05:56 this Tuesday (GMT):
>> On Sun, 19 May 2024 09:37:28 -0000 (UTC), Sebastian wrote:
>>
>>> One thing you can't do with Systemd is write a simple shell script
>>> that runs when the system finishes booting, without having to learn
>>> any of the ins and outs of Systemd.
>>
>> Sure you can. Just have a “WantedBy” dependency in your service
>> definition on whichever target represents the state you want the script
>> to run in,
>> e.g. “multi-user.target” for normal system operation.
>
>
> Or use @reboot in your crontab.

That feature hasn't made it to Debian yet, and the man
page where it is available gives this warning:

Please note that startup, as far as @reboot is concerned, is the time
when the cron(8) daemon startup. In particular, it may be before
some system daemons, or other facilities, were startup. This is due
to the boot order sequence of the machine.
Therefore there's no guarantee at all that this feature can be used
as a replacement for rc.local.

On Tue, 25 Jun 2024 06:10:03 -0000 (UTC), candycanearter07 wrote:

> Lawrence D'Oliveiro <ldo@nz.invalid> wrote at 05:56 this Tuesday (GMT):
>
>> On Sun, 19 May 2024 09:37:28 -0000 (UTC), Sebastian wrote:
>>
>>> One thing you can't do with Systemd is write a simple shell script
>>> that runs when the system finishes booting, without having to learn
>>> any of the ins and outs of Systemd.
>>
>> Sure you can. Just have a “WantedBy” dependency in your service
>> definition on whichever target represents the state you want the script
>> to run in, e.g. “multi-user.target” for normal system operation.
>
> Or use @reboot in your crontab.

In systemd, timer definitions have to do with time, not to do with whether
the system is rebooting. (Though you can define time relative to when the
system starts, if you want.)

This is a cleaner approach than crontab, which is trying to stuff a number
of different functions into an ill-fitting box.

On Tue, 25 Jun 2024 06:27:37 -0000 (UTC), Sebastian Wells wrote:

> On Tue, 25 Jun 2024 05:56:19 -0000 (UTC), Lawrence D'Oliveiro wrote:
>
>> On Sun, 19 May 2024 09:37:28 -0000 (UTC), Sebastian wrote:
>>
>>> One thing you can't do with Systemd is write a simple shell script
>>> that runs when the system finishes booting, without having to learn
>>> any of the ins and outs of Systemd.
>>
>> Sure you can. Just have a “WantedBy” dependency in your service
>> definition on whichever target represents the state you want the script
>> to run in, e.g. “multi-user.target” for normal system operation.
>
> Figuring out which "target" is the right one, and then how to write a
> "WantedBy dependency" would constitute "learning any of the ins and outs
> of Systemd". It's way more involved than the process of using
> /etc/rc.local is on a SysVInit system.

It’s one line of directive in a unit file.

Lawrence D'Oliveiro <ldo@nz.invalid> wrote at 06:55 this Tuesday (GMT):
> On Tue, 25 Jun 2024 06:10:03 -0000 (UTC), candycanearter07 wrote:
>
>> Lawrence D'Oliveiro <ldo@nz.invalid> wrote at 05:56 this Tuesday (GMT):
>>
>>> On Sun, 19 May 2024 09:37:28 -0000 (UTC), Sebastian wrote:
>>>
>>>> One thing you can't do with Systemd is write a simple shell script
>>>> that runs when the system finishes booting, without having to learn
>>>> any of the ins and outs of Systemd.
>>>
>>> Sure you can. Just have a “WantedBy” dependency in your service
>>> definition on whichever target represents the state you want the script
>>> to run in, e.g. “multi-user.target” for normal system operation.
>>
>> Or use @reboot in your crontab.
>
> In systemd, timer definitions have to do with time, not to do with whether
> the system is rebooting. (Though you can define time relative to when the
> system starts, if you want.)
>
> This is a cleaner approach than crontab, which is trying to stuff a number
> of different functions into an ill-fitting box.

oh
--
user <candycane> is generated from /dev/urandom