sched
sched hh:mm command
sched n
>sched 11:00 echo It\'s eleven o\'clock.
causes
the shell to echo 'It's eleven o'clock.' at 11 a.m. The time can be
in 12-hour a.m. or p.m. format >sched 5pm set prompt='[%h] It\'s after 5; go home: >'
or
it can be relative to the current time: >sched +2:15 /usr/lib/uucp/uucico -r1 -sother
A
relative time specification cannot use a.m. or p.m. format together.
The third form removes item n from the event
list: > sched
1 Wed Apr 4 15:42 /usr/lib/uucp/uucico -r1 -sother
2 Wed Apr 4 17:00 set prompt=[%h] It's after 5; go home: >
> sched -2
> sched
1 Wed Apr 4 15:42 /usr/lib/uucp/uucico -r1 -sother
A
command in the scheduled-event list is executed just before the first
prompt is printed after the time when the command is scheduled. It
is possible to miss the exact time when the command is to be run,
but an overdue command will execute at the next prompt. A command
which comes due while the shell is waiting for user input is executed
immediately. However, normal operation of an already-running command
will not be interrupted so that a scheduled-event list element can
be run.This mechanism is similar to, but not the same as, the at command on some UNIX systems. Its major disadvantage is that it might not run a command at exactly the specified time. Its major advantage is that because sched runs directly from the shell, it has access to shell variables and other structures. This provides a mechanism for changing one's working environment based on the time of day.
tcsh