From owner-freebsd-questions Tue Nov 21 18:20: 5 2000 Delivered-To: freebsd-questions@freebsd.org Received: from guru.mired.org (okc-65-26-235-186.mmcable.com [65.26.235.186]) by hub.freebsd.org (Postfix) with SMTP id 47D3737B4C5 for ; Tue, 21 Nov 2000 18:20:00 -0800 (PST) Received: (qmail 44960 invoked by uid 100); 22 Nov 2000 02:19:59 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14875.11599.841416.227931@guru.mired.org> Date: Tue, 21 Nov 2000 20:19:59 -0600 (CST) To: Bart Cc: questions@freebsd.org Subject: Re: ping OK, daemons dead ? In-Reply-To: <87345815@toto.iv> X-Mailer: VM 6.75 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bart types: > On Tue, 21 Nov 2000, brian william wolter wrote: > > > of situations; is it possible to use a script/program > > > which reboots the machine after 12 hours of no > > > activity of some kind of daemon (or login). > > you'd probibly be better off writing a script that will just restart the > > daemons that are dying on you, that way you won't have the downtime that > > will result from actually rebooting. you can just have the script check > > to see if the processes are still running and restart them if they are > > not. then just put it in the crontabs to execute every so often. > Well, I can not reach the console at this moment (it's a machine > located somewhere else) but the weird part is that I *can* connect > (using telnet) but no "login:" appears: > > acid2:/1/home/skin$ telnet mymachine.nl > Trying 212.104.204.x... > Connected to mymachine.nl. > Escape character is '^]'. > > So the daemon ain't dead... Those are the symptoms you see if one or more disks can't be accessed. Are you getting any error messages in the logs related to the disk? Do you have any daemons running that can respond without touching a disk (Apache status pages, maybe?)?