From owner-freebsd-questions@FreeBSD.ORG Thu May 7 18:51:09 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0D258106566B for ; Thu, 7 May 2009 18:51:09 +0000 (UTC) (envelope-from mel.flynn+fbsd.questions@mailing.thruhere.net) Received: from mailhub.rachie.is-a-geek.net (rachie.is-a-geek.net [66.230.99.27]) by mx1.freebsd.org (Postfix) with ESMTP id D15C88FC15 for ; Thu, 7 May 2009 18:51:08 +0000 (UTC) (envelope-from mel.flynn+fbsd.questions@mailing.thruhere.net) Received: from sarevok.dnr.servegame.org (mailhub.rachie.is-a-geek.net [192.168.2.11]) by mailhub.rachie.is-a-geek.net (Postfix) with ESMTP id D32547E837; Thu, 7 May 2009 10:51:07 -0800 (AKDT) From: Mel Flynn To: freebsd-questions@freebsd.org Date: Thu, 7 May 2009 20:51:06 +0200 User-Agent: KMail/1.11.2 (FreeBSD/8.0-CURRENT; KDE/4.2.2; i386; ; ) References: <560f92640905071057v7d298a68l680182144cc8898f@mail.gmail.com> In-Reply-To: <560f92640905071057v7d298a68l680182144cc8898f@mail.gmail.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200905072051.06511.mel.flynn+fbsd.questions@mailing.thruhere.net> Cc: Nerius Landys Subject: Re: Run script on boot, as ordinary user X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 May 2009 18:51:09 -0000 On Thursday 07 May 2009 19:57:03 Nerius Landys wrote: > So there's cron. Is there anything that lets an ordinary user start > his/her programs at bootup of the system? And then run a script when > the system is shutting down? I'm familiar with /etc/rc.d/, but that's > not really what I'm looking for. You sure? You can simply write an rc.d script that iterates through /home/*/rc.d/* and invokes each enabled script in there as the user, using su or sudo. This will cleanly shutdown stuff for them. Whether they *should* be running their own instances is an entirely different question. VirtualHost can do a lot and with mod_vhost_alias you simplify the maintenance, while maintaining several instances complicates it. -- Mel