01-11-2002
.forward file for mail redirection
I've set up a .forward file on a few identical servers that we have (all identical .forward file as well) but only one server is forwarding any of my unix mail (mail generated by cron) to my internet account.
Because these servers (5) are all identical in terms of aix versions, etc., I do not understand why only one works. The only difference that I can say is that these servers all run different cron jobs. Cron is the guy generating all these log messages and I'd like to see these emails in Outlook not unix.
Please advise as to what could be the issue. Is the use of the | tee command important in setting up the crontab to utilize the .forward file? Someone told me this is the case but I see no documentation in my unix admin book.
Thanks.
10 More Discussions You Might Find Interesting
1. Solaris
how can i forward roots mail, i want every mail fowarded (1 Reply)
Discussion started by: csaunders
1 Replies
2. UNIX for Dummies Questions & Answers
I am trying to configure sendmail to forward email to a PHP script. I don't know UNIX and am having trouble figuring out how to forward the mail. I think this is just a bunch of basic questions, but I have had little luck getting help elsewhere on my specific questions and it's driving me nuts. You... (3 Replies)
Discussion started by: bitt3n
3 Replies
3. Linux
Hai
can you help it out i am using send mail server in that some messages are teged with spam that messages has to forwaded to putecular Id and it has to removed from the user.
s.sheik (1 Reply)
Discussion started by: s_sheik
1 Replies
4. Solaris
Dear All,
Now I use solaris 10 and I try to forward mail from /var/mail/username to their external mail so what should I do?
thank u in advance (2 Replies)
Discussion started by: unitipon
2 Replies
5. Shell Programming and Scripting
I have forward dns zone file with A records and converting it to reverse zone file
ex.
subdomain1 A 10.20.30.40
subdomain2 A 10.20.31.41
subdomain3 A 10.20.35.43
subdomain4 A 10.20.30.41
subdomain5 ... (5 Replies)
Discussion started by: mosavani
5 Replies
6. UNIX for Dummies Questions & Answers
Hi there,
I receive job applications sent by a website daemon. The email subject contains the job offer description. The problem is that gmail tends to concatenate emails with the same subject and I don't really want all applications in the same email. Thus the from field contains the candidate... (0 Replies)
Discussion started by: chebarbudo
0 Replies
7. Debian
Hi There
Not sure if this is the correct place for this.
I'm running Sendmail on a Debian box and want to do the following.
e-mail comes in from userk@domain.co.za and is destined for usera@mydomain.co.za, but i want all mail from userk@domain.co.za to go to userb@mydomain.co.za. Sendmail... (3 Replies)
Discussion started by: linuxjunkie
3 Replies
8. UNIX for Advanced & Expert Users
Hi,
We are using mailx -s command to send mails from unix.
We need to ensure that this mail is not copied,forwarded etc.
Is there a command which can be used to achieve this using unix?
Thanks.
No double posting please, continue here. (0 Replies)
Discussion started by: dwarkeshr
0 Replies
9. UNIX for Dummies Questions & Answers
Hi,
We are using mailx -s command to send mails from unix.
We need to ensure that this mail is not copied,forwarded etc.
Is there a command which can be used to achieve this using unix?
Thanks. (1 Reply)
Discussion started by: dwarkeshr
1 Replies
10. Ubuntu
Hi,
I am new to linux stuff. I want to use linux iptables to configure rule so that all my incoming traffic with protocol "tcp" is forwarded to the "FORWARD CHAIN". The traffic i am dealing with has destination addresss of my machine but i want to block it from coming to input chain and somehow... (0 Replies)
Discussion started by: arsipk
0 Replies
cron(1M) System Administration Commands cron(1M)
NAME
cron - clock daemon
SYNOPSIS
/usr/sbin/cron
DESCRIPTION
cron starts a process that executes commands at specified dates and times.
You can specify regularly scheduled commands to cron according to instructions found in crontab files in the directory
/var/spool/cron/crontabs. Users can submit their own crontab file using the crontab(1) command. Commands which are to be executed only once
can be submitted using the at(1) command.
cron only examines crontab or at command files during its own process initialization phase and when the crontab or at command is run. This
reduces the overhead of checking for new or changed files at regularly scheduled intervals.
As cron never exits, it should be executed only once. This is done routinely by way of the svc:/system/cron:default service. The file
/etc/cron.d/FIFO file is used as a lock file to prevent the execution of more than one instance of cron.
cron captures the output of the job's stdout and stderr streams, and, if it is not empty, mails the output to the user. If the job does not
produce output, no mail is sent to the user. An exception is if the job is an at(1) job and the -m option was specified when the job was
submitted.
cron and at jobs are not executed if your account is locked. Jobs and processses execute. The shadow(4) file defines which accounts are not
locked and will have their jobs and processes executed.
Setting cron Jobs Across Timezones
The timezone of the cron daemon sets the system-wide timezone for cron entries. This, in turn, is by set by default system-wide using
/etc/default/init.
If some form of daylight savings or summer/winter time is in effect, then jobs scheduled during the switchover period could be executed
once, twice, or not at all.
Setting cron Defaults
To keep a log of all actions taken by cron, you must specify CRONLOG=YES in the /etc/default/cron file. If you specify CRONLOG=NO, no log-
ging is done. Keeping the log is a user configurable option since cron usually creates huge log files.
You can specify the PATH for user cron jobs by using PATH= in /etc/default/cron. You can set the PATH for root cron jobs using SUPATH= in
/etc/default/cron. Carefully consider the security implications of setting PATH and SUPATH.
Example /etc/default/cron file:
CRONLOG=YES
PATH=/usr/bin:/usr/ucb:
This example enables logging and sets the default PATH used by non-root jobs to /usr/bin:/usr/ucb:. Root jobs continue to use
/usr/sbin:/usr/bin.
The cron log file is periodically rotated by logadm(1M).
FILES
/etc/cron.d Main cron directory
/etc/cron.d/FIFO Lock file
/etc/default/cron cron default settings file
/var/cron/log cron history information
/var/spool/cron Spool area
/etc/cron.d/queuedefs Queue description file for at, batch, and cron
/etc/logadm.conf Configuration file for logadm
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO
svcs(1), at(1), crontab(1), sh(1), logadm(1M), svcadm(1M), queuedefs(4), shadow(4), attributes(5), smf(5)
NOTES
The cron service is managed by the service management facility, smf(5), under the service identifier:
svc:/system/cron:default
Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser-
vice's status can be queried using the svcs(1) command.
DIAGNOSTICS
A history of all actions taken by cron is stored in /var/cron/log and possibly in /var/cron/olog.
SunOS 5.10 5 Aug 2004 cron(1M)