11-27-2001
When you use pipe [ | ] you must work with stdin and/or stdout, not filenames. At the second, you didn't write tar command. At the third - why do you want to tar 1 file ?
At the fourth - "mail" don't send you compressed file as attachement but as message body. You have to use some combination of the MIME command to create attachement. Better is to use "mutt"
Your command pipe should be as folows:
cat logfile | gzip logfile.gz; mutt -s "logfile" -a logfile.gz
email@domain.com
10 More Discussions You Might Find Interesting
1. Cybersecurity
Yesterday I happened to check /var/log/httpd/access_log and found some funny things like these,
209.127.62.159 - - "GET /scripts/root.exe?/c+dir HTTP/1.0" 404 210
209.127.62.159 - - "GET /MSADC/root.exe?/c+dir HTTP/1.0" 404 208
209.127.62.159 - - "GET /c/winnt/system32/cmd.exe?/c+dir... (3 Replies)
Discussion started by: eddie
3 Replies
2. UNIX for Dummies Questions & Answers
When I try to use the CLI mail, I get the following error. What's wrong?
Welcome to Darwin!
% mail root
Subject: test
test
.
EOT
% /etc/mail/sendmail.cf: line 81: fileclass: cannot open /etc/mail/local-host-names: Group writable directory
Do I just need to change the... (1 Reply)
Discussion started by: chenly
1 Replies
3. 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
4. UNIX for Dummies Questions & Answers
Hi,
I've worked out that my server was getting clogged with the access_log.processed file.
I deleted it using the command
> /var/www/vhosts/domain.com/statistics/logs/access_log.processed
I also set that up as a crontab job for every Wednesday.
What I was wondering is the version using... (4 Replies)
Discussion started by: chickenhouse
4 Replies
5. Solaris
Hi
I need to look for the range dates of access_log for example:
between 02/May/2009:14:56:20 and 05/May/2009:18:46:06
then write the content to another file. Date and time is very important for me to concatenate them into access_log later.
Thanks (2 Replies)
Discussion started by: lamoul
2 Replies
6. Web Development
hi folks,
how to write CFID and CFTOKEN cookie in apache logs ?
can you give me a link or howtos in doing this.
thanks in advance (0 Replies)
Discussion started by: linuxgeek
0 Replies
7. UNIX for Advanced & Expert Users
i have sun machines having solaris 9 & 10 OS . Now i need to send mail from the machines to my outlook account . I have the ip adress of OUTLOOK mail server. Now what are the setting i need to do in solaris machines so that i can use mailx or sendmail.
actually i am trying to automate the high... (2 Replies)
Discussion started by: amitranjansahu
2 Replies
8. Linux
I found the /var/www/logs/access_log file (access log in order to find specific information about IP, And when users last logged in.)
but in my fedora the access_log file is is in my /var/log/cups and it looks different from what it should be. Why is that?
my goal is to get a list of IP... (4 Replies)
Discussion started by: bugenhagen_
4 Replies
9. Shell Programming and Scripting
Hello, my website under http get attack.
When i check the access_log i can see like this.
xx.xxx.xxx.xxx - - "GET //wp-admin/blabla/test.php?jASHSSAsgaGSAgsASGIGIG HTTP/1.1" 200 0 "-" "-"
xxx.xxx.x.xx - - "GET //wp-admin/blabla/test.php?jASHSSAsgaGSAgsASGIGIG HTTP/1.1" 200 0 "-" "-"
... (3 Replies)
Discussion started by: SAYGIN
3 Replies
10. UNIX for Advanced & Expert Users
I am having trouble getting mail to work on a red hat server. At first I was getting this message.
Diagnostic-Code: X-Postfix; delivery temporarily suspended: connect to :25: Connection refused
Then added the port to my firewall. Then I temporarily turned off selinux. I then copied this file... (1 Reply)
Discussion started by: cokedude
1 Replies
LEARN ABOUT OPENDARWIN
cron
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)