Sponsored Content
Operating Systems Linux at scheduling executes job immediately Post 302222977 by new2ss on Friday 8th of August 2008 03:59:13 AM
Old 08-08-2008
at scheduling executes job immediately

Hi all,

I am trying to schedule a one time job using at. First I do a `date` command to capture current date

Code:
[myhost]$ date
Fri Aug  8 15:53:20  # shows current date
[myhost]$ at -t 16:00 today #schedule command to run at 4pm
at> command1
at> <EOT> #after pressing Crtl D
job 6 at 2008-08-08 15:53

and the command1 run immediately.

I schedule the job to run at 4pm. But it instead runs at 3.53pm, which was the time i was scheduling it. Does anybody know why?
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

problem with scheduling a job

I scheduled 2 Oracle jobs to run on IBM AIX 4.3.3 at 06:50 and 06:58 on 02/02/03 with the below syntax: $ at 06:50 02/02/03 /orac/ora11/temp/sun_job1.sh Job oracle.1044175800.a will be run at Sun Feb 2 06:50:00 2003. $ at 06:58 02/02/03 /orac/ora11/temp/sun_job2.sh Job... (1 Reply)
Discussion started by: ted
1 Replies

2. Shell Programming and Scripting

Job Scheduling

Hello, I want to know about job scheduling utilities available in unix. It should not be responsible just for starting the job like in case of cron but should also be able to handle the execution of jobs. Regards, Ritesh (1 Reply)
Discussion started by: turlapaty
1 Replies

3. UNIX and Linux Applications

Job Scheduling

I am working on UNIX AIX system, with Oracle OS. We are not supposed to use any tools to schedule our unix shell scripts. Basically we have to make use of Oracle tables and Shell scripts to manage dependencies, restartability, scheduling, parallelizing,etc. If anyone has worked/ is working... (1 Reply)
Discussion started by: singhabhijit
1 Replies

4. Shell Programming and Scripting

Job Scheduling

I am working on UNIX AIX system, with Oracle OS. We are not supposed to use any tools to schedule our unix shell scripts. Basically we have to make use of Oracle tables and Shell scripts to manage dependencies, restartability, scheduling, parallelizing,etc. If anyone has worked/ is working... (4 Replies)
Discussion started by: singhabhijit
4 Replies

5. Shell Programming and Scripting

Job scheduling dependencies.

Hi, I have scheduled two jobs, 2nd job is depend upon the 1st one. Once the 1st job will finish the execution , then only 2nd job will start execution. Both the jobs present in the cron file. Please reply as earleist because this is one my requirement, where should put the condition,... (1 Reply)
Discussion started by: rajesh08
1 Replies

6. UNIX and Linux Applications

Job Scheduling (Autosys)

Hello! I will be working with Autosys and I am looking for individuals that have knowledge of this UNIX application. Thank-you! (3 Replies)
Discussion started by: preshe79
3 Replies

7. Shell Programming and Scripting

Shell script not getting called through cron job but executes fine manually.

Hi, My shell script not getting called through cron job. The same works fine when executed manually. I tried to generate logs to find if the scripts has some errors related to path using following command- trying to execute .sh file every 5 mins: */5 * * * * /home/myfolder/abc.sh... (17 Replies)
Discussion started by: Dejavu20
17 Replies

8. Shell Programming and Scripting

scheduling a job using at command

Hi All, I've been trying to schedule a job using the at command on Solaris 5.10 but i've been running into some issue. ( Not allowed to use cron :wall: ) I have a script that reads a logs file, does some iteration and cat's the output in an email . ## the o/p of /home/myscript.sh is : ... (2 Replies)
Discussion started by: Irishboy24
2 Replies

9. Shell Programming and Scripting

Output differs when run manually and when cron job executes it

I get a different output when i manually run the .sh script and when it is run by a cron job. Please help me .. TMP1="/lhome/bbuser/script/wslog/sar.t1" TMP2="/lhome/bbuser/script/wslog/sar.t2" TMP3="/lhome/bbuser/script/wslog/sar.t3" OUTPUT="/lhome/bbuser/script/wslog/sar.out"... (8 Replies)
Discussion started by: nithinankam
8 Replies

10. Shell Programming and Scripting

Job Scheduling

Hi All, I am new to unix and i have a task in front of me. The code part is "android update sdk" . I need to crontab this process. Hence i have written a script that runs the above command and sends a mail once the update is done. The problem with the automation is the installer asks for a... (5 Replies)
Discussion started by: Kashyap
5 Replies
AT(1)							     Linux Programmer's Manual							     AT(1)

