Changing times of 'at' jobs

I have a requirement to sometimes change the times of scheduled 'at' jobs.

I notice the date/time the job is due to run is not stored in /var/spool/cron/atjobs/xxx and
I can't seem to find where this information is stored/derived.  I've run a truss on 'at -l', but that made me
none the wiser.

Is it even possible?

My other choices in are to:

1.  Delete and resubmit the job (This can be very messy because of the application generating the jobs)
2.  Use a different batch scheduling tool.

I don't want to go down the other paths until I've totally ruled out manipulating the at times directly.
LVL 48
TintinAsked:
Who is Participating?
 
OtetelisanuCommented:
[root@pluto:/db/ttest] at -f ./tt 1200am Nov 07
commands will be executed using /bin/ksh
job 1068159600.a at Fri Nov  7 00:00:00 2003

[root@pluto:/db/ttest] at -l
user = root     1068159600.a    Fri Nov  7 00:00:00 2003


1 Day 24x3600=86400 sec


If you make the 1068159600.a + 86400 you have 1 day later.


1068159600 + 86400 = 1068246000


[root@pluto:/var/spool/cron/atjobs] mv 1068159600.a  1068246000.a
[root@pluto:/var/spool/cron/atjobs] at -l
user = root     1068246000.a    Sat Nov  8 00:00:00 2003
[root@pluto:/var/spool/cron/atjobs]

This 1068159600 is the secondtime from Unix born.

If you change with n second is with this second later


0
 
yuzhCommented:
Sorry, I don't think you can modify the run time for an at-job, but you can remove it and then
restart it.

Unlike a cron job which is running at regular based, at job is a one off job start at the user
predefinded time.
0
 
TintinAuthor Commented:
Thanks Otetelisanu.

I don't know why I didn't think of that.  I kept looking at the id numbers thinking they were simple sequence numbers.

Makes good sense now.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.