On Thu, Sep 06, 2018 at 10:53:29AM -0700, Guru Shetty wrote:
> On Thu, 6 Sep 2018 at 10:45, Ben Pfaff wrote:
>
> > Linux has an idea of process name that is visible in /proc/$pid/comm. This
> > is "ovs-vswitchd" for a freshly started ovs-vswitchd process. When the
> > monitor code restarted a
On Thu, 6 Sep 2018 at 10:45, Ben Pfaff wrote:
> Linux has an idea of process name that is visible in /proc/$pid/comm. This
> is "ovs-vswitchd" for a freshly started ovs-vswitchd process. When the
> monitor code restarted a crash child, it changed it to the empty string.
> This confused the
Linux has an idea of process name that is visible in /proc/$pid/comm. This
is "ovs-vswitchd" for a freshly started ovs-vswitchd process. When the
monitor code restarted a crash child, it changed it to the empty string.
This confused the daemon_is_running check in ovs-lib.in, which checks
comm.
