Hi, It looks sensible to me but...
On 02/07/2017 01:38 PM, Eelco Chaudron wrote: > Currently if either ovsdb-server or ovs-vswitchd is crashing the > daemon is not restarting leaving the system in faulty state. > This patch will detect the daemon crash and will restart the > openvswitch service. > > Here is a (bit to wide) table showing the behavior before and after > the patch. Note that only the Crash behavior has changed: > [..] > --- > diff --git a/rhel/usr_lib_systemd_system_ovs-vswitchd.service > b/rhel/usr_lib_systemd_system_ovs-vswitchd.service > index 01d9cee..39627e9 100644 > --- a/rhel/usr_lib_systemd_system_ovs-vswitchd.service > +++ b/rhel/usr_lib_systemd_system_ovs-vswitchd.service > @@ -9,6 +9,7 @@ PartOf=openvswitch.service > > [Service] > Type=forking > +Restart=on-failure > [...] > diff --git a/rhel/usr_lib_systemd_system_ovsdb-server.service > b/rhel/usr_lib_systemd_system_ovsdb-server.service > index d3d7408..68deace 100644 > --- a/rhel/usr_lib_systemd_system_ovsdb-server.service > +++ b/rhel/usr_lib_systemd_system_ovsdb-server.service > @@ -7,6 +7,7 @@ PartOf=openvswitch.service > > [Service] > Type=forking > +Restart=on-failure Is there any chance to end up in some sort of infinite 'start' loop here if the ovsdb-server or ovs-vswitchd crashes can't be self-healed by a simple restart? -- markos SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
