Leon Fauster wrote on 02/09/2021 15:39:
On 02.09.21 15:12, Andrei Borzenkov wrote:
On 02.09.2021 15:10, Leon Fauster wrote:
On 02.09.21 08:00, Andrei Borzenkov wrote:
On 02.09.2021 01:19, Leon Fauster wrote:
Example:
a@.service
b.service
a@.service is started as a@host1.service and
On 02.09.21 15:12, Andrei Borzenkov wrote:
On 02.09.2021 15:10, Leon Fauster wrote:
On 02.09.21 08:00, Andrei Borzenkov wrote:
On 02.09.2021 01:19, Leon Fauster wrote:
Example:
a@.service
b.service
a@.service is started as a@host1.service and b.service must be started
after a@host1.service
On 02.09.2021 15:10, Leon Fauster wrote:
> On 02.09.21 08:00, Andrei Borzenkov wrote:
>> On 02.09.2021 01:19, Leon Fauster wrote:
>>> Example:
>>>
>>> a@.service
>>> b.service
>>>
>>> a@.service is started as a@host1.service and b.service must be started
>>> after a@host1.service but the unit will
On 02.09.21 08:00, Andrei Borzenkov wrote:
On 02.09.2021 01:19, Leon Fauster wrote:
Example:
a@.service
b.service
a@.service is started as a@host1.service and b.service must be started
after a@host1.service but the unit will be differently parameterized
(depended of the region). So I want to
On 02.09.2021 01:19, Leon Fauster wrote:
> Dear list,
>
> following requirement exists here (systemd-239 installed):
>
> Applying a "Requires" statement with an instantiated service.
>
> Example:
>
> a@.service
> b.service
>
> a@.service is started as a@host1.service and b.service must be
Dear list,
following requirement exists here (systemd-239 installed):
Applying a "Requires" statement with an instantiated service.
Example:
a@.service
b.service
a@.service is started as a@host1.service and b.service must be started
after a@host1.service but the unit will be differently
