Thanks Lennart. Will analyze these options and get back to you.
On Mon, Sep 9, 2024 at 9:54 PM Lennart Poettering
wrote:
> On Mo, 09.09.24 20:15, Srinivas Naik (nivasn...@gmail.com) wrote:
>
> > Hello Everyone,
> > I am exploring systemd-boot counting for HLOS roll back. I am new to
> > systemd-
On Mo, 09.09.24 20:15, Srinivas Naik (nivasn...@gmail.com) wrote:
> Hello Everyone,
> I am exploring systemd-boot counting for HLOS roll back. I am new to
> systemd-boot. As part of boot counting systemd-boot will decrement the
> "tries-left" counter of the selected configuration and tries to boot
Hello Everyone,
I am exploring systemd-boot counting for HLOS roll back. I am new to
systemd-boot. As part of boot counting systemd-boot will decrement the
"tries-left" counter of the selected configuration and tries to boot with
that.
*For example **4.14.11-300.fc27.x86_64+2-1.conf*.
When the devi
On Mo, 09.09.24 13:12, Steve Traylen (steve.tray...@cern.ch) wrote:
>
> Example with lingering **disabled**
>
> root> systemd-run --service-type=exec --user --machine eric@.host
> /usr/bin/sleep 1m
>
> With this
>
> The systemd --user instance is started for Eric and also the sleep is
> start
Example with lingering **disabled**
root> systemd-run --service-type=exec --user --machine eric@.host
/usr/bin/sleep 1m
With this
The systemd --user instance is started for Eric and also the sleep is
started.
However after < 10 seconds or so the transient unit and user service is
a
On Fr, 06.09.24 14:49, Thomas Köller (tho...@koeller.dyndns.org) wrote:
> In 'man systemd.service', the description of ExecCondition= states:
>
> when an ExecCondition= command exits with exit code 1 through 254
> (inclusive), the remaining commands are skipped and the unit is not marked
> as fail
