Date: Fri, 22 Sep 2000 00:51:34 -0400 From: "Matthew Emmerton" <matt@gsicomp.on.ca> To: <freebsd-questions@FreeBSD.ORG>, "Bigwillie" <mvanberk@optonline.net> Subject: Re: Help the daemons are killing it Message-ID: <002e01c02450$c886e080$1200a8c0@zircon> References: <4.2.0.58.20000921224146.00992f00@mail-hub.optonline.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?002e01c02450$c886e080$1200a8c0>