Re: In the systemd scheme, where should startup/stop scripts for things systemd can't handle go?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



On Sat, Jul 28, 2012 at 12:39 AM, C Anthony Risinger <anthony@xxxxxxx> wrote:
> also note that you likely want to simply run the service differently
> that you had previously.
>
> for example, i modify several .service files -- even ones that are
> shipped upstream -- because they are pointlessly configured as
> `forking` when they could be much better integrated (ddclient, dhcpd,
> hostapd, SEVERAL unfortunately) ...

They are often configured as Type=forking because they only fork after
performing some form of initialization (e.g. dhcpcd [the client] might
fork only after actually receiving a DHCP lease), and systemd will
interpret this as a signal that the service has now started, without
having to add systemd-specific sd_notify().

-- 
Mantas Mikulėnas


[Index of Archives]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux