Date: Thu, 6 Jul 2000 16:34:19 -0400 (EDT) From: Robert Watson <rwatson@FreeBSD.org> To: Sheldon Hearn <sheldonh@uunet.co.za> Cc: Brian Somers <brian@Awfulhak.org>, Thomas Gellekum <tg@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/etc rc.shutdown Message-ID: <Pine.NEB.3.96L.1000706163257.52496E-100000@fledge.watson.org> In-Reply-To: <12690.962870098@axl.ops.uunet.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
So, generally, my observation for rc.d scripts was that previously, they
never even looked at the arguments, so running (whatever) stop will
actually run additional copies of the service on shutdown, if
/usr/local/etc/rc.d is not updated. Is this correct?
I.e., if I shutdown postgresql, but then run shutdown -p NOW, it will
restart postgresql, then kill it?
On Thu, 6 Jul 2000, Sheldon Hearn wrote:
>
>
> On Wed, 05 Jul 2000 19:58:08 +0100, Brian Somers wrote:
>
> > > Now that the scripts in our ports support this, call the scripts
> > > in ${local_startup} with the `stop' option on shutdown.
> >
> > Is this not going to cause confusion as people update /etc and don't
> > update /usr/local/etc/rc.d ?
>
> Confusion, certainly. Disaster, no. :-)
>
> Basically, a HEADS UP to the -current mailing list will reduce the
> number of posts complaining about harmless error messages, but they are
> harmless nonetheless.
>
> Ciao,
> Sheldon.
>
>
Robert N M Watson
robert@fledge.watson.org http://www.watson.org/~robert/
PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1
TIS Labs at Network Associates, Safeport Network Services
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1000706163257.52496E-100000>