Date: Mon, 5 Dec 2005 12:30:14 +0000 From: Brian Candler <B.Candler@pobox.com> To: Doug Barton <dougb@FreeBSD.org> Cc: freebsd-current@freebsd.org, Scott Robbins <scottro@nyc.rr.com>, Nicolas Blais <nb_root@videotron.ca> Subject: Re: [rc update] sshd no longer starts at boot Message-ID: <20051205123014.GA90877@uk.tiscali.com> In-Reply-To: <43933227.4050906@FreeBSD.org> References: <200512031609.48962.nb_root@videotron.ca> <200512041135.39342.nb_root@videotron.ca> <20051204174032.GA1304@mail.scottro.net> <200512041303.45970.nb_root@videotron.ca> <43933227.4050906@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Dec 04, 2005 at 10:15:03AM -0800, Doug Barton wrote: > Nicolas Blais wrote: > > >For cupds, after you did the update, did you rm > >/usr/local/etc/rc.d/cups.sh and cp /usr/local/etc/rc.d/cups.sh.sample > >/usr/local/etc/rc.d/cups.sh ? > > A more effective long term solution to that problem is to do: > > cd /usr/local/etc/rc.d > rm cups.sh > ln -s cups.sh.sample cups.sh I presume that if ports are upgraded so that they honour foo_enable from rc.conf, there is no need for them to install foo.sh.sample any more, and they should just install foo.sh instead? That's unless the port *intends* that the user make changes to the startup script directly (in which case, the symlink option given above isn't really appropriate) Regards, Brian.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051205123014.GA90877>