On 13 May 2016 at 00:04, Terry Burton wrote:
> I have a process (ISC DHCP) that has no reload or soft restart
> mechanism. The only way to "reload" it is a stop and start.
>
> I understand systemd's design choice of maintaining a clear
> distinction between reload an
Hi,
I have a process (ISC DHCP) that has no reload or soft restart
mechanism. The only way to "reload" it is a stop and start.
I understand systemd's design choice of maintaining a clear
distinction between reload and restart based on whether the service is
interrupted or not, so it's clear that
On 26 February 2016 at 14:14, Mantas Mikulėnas wrote:
> On Fri, Feb 26, 2016 at 3:06 PM, Terry Burton wrote:
>> I have an application that in part consists of a number of instances
>> of similar processes (each with their own configuration and bound to
>> neighbouring ports
Hi,
I have an application that in part consists of a number of instances
of similar processes (each with their own configuration and bound to
neighbouring ports, etc.)
I could create a .service file for each instance from a template but
I'm wondering whether systemd has some built-in way of handl