From owner-freebsd-questions Fri Sep 22 0:25:53 2000 Delivered-To: freebsd-questions@freebsd.org Received: from guru.mired.org (zoom0-069.telepath.com [216.14.0.69]) by hub.freebsd.org (Postfix) with SMTP id 8617537B422 for ; Fri, 22 Sep 2000 00:25:50 -0700 (PDT) Received: (qmail 70369 invoked by uid 100); 22 Sep 2000 07:25:49 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14795.2429.18231.182368@guru.mired.org> Date: Fri, 22 Sep 2000 02:25:49 -0500 (CDT) To: Bigwillie Cc: questions@freebsd.org Subject: Re: Help the daemons are killing it In-Reply-To: <36359760@toto.iv> X-Mailer: VM 6.72 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 Bigwillie writes: > Just joking, but not a serious problem (I have to reinstall most > likely). The problem I have is on a experimental box and Im some what a > newbie. Ive been playing around with cron so that it starts seti@home > every hour if its not running, and if it is it doesn't do a thing. I came > across problems where I would get errors==> Well, others have dealt with the problem.. > Another issue, why is cron so difficult to setup. I don't think it's any harder than installing FreeBSD in the first place. Of course, in trying to use it to make sure some process is always running, you're trying to drive nails with a screwdriver - and it doesn't work very well. For this particular application, I'd recommend installing TkSETI (it's in the ports). Not only does it monitor seti@home and restart it if need be, it provides a nice GUI interface showing what's going on, including a star map showing where you're looking, where you've looked, and where the last spike and gaussian were.