RFC Systemd Service Restart Policy

[Andrew Jeffery]

On Wed, 2017-09-06 at 12:50 -0700, Vernon Mauery wrote:
> > I have some maintainability concerns with trying to pick specific
> > services to cause a BMC reboot.  Maybe it would be better to define a
> > default  that all services cause a BMC reboot, then pick specific
> > one’s that would not result in a reboot?  Or maybe it’s best to never
> > reboot, and just let the system owners manage it?  Thoughts
> > appreciated.
> 
> I would prefer that we have a set core (such as dbus and the mapper) 
> that are terminal faults (maybe even without retries) and then assume 
> that everything else can be restarted nicely. If something cannot be 
> restarted nicely, there should be a really good reason for that and that 
> service's unit file can specify something other than the defaults to 
> change its behavior.
> 
> This is a Linux system; in the ideal world, it should only need to be 
> restarted for firmware updates. All other faults should be recoverable. 
> Ideal world aside, individual services that can only be recovered with a 
> reboot can handle that case without adjusting the global default.

I second Vernon's position.

Andrew
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: This is a digitally signed message part
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20170907/b5f8da11/attachment.sig>