Date: Thu, 31 Mar 2016 19:45:43 +0200 From: Christoph Brinkhaus <c.brinkhaus@t-online.de> To: =?iso-8859-1?Q?Jos=E9_Garc=EDa?= Juanino <jjuanino@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: fetchmail service do not stop cleanly;it ignores TERM signal Message-ID: <20160331174543.GA40301@esprimo.local> In-Reply-To: <CAAVO5%2BL42sd_Ttm6XzpaqoLtkEFw2QiAq2JTk9qWraoUy4ZD3Q@mail.gmail.com> References: <CAAVO5%2BL42sd_Ttm6XzpaqoLtkEFw2QiAq2JTk9qWraoUy4ZD3Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Mar 29, 2016 at 11:34:29PM +0200, Jos=E9 Garc=EDa Juanino wrote: > Hi, Hello Jos=E9, >=20 > I have noticed that fetchmail service hangs in stop phase. I have the > following in rc.conf: >=20 > fetchmail_enable=3D"YES" > fetchmail_users=3D"juanino" > fetchmail_juanino_polling_interval=3D60 >=20 >=20 > When I have to restart the service, it hangs forever: >=20 > # service fetchmail restart > =3D=3D=3D> fetchmail user: juanino > Stopping fetchmail. > Waiting for PIDS: 9284 >=20 > The only way to stop the service is to send the INT (or KILL) signal: >=20 > # pkill -INT fetchmail >=20 > It seems to be that is ignoring TERM (or HUP) signal. I have faced the same situation. >=20 > Ugly workaround: >=20 > echo "sig_stop=3D\"INT\" " > /etc/rc.conf.d/fetchmail >=20 > to force the INT signal instead of TERM. >=20 > The same issue applies to some other services as polipo. It is not > clear for me if this issue is freebsd specific. Any idea? Some days ago I have seen a related report about 10.3 on the stable mailing list. It has been reported that some services to not stop properly and the enabling of SAVESIGVEC has been detected as a likely trigger. If I remember correctly the proposal was to disable SAVESIGVEC until the real root cause is fixed. may be in the current kernel sources it is already fixed or SAVESIGVEC is re-disabled. I have digged a little bit and found SAVESIGVEC defined in /usr/src/bin/csh/config_p.h. I have simply commented that out=20 and made a new world and a new kernel. This is my current work arround. As said above I am not sure about the current situation. I hope this information helps. Kind regards, Christoph
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160331174543.GA40301>