From owner-freebsd-questions Thu Sep 21 23:31:55 2000 Delivered-To: freebsd-questions@freebsd.org Received: from s1.optonline.net (s1.optonline.net [167.206.112.6]) by hub.freebsd.org (Postfix) with ESMTP id EC9C437B449 for ; Thu, 21 Sep 2000 23:31:46 -0700 (PDT) Received: from steinyv (d133-151.jcsnnj.optonline.net [24.189.133.151]) by s1.optonline.net (8.10.2/8.10.2) with ESMTP id e8M6Vd209953; Fri, 22 Sep 2000 02:31:39 -0400 (EDT) Message-Id: <4.2.0.58.20000922022314.009d5ce0@mail-hub.optonline.net> X-Sender: mvanberk@mail-hub.optonline.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Fri, 22 Sep 2000 02:26:44 -0400 To: "Matthew Emmerton" From: Bigwillie Subject: Re: Help the daemons are killing it Cc: freebsd-questions@freebsd.org In-Reply-To: <002e01c02450$c886e080$1200a8c0@zircon> References: <4.2.0.58.20000921224146.00992f00@mail-hub.optonline.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When I was experimenting with cron, I was editing /etc/crontab, and I had added a line to it so I can do the seticlient. When I was about to give up I removed it, so it should be back to normal. Anyway, Ill have to double check the files tomorrow. I have been beat up enough by the daemons today. Ill let you all know what happens in tomorrows episode...... At 12:51 AM 9/22/00 , you wrote: > > Its like world war 13 in that box. I ran top while this was going on, and > > sendmail and local.mail were on top just running things. > >If they were "running away" filling up your mail spool as fast as they can, >check your crontab setup. Most likely you've forgotten to redirect the >output of the scripts / programs you're running in your crontab to /dev/null >or a log file. If you don't, then cron will mail the output to root. > >If you're starting Seti@Home from crontab without redirecting the output, >then cron will be emailing root with all the status information that the >Seti@Home client churns out to the console. This could be responsible for >why your mailbox is filling up. > > > Its kind of amusing to see this happen. Since its an experimental box, I > > dont care about what happens to it. My real issue is how could I find out > > where all of this information is being written to. At one moment > > /var/mail/root had a huge file size then it would go down then up again, >so > > maybe the rest was in the spool, dont know. > >You're looking in the right place. /var/mail/root is root's mbox, and >/var/spool/mqueue is the mail queue. > > > Another issue, why is cron so difficult to setup. > >It's not difficult to set up at all. Just make sure that you read the >manpage for 'crontab'. > >-- >Matthew Emmerton >GSI Computer Services >+1 (800) 217-5409 (Canada) > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" in the body of the message _________________________________________ Steiny's Studio Pachyderm Productions http://steiny.hypermart.net mailto:info@steiny.hypermart.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message