FC1 job Scheduler problem - "at" command doesnt wrk
 

Hi all,
I am facing an issue scheduling a job in Fedora Core 1.I need to use the "at" command to start a job at a specified time (actually my broadband service provides free unlimited downloads between 2:00AM and 8:00AM).

[user@localhost Apps]$ at 2:30
at> execute
at> <EOT>
job 27 at 2006-01-07 02:30
[user@localhost Apps]$

"execute" is a shell script.
The following are the contents of my shell script "execute"

'''''''''''''Shell script''''''''''''''''''''
#! /bin/bash
/home/user/Apps/BitTornado/btdownloadheadless.py /home/user/Apps/BitTornado/mytorrent.torrent --saveas /mnt/e/linux/torrent_downloads/mytorrent 1>> /dev/null 2>> /dev/null
'''''''''''''Shell script''''''''''''''''''''

But the job is not starting at 2:00 AM.In fact,the "at" command simply does not work. It accepts the job i specify, assigns a job ID to it, but simply refuses to start the job at the given time.

I tried the following
---------------------

1. tried using "at" command as a root user,still it doesnt work

2. I tried chking the "at" command as follows

[user@localhost Apps]$ at now
at> execute
at> <EOT>
job 27 at 2006-01-06 19:30
[user@localhost Apps]$

But still the job does not run

3.I checked the "at" queue using the "atq". It displays the pending job as
27 2006-01-07 02:30 a user
but once the shceduled time elapses, the "at" queue no longer displays the job. But job does not start

4. I tried googling, but couldnt find any solid clue as to what could be the cause.

5. But i did come accross a link which said, the "at" command uses two files in the /etc folder, namely, at.allow and at.deny. I checked the /etc folder, the at.allow does not exists but at.deny exists and is empty

6. I checked and found "atd" running.

Am i missing something ????

Please help me resolve this problem.

regards
Harris

ok, well the first guess is always that the script you're running isn't executable (chmod +x) secondly i would suggest that you attempt to manually run the process that at would do. by this i don't just mane run your script though. if you run "at -c job" you'll get the actaul script that at will run, so just run that and see if it actaully works. after that you're looking at other permissions issues, or path probelms.... is "execute" on your path?

Hi

Thanks a lot for the help.I have actually found the reason as to y at was not starting my program. The shell script,rather Bittornado was the culprit.

I was invoking btdownloadheadless.py using "at" command, now btdownloadheadless.py reports error if i invoke it thro "at" (i redirected the standard error to a file) saying

"Error opening terminal:unknown."


Looks like btdownloadheadless.py is importing curses. When i commented out this import, the job got invoked at the scheduled time. The following link helped me resolve the issue

http://www.linuxquestions.org/questi...postid=1668601

Thanks again for responding

Regards
linfreak