Sponsored Content
Top Forums Shell Programming and Scripting Please let me know what this line in cron means? Post 302241212 by mac4rfree on Monday 29th of September 2008 01:10:41 AM
Old 09-29-2008
Please let me know what this line in cron means?

Hi All,

I found this line in my crontab..

0 6 * * * "some script name"

my question is it means the script should run at 6 00 am. But on what those days are not mentioned. Then in that case when will the script will run?

Thanks for ur help in advance,
Magesh
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

One line of cron is not working - PLS Help

Hi all, I have spent 2 hours going through the forum and have not found an answer to my question, I hope someone can help. I have cron setup to run two commands, one at 1am and one at 3 am, the one at 1 am works but not the one at 3 am. The time is set as: 0 1 * * * /path/to/file 0 3 * * *... (3 Replies)
Discussion started by: burnie
3 Replies

2. UNIX for Advanced & Expert Users

process nice level command line vs cron

Under, Solaris 10 I have the following problem: A script executed at command line runs with nice level 0, as expected. Same script started under (user) crontab runs with nice level 2. I would prefer it run at 0. Is this possible? If so, how? Thanks. (0 Replies)
Discussion started by: henrydark
0 Replies

3. UNIX for Dummies Questions & Answers

script works on command line, not in cron job

Hey there, I'm a total newbie unix guy here and just picking this stuff up. Have a very small script I put together that works fine from the command line but not once I put it in a cron job. Searched and found this thread and am wondering it it has something to do with setting variables, though the... (7 Replies)
Discussion started by: JackTheTripper
7 Replies

4. UNIX for Dummies Questions & Answers

Script through cron and command line

I have a script which runs fine through command line, but doesn't run through cron. There are some variables which are set by the .profile file which are used by the script. Is it that cront does not pick these variables. $/export/home/rahul/bin/createfile.sh >>... (3 Replies)
Discussion started by: rahulrathod
3 Replies

5. Shell Programming and Scripting

Why does '$$' means an empty line in agrep -d '$$'

Hi all, Why does '$$' means an empty line in agrep -d '$$'. I did not know that '$$' can be seen as an empty line in regular expression. So did I miss something here ? Thanks! (4 Replies)
Discussion started by: qiulang
4 Replies

6. Shell Programming and Scripting

s3cmd works on command line not on cron

Ubuntu 9.10 is my linux distro Based on forums they say that the problem is with environment . here is my case: login as user, then sudo -s using this command: s3cmd put file s3://bucket >>worked! now here is the simple script intended for testing: #! /bin/bash env >/tmp/cronjob.log... (1 Reply)
Discussion started by: qwerty20
1 Replies

7. Shell Programming and Scripting

cron woes - line too long ??

Here is my cron entry: 13 10 * * * /home/my_login/mystf/myscriptsize.sh > /home/my_login/mystf/`date +"%Y%m%d"`log.csv Here is my cron error: unexpected EOF while looking for matching ``' ...cron executes: /home/my_login/mystf/myscriptsize.sh > /home/my_login/mystf/`date +" ..and NOT... (2 Replies)
Discussion started by: landog
2 Replies

8. UNIX for Dummies Questions & Answers

One Line for loop in CRON

Hello, I'm trying to run a one line for loop from the CRON. This is the exact command /bin/bash for file in $(/bin/find /opt/local/edw_extract/logs -name "*.log"); do /bin/cat /dev/null > $file; done This will run from the command successfully. When I schedule this to run it will... (3 Replies)
Discussion started by: mhauff
3 Replies

9. Shell Programming and Scripting

Issue in running a command line utility in CRON

Hi Everyone! I am facing an issue in running a command line utility from the CRON. This utility displays IPC statistics on UNIX message queues: The "queue name" and the "count" of messages in the queue. When running this utility from prompt, it will provide an output on the screen, like the... (4 Replies)
Discussion started by: vai_sh
4 Replies
FAXCRON(8)						      System Manager's Manual							FAXCRON(8)

NAME
faxcron - HylaFAX routine maintenance script SYNOPSIS
/usr/sbin/faxcron [ -n ] [ -l lastrun ] DESCRIPTION
faxcron is a command script that does routine upkeep tasks in a HylaFAX spooling directory hierarchy. This script is intended to be invoked from cron(8) on behalf of the fax user (often the ``fax'' user is uucp) once a day, with the standard output sent by mail to the HylaFAX administrator. For example, the following crontab might be set up for the fax user: 25 23 * * * sh /usr/sbin/faxcron | mail FaxMaster The faxcron script does the following work: o report statistics for facsimile transmitted since the last time faxcron was run. o report statistics for facsimile transmitted in the past week. o report statistics for facsimile received since the last time faxcron was run. o report statistics for facsimile received in the past week. o report any recent calls that failed suspiciously and return the associated trace log; o purge data that is 30 days or older from the remote machine information directory; o delete information that is 30 days or older from session trace log files; o remove files from the tmp directory that are older than 1 day; o remove files in the received facsimile queue that are 7 days or older; o report sites that are currently having jobs rejected; and o force all session log files to be owned by the fax user and kept with protection mode 644. OPTIONS
-n Forces faxcron to run without updating any files. -l lastrun Forces the notion of the last time that faxcron was run to be lastrun. The value of lastrun is a date and time string of the form ``MM/DD/YY HH:MM'' (the date(1) format string ``%D %H:%M''). -info n Set the expiration time for data in the info database to be n days. -log n Set the expiration time for session log data to be n days. -rcv n Set the expiration time for files in the received facsimile queue to be n days. -tmp n Set the expiration time for files in the tmp directory to be n days. -mode m Set the file protection mode for session logs to m (a command line argument to chmod(1)). NOTES
This script requires nawk(1) or gawk(1) and a date (1) program that supports the ``+format'' option. If session logs are to be kept private this script must be modified to filter out sensitive information such as calling card numbers. (It should also be run with ``-mode 0600'' so that session log files are not publicly readable.) FILES
/var/spool/hylafax spooling area /var/spool/hylafax/status/lastrun timestamp of last run /usr/sbin/xferfaxstats for generating transmit statistics /usr/sbin/recvstats for generating receive statistics /var/spool/hylafax/tmp/faxcronXXXX temporary file for truncating session logs /var/spool/hylafax/tmp/faxlogXXXX temporary file for logs of failed calls SEE ALSO
cron(8), faxq(8), faxgetty(8), faxsend(8), xferfaxstats(8), recvstats(8), hylafax-server(5) May 12, 1996 FAXCRON(8)
All times are GMT -4. The time now is 09:50 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy