I'm developing a web server in python that is referenced in the path inside
a systemd service ( server.service ). In the path that points to the
execution of the python file it works without problems but when I make any
changes in this file it is necessary to restart the file in order to get
the
On Tue, Jul 13, 2021 at 4:06 PM Andrei Borzenkov wrote:
>
> On Tue, Jul 13, 2021 at 3:46 PM Manuel Wagesreither
> wrote:
> >
> > Hi all,
> >
> > when I have an udev rule with an ENV{SYSTEMD_WANTS}+="my.service", and
> > another.service with After=systemd-udevd.service, can I at system boot
On Tue, Jul 13, 2021 at 3:46 PM Manuel Wagesreither wrote:
>
> Hi all,
>
> when I have an udev rule with an ENV{SYSTEMD_WANTS}+="my.service", and
> another.service with After=systemd-udevd.service, can I at system boot rely
> on my.service to be already run when another.service starts?
>
No.
On Tue, Jul 13, 2021 at 3:46 PM Manuel Wagesreither
wrote:
> Hi all,
>
> when I have an udev rule with an ENV{SYSTEMD_WANTS}+="my.service", and
> another.service with After=systemd-udevd.service, can I at system boot rely
> on my.service to be already run when another.service starts?
>
No, rule
Hi all,
when I have an udev rule with an ENV{SYSTEMD_WANTS}+="my.service", and
another.service with After=systemd-udevd.service, can I at system boot rely on
my.service to be already run when another.service starts?
Here's the background to the question:
I'm developing an embedded device with
