[Bug 208132] releng/10.3 (RC3) strange SIGTERM behaviour
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Sat Mar 19 03:56:39 UTC 2016
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208132
Bug ID: 208132
Summary: releng/10.3 (RC3) strange SIGTERM behaviour
Product: Base System
Version: 10.3-BETA2
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: bin
Assignee: freebsd-bugs at FreeBSD.org
Reporter: John.Marshall at riverwillow.com.au
FreeBSD 10.3-RC3 #0 r297005: Fri Mar 18 21:14:17 AEDT 2016 i386
FreeBSD 10.3-RC3 #0 r297005: Fri Mar 18 16:13:17 AEDT 2016 amd64
As reported to -stable at ...
I've just upgraded two local servers from 10.3-RC2 to 10.3-RC3. One is
i386 (Pentium 4) with 1.5GB memory; the other is amd64 (Xeon E5 x 2)
with 16GB. Something seems to be swallowing SIGTERM sometimes. I've
never seen this before.
rc scripts and service(8) hang when trying to stop some services. If I
break out of the script or service command (via ctrl-C) and invoke
kill(1), passing the relevant PID, the shell prompt returns immediately
but the process doesn't terminate. Sending SIGKILL to the process via
kill(1) does its job.
I am seeing this with:
squid (on both servers)
ircd-ratbox (on both servers)
git_daemon
I am not seeing this (all seems normal) with:
cupsd
sendmail (on both servers)
Looking back through the commits between -RC2 and -RC3, I've decided to try
backing out r296976 to see if that may be related. Building now. Will take
several hours.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-bugs
mailing list