A cron job always sends a mail to the owner of the respective cron queue when it produces output which would go to the screen. Since there is no terminal attached to a cron job the only way for it to put that output somewhere is to mail it to the originator.
I would check the cron jobs of all users (you can find the crontabs of all users in "/var/spool/cron/crontabs/<username>") and add complete output suppression to those which haven't one already. If a cron job has to produce some output it should go to logfiles:
I keep having this msg on my SunOS console :
Jun 29 08:57:40 bersimis sendmail: NOQUEUE: low on space (have 0, SMTP-DAEMON needs 101 in /var/spool/mqueue)
I tried to make some space by deleting the files in it, but the msg came back ...
Any tips ?
Thanks (3 Replies)
Hi,
We have all the user account in a home direcory where their mail is stored and retrieved by email clients. We do however have /var/spool/mail with all the user accounts in it as well Our sendmail.cf is configured to use /var/spool/mqueue as the queue so .what is /var/spool/mail being used... (3 Replies)
Hi,
First Question: In our company our users have their mailboxes in /var/spool/mail
When I look at the users file it seems as if every email sent/received is in that user file! Is this because IMAP is being used or is that just how sendmail works?
Second Question: How is that when I create... (3 Replies)
Hi,
How can i get my mail on either /var/spool/mail or /var/mail?
I use mail and sendmail command to send mail. But everytime I send mail it comes to my outlook inbox and when I check with mail command I get the message "No mail for siba". (Note siba is my user Id.) (2 Replies)
Hello,
I have a bunch of cron jobs in the crontab. For some reason mail from the cron jobs started going to /var/spool/mqueue instead of being sent.
Does anyone know why mail from cron jobs would go to the queue instead of being sent? (9 Replies)
Hi, We have some 2-3 Solaris 9 servers with the following issue.
For every cron job which has email notifications, it is sending the emails, but it create files at /var/spool/clientmqueue/ which has similar contents.
"
V6
T1271362260
K1271362260
N1
P30359
MDeferred: Connection refused... (1 Reply)
Hi,
solaris : 9
can we delete the files from this location /var/spool/clientmqueue . I found around 40K files lying in this location.
Regards (1 Reply)
Hi
My box is running with AIX 6100-06 and Im the root user of this box
My /var gets filled up often to 100%
When I investigate I find that it is the below file which increases rapidly
/var/spool/mail/pdgadmin
I dont know why this file is growing up.
Can any one assist me on this.... (2 Replies)
Hi guys .
I have a solaris machine serving as a DNS server for my environment. Everytime I go into /var/spool/mqueue , there are an aweful lot of emails with names likes:
qfqB6ChrpL006644.
When I cat the file , I get the following output:
H??Received: from machine.domain.com... (3 Replies)
I have Red hat Linux server. There are 14 NFS shares which are coming from NAS. There are so many messages filling /var/log/messages, which seems like some NFS logging is enables somewhere, but I am not able to figure it out. Every few minutes, it will filll my /var (which is part of root) to 100%... (2 Replies)
Discussion started by: solaris_1977
2 Replies
LEARN ABOUT REDHAT
crond
CRON(8) System Manager's Manual CRON(8)NAME
cron - daemon to execute scheduled commands (Vixie Cron)
SYNOPSIS
cron
DESCRIPTION
Cron should be started from /etc/rc or /etc/rc.local. It will return immediately, so you don't need to start it with '&'.
Cron searches /var/spool/cron for crontab files which are named after accounts in /etc/passwd; crontabs found are loaded into memory. Cron
also searches for /etc/crontab and the files in the /etc/cron.d/ directory, which are in a different format (see crontab(5)). Cron then
wakes up every minute, examining all stored crontabs, checking each command to see if it should be run in the current minute. When execut-
ing commands, any output is mailed to the owner of the crontab (or to the user named in the MAILTO environment variable in the crontab, if
such exists).
Additionally, cron checks each minute to see if its spool directory's modtime (or the modtime on /etc/crontab) has changed, and if it has,
cron will then examine the modtime on all crontabs and reload those which have changed. Thus cron need not be restarted whenever a crontab
file is modified. Note that the Crontab(1) command updates the modtime of the spool directory whenever it changes a crontab.
SEE ALSO crontab(1), crontab(5)AUTHOR
Paul Vixie <paul@vix.com>
4th Berkeley Distribution 20 December 1993 CRON(8)