I've been trying out the Restart= option in some of my own systemd
service unit files - which appears to work fine
However, I notice that this option is only used in a few OS provided
service unit files - and was wondering about the wisdom of adding this
capability to other daemons/services? (e
Although not on CentOS, I've been forced to use it with serial-getty@.service
(even after enabling and starting it) to get the OS to display a console prompt
after an OS upgrade. In this case I used Restart=on-success and RestartSec=5
(the latter an arbitrary value) because agetty exited after
On 27/06/2017 00:49, James A. Peltier wrote:
Bind does not have a method to do multi-master replication. All updates must
be done via an intermediary service (database).
In our case, we've used containers and Consul for providing a highly available
DNS service. A container will fire up and r
On Wed, Jun 28, 2017 at 12:54:43PM +, James Pearson wrote:
> However, I notice that this option is only used in a few OS provided
> service unit files - and was wondering about the wisdom of adding this
> capability to other daemons/services? (e.g. chronyd or ntpd, crond,
> rpcbind, etc, etc
Matthew Miller wrote:
>
> I think it's a good idea. We just haven't had a push (either at
> Red Hat internally or Fedora upstream) to go through and enable this
> everywhere it makes sense. The guidelines do recommend it:
>
> https://fedoraproject.org/wiki/Packaging:Systemd#Automatic_restarting
>
>
5 matches
Mail list logo
