Date: Fri, 17 Mar 2000 18:07:05 +0200 From: Yiorgos Adamopoulos <adamo@dblab.ece.ntua.gr> To: Vivek Khera <khera@kciLink.com> Cc: freebsd-stable@FreeBSD.ORG Subject: Re: How to force remote reboot of 3.4-Release? Message-ID: <200003171607.e2HG75Y91631@dblab.ece.ntua.gr> In-Reply-To: <14546.20672.830493.146521@onceler.kcilink.com> References: <14546.20672.830493.146521@onceler.kcilink.com> <200003170213.KAA26062@netrinsics.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Message-ID: <EXECMAIL.1000317180705.A@mbazo.dblab.ece.ntua.gr> Priority: NORMAL X-Mailer: Execmail for Win32 Version 5.0.1 Build (55) MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" On Fri, 17 Mar 2000 10:35:28 -0500 (EST) Vivek Khera <khera@kciLink.com> wrote: > MR> possible to exploit any of the other resource starvation features in > MR> 3.4-Release to force a reboot? Getting access to the server is a big > MR> pain in the rear, so I'd like to avoid the trip if at all possible. Once I was left out with no TTYs so I could not login. But I could NFS mount as root / and edited /etc/crontab to schedule a reboot -- Yiorgos Adamopoulos, adamo@ieee.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200003171607.e2HG75Y91631>