shell script run by user or cron job ? Post: 302232785

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

problem when the script is scheduled to run as cron job

Hello, I have problem in executing a shell script. When the shell script is executed at the shell prompt the script works successfully but when the same script is run as a cron job it fails to execute the files called within the shell script. I have scheduled the job in my crontab file as ...

2. Shell Programming and Scripting

script wont run from cron job

I have written a simple bash script that will run a wget command to recursively ftp an entire directories and it's contents. #!/bin/bash wget -r -N ftp://user:pass@server//VOL1/dir If I run from the regular command line it works fine. root@BUSRV: /media/backup1$ ./gwbu When I put it in...

3. UNIX for Advanced & Expert Users

Need help with a script run by a cron job.

Hi, new to this forum and not sure if this is the right place to post. I'm new to cron jobs and scripts, and I need some help with a script to be used with a cron job. I already have a bot set up at a certain website address and need a script that the cron job will load every day that tells it to...

4. Shell Programming and Scripting

Cron job shell script..

Hey Guys, i was trying out a shell script which has to remove a file for every 90 mins. this is the code i came up with . $ crontab -e file1 file1 contains 30 1 * * * * rm -r /folder1/folder2/somefile.txt Now i need the cron to run for every 90 mins. the problem with this is...

5. Solaris

Shell Script gives error when run through cron job.

Hi, The following shell script runs without any problem when executed manulally. USED=$(df -h /arch | tail -1 | awk '{print $5}' | cut -d '%' -f 1) if then find /arch/AUBUAT/ -type f -mtime +0 | xargs rm find /arch/AUBMIG/ -type f -mtime +0 | xargs rm fi But the same gives below...

6. UNIX for Dummies Questions & Answers

cron job for the created shell script

Hi am newbie for unix shell.. how to create a cron job for my already created shell script.:confused: Thanks!

7. Shell Programming and Scripting

how to run a script using cron job and send the output as attachment via e-mail using unix

how to run a script using cron job and send the output as attachment via e-mail using unix. please help me. how my cron job entry should be? As of now my cron job entry is to run the script at specific time, 15 03 * * * /path/sample.sh | mail -s "Logs" email_id In the above entry, what...

8. Shell Programming and Scripting

how do I run bash script using cron job

How do I run bash script using a cron job? I have tried to just write the path of the script, but that didn't work.

9. Shell Programming and Scripting

Cron job - Need to run Cron every quarter at particular time

Hi, 1) If some job supposed to run on 1st of every month at 7 AM In cron job when we have a blackout on the 1st ( i.e when 1st falls on a sunday ) how can we make the job run the next business day? 2) How can we run a job on 25th of every quarter 7 AM(jan,apr,jul,oct) And if 25th...

10. Shell Programming and Scripting

Script that will send an email if the cron job did not run.

Team, Would like to know what is the best script that will send you an email if cronjob did not run. Thanks

LEARN ABOUT BSD

at

AT(1)							      General Commands Manual							     AT(1)

NAME

       at - execute commands at a later time

SYNOPSIS

       at [ -c ] [ -s ] [ -m ] time [ day ] [ file ]

DESCRIPTION

       At spools away a copy of the named file to be used as input to sh(1) or csh(1).	If the -c flag (for (csh(1))) or the -s flag (for (sh(1)))
       is specified, then that shell will be used to execute the job; if no shell is specified, the current environment shell is used.	If no file
       name is specified, at prompts for commands from standard input until a ^D is typed.

       If  the -m flag is specified, mail will be sent to the user after the job has been run. If errors occur during execution of the job, then a
       copy of the error diagnostics will be sent to the user. If no errors occur, then a short message is sent informing the user that no  errors
       occurred.

       The  format  of the spool file is as follows: A four line header that includes the owner of the job, the name of the job, the shell used to
       run the job, and whether mail will be set after the job is executed. The header is followed by a cd command to the current directory and  a
       umask command to set the modes on any files created by the job.	Then at copies all relevant environment variables to the spool file.  When
       the script is run, it uses the user and group ID of the creator of the spool file.

       The time is 1 to 4 digits, with an optional following `A', `P', `N' or `M' for AM, PM, noon or midnight.  One and  two  digit  numbers  are
       taken to be hours, three and four digits to be hours and minutes.  If no letters follow the digits, a 24 hour clock time is understood.

       The  optional  day is either (1) a month name followed by a day number, or (2) a day of the week; if the word `week' follows, invocation is
       moved seven days further off.  Names of months and days may be recognizably truncated.  Examples of legitimate commands are

	      at 8am jan 24
	      at -c -m 1530 fr week
	      at -s -m 1200n week

       At programs are executed by periodic execution of the command /usr/libexec/atrun from cron(8).  The granularity of at depends upon the  how
       often atrun is executed.

       Error output is lost unless redirected or the -m flag is requested, in which case a copy of the errors is sent to the user via mail(1).

FILES

       /usr/spool/at		    spooling area
       /usr/spool/at/yy.ddd.hhhh.*  job file
       /usr/spool/at/past	    directory where jobs are executed from
       /usr/spool/at/lasttimedone   last time atrun was run
       /usr/libexec/atrun		executor (run by cron(8))

SEE ALSO

       atq(1), atrm(1), calendar(1), sleep(1), cron(8)

DIAGNOSTICS

       Complains about various syntax errors and times out of range.

BUGS

       Due  to	the  granularity  of  the execution of /usr/libexec/atrun, there may be bugs in scheduling things almost exactly 24 hours into the
       future.

       If the system crashes, mail is not sent to the user informing them that the job was not completed.

       Sometimes old spool files are not removed from the directory /usr/spool/at/past. This is usually due to a system crash, and  requires  that
       they be removed by hand.

4th Berkeley Distribution					 October 21, 1996							     AT(1)