From owner-freebsd-questions@FreeBSD.ORG Mon May 24 11:51:34 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C2E2016A4CE for ; Mon, 24 May 2004 11:51:34 -0700 (PDT) Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.198.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id B0DFC43D41 for ; Mon, 24 May 2004 11:51:34 -0700 (PDT) (envelope-from apeiron@comcast.net) Received: from prophecy.velum (pcp08490587pcs.levtwn01.pa.comcast.net[68.83.169.224]) by comcast.net (rwcrmhc11) with SMTP id <20040524185120013001742ve> (Authid: apeiron@comcast.net); Mon, 24 May 2004 18:51:20 +0000 Date: Mon, 24 May 2004 14:51:18 -0400 From: Christopher Nehren To: Kirk Strauser , Gerard Seibert Message-ID: <20040524185118.GB53827@prophecy.dyndns.org> References: <877jv28utv.fsf@strauser.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="WhfpMioaduB5tiZL" Content-Disposition: inline In-Reply-To: <877jv28utv.fsf@strauser.com> User-Agent: Mutt/1.5.6i cc: freebsd-questions@freebsd.org Subject: Re: Proper way to start a program at log-on X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 May 2004 18:51:34 -0000 --WhfpMioaduB5tiZL Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, May 23, 2004 at 21:42:04 EDT, Kirk Strauser scribbled these curious markings: > Nope, that's fine. Of course, you *could* just leave it running forever,= if > you really wanted to. No, it is anything _but_ fine. If Gerard makes a mistake with mergemaster, his shutdown changes are lost. The proper way to do so is,=20 as others have suggested, to place a script in /usr/local/etc/rc.d/. If=20 you want to do it completely properly, using rcNG (with rc.subr and rc.conf) is the way to go. Generally speaking, any well-behaved port leaves /etc alone completely.=20 The only change that you should ever have to make to anything in /etc=20 is a ${portname}_enable=3D"YES" in /etc/rc.conf, if the port uses rcNG.=20 Having third-party software muck around in /etc (especially things like a shutdown script) is a Linux prob ... er ... methodology. I'd hate to think of what would happen if an entry in /etc/rc.shutdown was incorrect, and caused the script to fail, thus not returning 0... --=20 I abhor a system designed for the "user", if that word is a coded pejorative meaning "stupid and unsophisticated". -- Ken Thompson - Unix is user friendly. However, it isn't idiot friendly. - Please CC me in all replies, even if I'm on the relevant list(s). --WhfpMioaduB5tiZL Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAskQmk/lo7zvzJioRAufbAKC4jwmSsudjjfQ5tjsILwZeiycQnQCgqf1S cBhnpB7xk/tIEIq7qqeSrEw= =pmS3 -----END PGP SIGNATURE----- --WhfpMioaduB5tiZL--