From owner-freebsd-ports@FreeBSD.ORG Wed Apr 4 22:47:27 2007 Return-Path: X-Original-To: ports@freebsd.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3585616A403 for ; Wed, 4 Apr 2007 22:47:27 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 20A7513C45B for ; Wed, 4 Apr 2007 22:47:27 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 008171A4D8E; Wed, 4 Apr 2007 15:47:27 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 39F3151438; Wed, 4 Apr 2007 18:47:26 -0400 (EDT) Date: Wed, 4 Apr 2007 18:47:26 -0400 From: Kris Kennaway To: Kevin Downey Message-ID: <20070404224725.GA65803@xor.obsecurity.org> References: <4420D14C.4020503@FreeBSD.org> <4420D279.2090405@FreeBSD.org> <1d3ed48c0704041359p378ac1d0i5296525857953382@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="envbJBWh7q8WU6mo" Content-Disposition: inline In-Reply-To: <1d3ed48c0704041359p378ac1d0i5296525857953382@mail.gmail.com> User-Agent: Mutt/1.4.2.2i Cc: ports@freebsd.org Subject: Re: Switch to using rc.d for local packages is premature for RELENG_6 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Apr 2007 22:47:27 -0000 --envbJBWh7q8WU6mo Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 04, 2007 at 01:59:32PM -0700, Kevin Downey wrote: > On 3/21/06, Maxim Sobolev wrote: > >I have just realized that maybe the best approach to address this > >problem would be not reverting the change in question, but making > >find_local_scripts_new() more strict, so that only those local rc.d > >scripts that have been explicitly marked by maintainer as fully > >rc.d-safe are handled in a new way. Checking for '^# PROVIDE:' doesn't > >really work reliably. > > > >-Maxim > > > >Maxim Sobolev wrote: > >> Hi guys, > >> > >> As part of testing how well some of our products work with latest > >> RELENG_6, I have make a new build and found that lot of important > >> services (for example PostgreSQL, Apache) doesn't start up (despite > >> having respective xxx_enable entries in /etc/rc.conf) when installed > >> from the freshly updated ports tree onto a clean, freshly updated > >> RELENG_6 system. This is very bad, considering how close to release are > >> we and how much FreeBSD users rely on those services to work OOB. > >> > >> I would expect them to be really pissed off when lot of important > >> services just don't work after upgrading their server from 6.0 to 6.1 = or > >> after installing it from install cd. This is apparently caused by the > >> fact that lot of rc.d scripts in /usr/local/etc/rc.d are newstyle one > >> now (sufficiently newstyle to pass find_local_scripts_new check), but > >> few of them were actually tested to work correctly in fully rc.d > >> environment. > >> > >> Therefore, I think that the RELENG_6 should be reverted to using old > >> stuff and it should be left for 7.x tree. > >> > >> Regards, > >> > >> Maxim >=20 > Which apache port? I have been using www/apache20 for sometime now on > a machine tracking RELENG_6_2. I use 'apache2_enable=3D"YES"' in > /etc/rc.conf and it starts and runs fine. Perhaps I am > misunderstanding your complaint. Note that you're replying to a mail from a year ago which was probably coughed up by someone's borken mail server. Kris --envbJBWh7q8WU6mo Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGFCr9Wry0BWjoQKURAub3AJ9TrDrezRYF++RV6xmbBZ/egzw0ygCgzAu1 pLznp8Xmg4PCjg+GlZuUeoQ= =ySMI -----END PGP SIGNATURE----- --envbJBWh7q8WU6mo--