On Tue, 2017-05-30 at 18:07 +, Moravec, Stanislav (ERT) wrote:
> OK. Understood, thanks much!
> We'll try to follow up on using some parent process (xinetd or something like
> that).
BTW your problem description wasn't very clear. Is your specific
problem case about socket activation of
On Tue, 30 May 2017 11:57:00 -0400,
Pietro Paolini wrote:
> Hi everybody,
>
> I am trying to configure my systemd to run my service *after* the
> timesyncd service is synchronized with the NTP server, unfortunately
> adding the "After=time-sycd.target" does not work as I can't see any
> change in
On Tue, May 30 2017, Michael Biebl wrote:
> 2017-05-30 0:19 GMT+02:00 NeilBrown :
>
>> +.B bg
>> +option is not supported, and may be stripped from the option list.
>
> Either systemd is updated to actually strip the bg option or not. The
> documentation should reflect that.
> I
2017-05-30 0:19 GMT+02:00 NeilBrown :
> +.B bg
> +option is not supported, and may be stripped from the option list.
Either systemd is updated to actually strip the bg option or not. The
documentation should reflect that.
I don't think we should be vague about this, as it would
2017-05-30 10:55 GMT+02:00 NeilBrown :
> On Tue, May 30 2017, Michael Biebl wrote:
>
>> 2017-05-30 0:19 GMT+02:00 NeilBrown :
>>
>>> +.B bg
>>> +option is not supported, and may be stripped from the option list.
>>
>> Either systemd is updated to actually strip the
On Tue, 30.05.17 08:19, NeilBrown (ne...@suse.com) wrote:
>
> Systemd does not, and will not, support "bg" correctly.
> It has other, better, ways to handle "background" mounting.
>
> Explain this.
>
> See also https://github.com/systemd/systemd/issues/6046
>
> Signed-off-by: NeilBrown
On Tue, 30.05.17 11:15, Michael Biebl (mbi...@gmail.com) wrote:
> 2017-05-30 10:55 GMT+02:00 NeilBrown :
> > On Tue, May 30 2017, Michael Biebl wrote:
> >
> >> 2017-05-30 0:19 GMT+02:00 NeilBrown :
> >>
> >>> +.B bg
> >>> +option is not supported, and may be
OK. Understood, thanks much!
We'll try to follow up on using some parent process (xinetd or something like
that).
Eventually however, this is a limitation that prohibits using systemd as full
init
replacement and should be addressed in some way sooner or later, I guess.
Thanks again
Stan
Hi everybody,
I am trying to configure my systemd to run my service *after* the timesyncd
service is synchronized with the NTP server, unfortunately adding the
"After=time-sycd.target" does not work as I can't see any change in the
behavior - my service is started immediately anyway.
Reading
Uoti,
yes, it was about Redhat/Centos7 authd (rfc 1413) service, so it was
the latter - one child process per each connection:
auth@.service:[Unit]
auth@.service:Description=Authd Ident Protocol Requests Server
auth@.service:After=local-fs.target
auth@.service:
auth@.service:[Service]
10 matches
Mail list logo