Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 26 Jan 2015 23:56:55 +0100
From:      "Dr. Peter Voigt" <pvoigt@uos.de>
To:        freebsd-ports@freebsd.org
Subject:   Re: www/squid does not shutdown via rc
Message-ID:  <20150126235655.5d371915@kirk.drpetervoigt.private>
In-Reply-To: <20150126212514.56c8f0866f1d63bb98089dd0@mimar.rs>
References:  <20150126152433.52f07277f377f9396b65c9a8@mimar.rs> <20150127.002919.335530336.yasu@utahime.org> <20150126163934.32f199d43d86a70b00dd7e4a@mimar.rs> <20150127.010539.230444205.yasu@utahime.org> <54C6695E.6010704@freebsd.org> <20150126212514.56c8f0866f1d63bb98089dd0@mimar.rs>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 26 Jan 2015 21:25:14 +0100
Marko Cupa=C4=87 <marko.cupac@mimar.rs> wrote:

> On Mon, 26 Jan 2015 16:20:46 +0000
> Matthew Seaman <matthew@freebsd.org> wrote:
>=20
> > >> > Also, is there a chance they will be pushed to freebsd-update?
> >=20
> > No.  Unless these are either security fixes or fixes for a major
> > regression (which this is not) in 10.1-RELEASE, then they won't be
> > applied to that branch.
>=20
> From OS point of view, this could be indeed seen as minor regression.
>=20
> But please consider server admin's point of view:
> - squid33 had latest release on 2014-08-27
> - squid33 has been scheduled for expiration on 2015-01-31, but was
>   extended to 2015-05-31 because of ntlm_auth issue in squid34
> - squid34 does not run on 10.1-RELEASE-pX
> - 10.2-RELEASE is not likely to be before 2015-05-31
>=20
> Which means that pkg installs of latest squid (www/squid34) will be
> useless on latest FreeBSD release (10.1-RELEASE) for a long time.
>=20
> > They will, however, be in the next release cut from stable/10, which
> > will be 10.2-RELEASE, and presumably in releases from other branches
> > from now on.
> >=20
> > Your best recourse at the moment is to manually patch the kernel
> > sources and build yourself a custom kernel on the affected machines.
>=20
> I was looking forward to avoid it. Perhaps I'm succumbing to
> conformism.

I am suffering from the same 10.1/Squid problem for some time and I am
glad stumbling across this thread. Fortunately Squid is running stable
apart from this shutdown issue.

To me it looks like a serious kernel issue and I can hardly believe it
will not be fixed in the 10.1-RELEASE.

It is quite an effort to compile, manually patch and install a custom
kernel, if you aren't too experienced like I am. I have only managed
building the GENERIC kernel so far as part of the build world process
when upgrading to 10.1.

Regards,
Peter



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150126235655.5d371915>