* flock leaves the lock file behind so you'd need some type of
cleanup in case you really want the jobs to be trace-free. This is
not as trivial is it might seem, e.g. you cannot do it from the
service units themselves in `ExecStartPost=` or similar.
An
ExecStartPost=-/usr/bin/flock -F /path/to/
* flock leaves the lock file behind so you'd need some type of
cleanup in case you really want the jobs to be trace-free. This is
not as trivial is it might seem, e.g. you cannot do it from the
service units themselves in `ExecStartPost=` or similar.
An
ExecStartPost=-/usr/bin/flock -F /path/to/
exactly for this you would use a flock(1) in your .service.
Thanks for the hint, didn't have that in mind. So you're suggesting
something
like this?
# service-a.service
# (...)
[Service]
ExecStart=/usr/bin/flock -F /var/lock/resource.lock
/usr/bin/service-a
# service-b.
Dear [systemd-devel],
imagine you've got multiple services that perform system housekeeping
tasks, all triggered by .timer units. These services all happen to use
a specific resource (e.g. the system package manager) so they must not
be run in parallel, but they all need to be run.
Is there a sy
Dear list members,
I'm having some strange issues with systemd bootup being blocked by
waiting for devices that do already exist. The situation is a bit
complicated, but I'll try to be as clear as possible.
I have four encrypted partitions (dm-crypt, LUKS) on four different
disks set up by /etc/c
