Hello, can someone suggest an alternative to "at" for scheduled script execution? I currently use at to schedule recordings with my tv-card, but I find it lacking in a few ways. One thing that would be nice if the scheduler could execute a script at one time, kill it off at another, and prevent other jobs from being scheduled in the time in between. This because access to the tv device is only allowed by one process at once. Also, I think the output is lacking. Here is how I use at today: The current output of atq: 44 2006-10-01 17:00 a claes 32 2006-09-30 23:25 a claes 34 2006-09-27 22:00 a claes 45 2006-10-08 17:00 a claes 46 2006-09-27 22:00 a claes 47 2006-10-04 22:00 a claes 42 2006-09-30 21:00 a claes Each of these jobs correspond to a certain recording, but the listing does not reveal which one, and at what time it ends. To find that I have to enter at -c jobname, which will print a lot of garbage with the interesting stuff at the bottom: at -c 48 #LOTS of env stuff... G_BROKEN_FILENAMES=1; export G_BROKEN_FILENAMES JAVA_ROOT=/usr/lib/jvm/java; export JAVA_ROOT COLORTERM=1; export COLORTERM mc=\(\)\ {\ \ .\ /usr/share/mc/bin/mc-wrapper.sh" "}; export mc cd /home/claes || { echo 'Execution directory inaccessible' >&2 exit 1 } rectv 6 1h simpsons The bottom line is a call to my recording script with arguments for channel, duration and name. I would have liked it if I could give the scheduler the duration and name and have it present it in the listing. Or at least, if the scheduler would take a name for argument so i could name the jobs and see them in the listing. Note that I prefer a simple, command-line-driven program since this will run on a headless server. Thanks, Claes