[systemd-devel] Service not restarting after Condition failed
spider at aanstoot.se
Tue Dec 2 02:24:31 PST 2014
On 01/12/14 01:20, Lennart Poettering wrote:
> On Mon, 24.11.14 20:02, D.S. Ljungmark (spider at aanstoot.se) wrote:
>> Basically, some files (config & certificates) may not exist on a system
>> until it's provisioned properly, something that may take a while ( a few
>> After provisioning, we want the services depending on those file to
>> start automatically.
> I'd be really careful with schemes like this. What is "after
> provisioning" supposed to mean? When precisely do you want to start
> those services? After the first file is in the process of being copied
> in? After all files are copied in and the copying is complete? If so
> how do you detect "all"? How do you detect "copying is complete"?
> .path units can be used for this, but they require a strict regime how
> precisely the files are dropped in, for example atomically via rename,
> and which file is the last one.
Okay, that makes sense. That sort of thing has to be done carefully
anyhow, just to make sure it's a habit.
8362 CB14 98AD 11EF CEB6 FA81 FCC3 7674 449E 3CFC
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 819 bytes
Desc: OpenPGP digital signature
More information about the systemd-devel