From owner-freebsd-ports@FreeBSD.ORG Mon Jan 26 22:42:21 2015 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 14DA7216 for ; Mon, 26 Jan 2015 22:42:21 +0000 (UTC) Received: from mail-lb0-x22e.google.com (mail-lb0-x22e.google.com [IPv6:2a00:1450:4010:c04::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 83382CD5 for ; Mon, 26 Jan 2015 22:42:20 +0000 (UTC) Received: by mail-lb0-f174.google.com with SMTP id f15so10185011lbj.5 for ; Mon, 26 Jan 2015 14:42:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=vIxoyp+hadsJcfvhPN2ssb29UQ6VY48NGd2gRVP+Sp4=; b=byZas/LkiqoaFp0WksvfF49jMZYqw9ZNARjjnvkf03e7lBw1FDiqyerlX5nUAmnabM XY0IfVVfs3phXqu5uvPlSVUFMS6uEKa6FafACp/pbK1PJAsHmh0Xkk1HdrtvDj/uFhGO ndgnimJDtL+FF+QOTxmV0V9T04OBz/jCWR3ICHBCA2FTDtmezgt4HIKOu7IKfUXqe3eI bilCDWiiDjvoWjNBDctlStoLyaR2QdHhg/2mu8aRfK96W3NtFnUDO8jQ8GxsaofBOM04 HmaV2UgtsWI9fcPXVotXtvh4migA6HYZerZe/ZITcchrHtP0Hta4e0yd6ruZTrCqpsXz WbHg== MIME-Version: 1.0 X-Received: by 10.112.44.230 with SMTP id h6mr702852lbm.98.1422312138582; Mon, 26 Jan 2015 14:42:18 -0800 (PST) Received: by 10.25.21.14 with HTTP; Mon, 26 Jan 2015 14:42:18 -0800 (PST) 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> Date: Mon, 26 Jan 2015 14:42:18 -0800 Message-ID: Subject: Re: www/squid does not shutdown via rc From: Nick Rogers To: =?UTF-8?B?TWFya28gQ3VwYcSH?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-ports@freebsd.org" X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jan 2015 22:42:21 -0000 On Mon, Jan 26, 2015 at 12:25 PM, Marko Cupa=C4=87 w= rote: > On Mon, 26 Jan 2015 16:20:46 +0000 > Matthew Seaman wrote: > > > >> > Also, is there a chance they will be pushed to freebsd-update? > > > > 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. > > From OS point of view, this could be indeed seen as minor regression. > > 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 > > Which means that pkg installs of latest squid (www/squid34) will be > useless on latest FreeBSD release (10.1-RELEASE) for a long time. > I'm also now having to patch my 10.1-RELEASE kernel to get around this problem. Sounds like a fairly serious regression to me as well, at least for squid users. > > 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. > > > > Your best recourse at the moment is to manually patch the kernel source= s > > and build yourself a custom kernel on the affected machines. > > I was looking forward to avoid it. Perhaps I'm succumbing to conformism. > -- > Marko Cupa=C4=87 > https://www.mimar.rs > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" >