From owner-freebsd-current@FreeBSD.ORG Sun Dec 4 02:11:13 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A785016A41F for ; Sun, 4 Dec 2005 02:11:13 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mail2.fluidhosting.com [204.14.90.12]) by mx1.FreeBSD.org (Postfix) with SMTP id 266A143D45 for ; Sun, 4 Dec 2005 02:11:13 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 2910 invoked by uid 399); 4 Dec 2005 02:11:07 -0000 Received: from localhost (HELO ?192.168.0.5?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 4 Dec 2005 02:11:07 -0000 Message-ID: <43925039.3060305@FreeBSD.org> Date: Sat, 03 Dec 2005 18:11:05 -0800 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5 (X11/20051203) MIME-Version: 1.0 To: Nicolas Blais References: <200512031609.48962.nb_root@videotron.ca> In-Reply-To: <200512031609.48962.nb_root@videotron.ca> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, asa@agava.com Subject: Re: [rc update] sshd no longer starts at boot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Dec 2005 02:11:13 -0000 Nicolas Blais wrote: > After a cvsup/buildworld today, sshd (and cupsd, reported in PR ports/89892) > will no longer start at boot on my system. There was a problem with the cups.sh startup script that is only apparent relative to the new rcorder stuff in HEAD. The cups.sh script has the PROVIDE label in it for NetBSD's purposes, but from our standpoint, it's still an "old style" startup script. Since the new code in HEAD looks for this label, it was trying to treat the script in the new way, and that caused the boot to fail. I just committed the the simplest possible fix, removing that line from the startup script. If the maintainer (cc'ed) has a better idea, that's not a problem, but since I use cups as well, I knew this was going to be a problem, and I wanted to make sure this didn't bite any more people than absolutely necessary. Doug -- This .signature sanitized for your protection