Scheduled job starting too late

This is likely to be an at problem, what is the output of 'atq' after you have added a task ?

- gaute

Hi Gaute, thanks for the quick reaction, and sorry for my late answer.
I have scheduled a task for today at 20.00h (record 1 hour of internet radio, my standard use case).

Output of "atq" and "at" looks like this:

ruediger@helge:~$ atq
81 Mon Dec 14 20:00:00 2009 a ruediger

ruediger@helge:~$ at -c 81
#!/bin/sh
# atrun uid=1000 gid=1000
# mail ruediger 0
umask 22
GDM_KEYBOARD_LAYOUT=de; export GDM_KEYBOARD_LAYOUT
GNOME_KEYRING_PID=2879; export GNOME_KEYRING_PID
USER=ruediger; export USER
GNOME_KEYRING_SOCKET=/tmp/keyring-gDnD9A/socket; export GNOME_KEYRING_SOCKET
SSH_AGENT_PID=2941; export SSH_AGENT_PID
ORBIT_SOCKETDIR=/tmp/orbit-ruediger; export ORBIT_SOCKETDIR
HOME=/home/ruediger; export HOME
DESKTOP_SESSION=gnome; export DESKTOP_SESSION
XDG_SESSION_COOKIE=34d3d1930af63600525a957c48405b01-1260710869.368217-211562992; export XDG_SESSION_COOKIE
GTK_MODULES=canberra-gtk-module; export GTK_MODULES
GTK_RC_FILES=/etc/gtk/gtkrc:/home/ruediger/.gtkrc-1.2-gnome2; export GTK_RC_FILES
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-K9LWpIEgxB,guid=1ad8a35491d82bca2000b53c4b24ebd5; export DBUS_SESSION_BUS_ADDRESS
LOGNAME=ruediger; export LOGNAME
POSIXLY_CORRECT=enabled; export POSIXLY_CORRECT
USERNAME=ruediger; export USERNAME
GNOME_DESKTOP_SESSION_ID=this-is-deprecated; export GNOME_DESKTOP_SESSION_ID
GDM_LANG=en_US.UTF-8; export GDM_LANG
SESSION_MANAGER=local/helge:@/tmp/.ICE-unix/2894,unix/helge:/tmp/.ICE-unix/2894; export SESSION_MANAGER
PATH=/home/ruediger/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games; export PATH
LANG=en_US.UTF-8; export LANG
XAUTHORITY=/var/run/gdm/auth-for-ruediger-8DDoMY/database; export XAUTHORITY
SSH_AUTH_SOCK=/tmp/keyring-gDnD9A/socket.ssh; export SSH_AUTH_SOCK
GDMSESSION=gnome; export GDMSESSION
GPG_AGENT_INFO=/tmp/seahorse-kyACwT/S.gpg-agent:2964:1; export GPG_AGENT_INFO
PWD=/home/ruediger; export PWD
SPEECHD_PORT=7560; export SPEECHD_PORT
XDG_DATA_DIRS=/usr/share/gnome:/usr/local/share/:/usr/share/; export XDG_DATA_DIRS
PYTHONPATH=::/usr/lib/python2.6/site-packages/gtk-2.0/:; export PYTHONPATH
cd /home/ruediger || {
  echo 'Execution directory inaccessible' >&2
  exit 1
}
###### ---- GNOME_SCHEDULE_SCRIPT_DELIMITER #####
unset POSIXLY_CORRECT
icecream --stop=61min --name=deleteme-%F-%T http://www.byte.fm/stream/bytefm.m3u

thanks, gnome-schedule just adds an 'at' task - and as you see it has been scheduled correctly on 20:00, after that its up to 'atd' to start the task when it should. So as far as I can see this is an atd bug.

You could try creating a task that does:
date > /tmp/testtask (make sure all output is on)

then check whats in /tmp/testtask.. is the time you are checking against the time on the server? are you sure they are synced?

- gaute