From owner-freebsd-ports Mon Sep 7 14:00:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA04416 for freebsd-ports-outgoing; Mon, 7 Sep 1998 14:00:05 -0700 (PDT) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA04357 for ; Mon, 7 Sep 1998 14:00:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.8/8.8.5) id OAA00173; Mon, 7 Sep 1998 14:00:01 -0700 (PDT) Date: Mon, 7 Sep 1998 14:00:01 -0700 (PDT) Message-Id: <199809072100.OAA00173@freefall.freebsd.org> To: freebsd-ports@FreeBSD.ORG From: Dom Mitchell Subject: Re: ports/7844: rm -f /var/run in /etc/rc causes error in boot with sudo Reply-To: Dom Mitchell Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR ports/7844; it has been noted by GNATS. From: Dom Mitchell To: nodog@mail.utexas.edu Cc: freebsd-gnats-submit@freebsd.org Subject: Re: ports/7844: rm -f /var/run in /etc/rc causes error in boot with sudo Date: Mon, 07 Sep 1998 08:18:44 +0100 nodog@mail.utexas.edu writes: > >Synopsis: rm -f /var/run in /etc/rc causes error in boot with sudo Update your version of /etc/rc to the latest one. Also install the latest version of the sudo port. Anything that installs stuff in /var/run can expect it to get blown away and will have to recreate it on boot. Xemacs is another good example. -- ``Quick, beam that cheese to sickbay!'' -- BT To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message