From owner-freebsd-bugs Thu Jul 23 11:50:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA09662 for freebsd-bugs-outgoing; Thu, 23 Jul 1998 11:50:32 -0700 (PDT) (envelope-from owner-freebsd-bugs@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 LAA09655 for ; Thu, 23 Jul 1998 11:50:31 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.8/8.8.5) id LAA10861; Thu, 23 Jul 1998 11:50:01 -0700 (PDT) Date: Thu, 23 Jul 1998 11:50:01 -0700 (PDT) Message-Id: <199807231850.LAA10861@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.ORG From: Thomas David Rivers Subject: Re: conf/7366: /tmp/.X* not removed by /etc/rc if clear_tmp_enable != YES Reply-To: Thomas David Rivers Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR conf/7366; it has been noted by GNATS. From: Thomas David Rivers To: rivers@dignus.com, smoergrd@oslo.geco-prakla.slb.com Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: conf/7366: /tmp/.X* not removed by /etc/rc if clear_tmp_enable != YES Date: Thu, 23 Jul 1998 12:07:11 -0400 (EDT) > > Thomas David Rivers writes: > > if clear_tmp_enable is YES, then /etc/rc kindly removes > > /tmp/.X*-lock and /tmp/.X11-unix/* > > > > But - if clea_tmp_enable isn't yes; then these don't get > > removed; causing X11 startup to fail on reboot. > > These files shouldn't be present if X was shut down properly (CTRL-R > in xdm, ALT-CTRL-BACKSPACE, kill -TERM, you name it). If X did not > shut down properly (kernel panic, power outage, kill -KILL, X server > bug), the machine probably needs human intervention anyway. > > DES > -- > Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.com > Well - isn't that simply drawing "the line" at X. For example, we go ahead and do fsck after a power outage, should we not do that? Exactly what things should we do and what things should we not do? Personally, I'd like X to come back if it can... I'll also add that if human intervention is needed, the machine drops to single-user state... so the human intervention will be there... In a situation where FreeBSD is used for many machines; I'd hate to have to visit hundreds of machines just because of a power outage (or, worse yet, instruct users to "become root and remove those files, then reboot...") - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message