On Fri, Feb 23, 2018 at 1:04 PM, Niels de Vos wrote:
> On Wed, Feb 21, 2018 at 08:25:21PM +0530, Atin Mukherjee wrote:
> > On Wed, Feb 21, 2018 at 4:24 PM, Xavi Hernandez
> wrote:
> >
> > > Hi all,
> > >
> > > currently glusterd sends a SIGKILL to stop gNFS, while all other
> services
> > > are
On Wed, Feb 21, 2018 at 08:25:21PM +0530, Atin Mukherjee wrote:
> On Wed, Feb 21, 2018 at 4:24 PM, Xavi Hernandez wrote:
>
> > Hi all,
> >
> > currently glusterd sends a SIGKILL to stop gNFS, while all other services
> > are stopped with a SIGTERM signal first (this can be seen in
> > glusterd_sv
On Wed, Feb 21, 2018 at 4:24 PM, Xavi Hernandez wrote:
> Hi all,
>
> currently glusterd sends a SIGKILL to stop gNFS, while all other services
> are stopped with a SIGTERM signal first (this can be seen in
> glusterd_svc_stop() function of mgmt/glusterd xlator).
>
> The question is why it cannot
Hi all,
currently glusterd sends a SIGKILL to stop gNFS, while all other services
are stopped with a SIGTERM signal first (this can be seen in
glusterd_svc_stop() function of mgmt/glusterd xlator).
The question is why it cannot be stopped with SIGTERM as all other
services. Using SIGKILL blindly