NAME
at, batch, atq, atrm - queue, examine or delete jobs for later execution SYNOPSIS
at [-V] [-q queue] [-f file] [-mldbv] TIME at -c job [job...] atq [-V] [-q queue] atrm [-V] job [job...] batch [-V] [-q queue] [-f file] [-mv] [TIME] DESCRIPTION
at and batch read commands from standard input or a specified file which are to be executed at a later time, using the shell set by the user's environment variable SHELL, the user's login shell, or ultimately /bin/sh. at executes commands at a specified time. atq lists the user's pending jobs, unless the user is the superuser; in that case, everybody's jobs are listed. The format of the out- put lines (one for each job) is: Job number, date, hour, job class. atrm deletes jobs, identified by their job number. batch executes commands when system load levels permit; in other words, when the load average drops below 0.8, or the value specified in the invocation of atrun. At allows fairly complex time specifications, extending the POSIX.2 standard. It accepts times of the form HH:MM to run a job at a spe- cific time of day. (If that time is already past, the next day is assumed.) You may also specify midnight, noon, or teatime (4pm) and you can have a time-of-day suffixed with AM or PM for running in the morning or the evening. You can also say what day the job will be run, by giving a date in the form month-name day with an optional year, or giving a date of the form MMDDYY or MM/DD/YY or DD.MM.YY. The specifi- cation of a date must follow the specification of the time of day. You can also give times like now + count time-units, where the time- units can be minutes, hours, days, or weeks and you can tell at to run the job today by suffixing the time with today and to run the job tomorrow by suffixing the time with tomorrow. For example, to run a job at 4pm three days from now, you would do at 4pm + 3 days, to run a job at 10:00am on July 31, you would do at 10am Jul 31 and to run a job at 1am tomorrow, you would do at 1am tomorrow. /usr/share/doc/at-3.1.8/timespec contains the exact definition of the time specification. For both at and batch, commands are read from standard input or the file specified with the -f option and executed. The working directory, the environment (except for the variables TERM, DISPLAY and _) and the umask are retained from the time of invocation. An at - or batch - command invoked from a su(1) shell will retain the current userid. The user will be mailed standard error and standard output from his commands, if any. Mail will be sent using the command /usr/sbin/sendmail. If at is executed from a su(1) shell, the owner of the login shell will receive the mail. The superuser may use these commands in any case. For other users, permission to use at is determined by the files /etc/at.allow and /etc/at.deny. If the file /etc/at.allow exists, only usernames mentioned in it are allowed to use at. If /etc/at.allow does not exist, /etc/at.deny is checked, every username not mentioned in it is then allowed to use at. If neither exists, only the superuser is allowed use of at. An empty /etc/at.deny means that every user is allowed use these commands, this is the default configuration. OPTIONS
-V prints the version number to standard error. -q queue uses the specified queue. A queue designation consists of a single letter; valid queue designations range from a to z. and A to Z. The a queue is the default for at and the b queue for batch. Queues with higher letters run with increased niceness. The spe- cial queue "=" is reserved for jobs which are currently running. If a job is submitted to a queue designated with an uppercase letter, it is treated as if it had been submitted to batch at that time. If atq is given a specific queue, it will only show jobs pending in that queue. -m Send mail to the user when the job has completed even if there was no output. -f file Reads the job from file rather than standard input. -l Is an alias for atq. -d Is an alias for atrm. -v Shows the time the job will be executed. Times displayed will be in the format "1997-02-20 14:50" unless the environment variable POSIXLY_CORRECT is set; then, it will be "Thu Feb 20 14:50:00 1996". -c cats the jobs listed on the command line to standard output. FILES
/var/spool/at /var/spool/at/spool /proc/loadavg /var/run/utmp /etc/at.allow /etc/at.deny SEE ALSO
cron(1), nice(1), sh(1), umask(2), atd(8). BUGS
The correct operation of batch for Linux depends on the presence of a proc- type directory mounted on /proc. If the file /var/run/utmp is not available or corrupted, or if the user is not logged on at the time at is invoked, the mail is sent to the userid found in the environment variable LOGNAME. If that is undefined or empty, the current userid is assumed. At and batch as presently implemented are not suitable when users are competing for resources. If this is the case for your site, you might want to consider another batch system, such as nqs. AUTHOR
At was mostly written by Thomas Koenig, ig25@rz.uni-karlsruhe.de. local Nov 1996 AT(1)
All times are GMT -4. The time now is 02:01 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy