Get it from https://sourceforge.net/projects/gnome-schedule/files/.

- gaute

(and it contains a convenient debugging function that gets the name of the inotify event as a char *)

Gnome-schedule is a graphical user interface that leverages the power
of crontab (vixie-cron, dcron) and at to manage your crontab file and
provide an easy way to schedule tasks on your computer. It supports
recurrent (periodical) tasks and tasks that happen only once in the
future. It is written in Python using pygtk, and has been developed,
tested and packaged for various Linux distributions.

New in this release:
Apart from fixing a number of annoying bugs (including where you couldn’t enter times above 13:49), and long awaited X support. You should now be able to set up your X applications to be run by cron and at, and as long as you are logged in they will be run. This does depend on you having you X server running on the same DISPLAY. Please note that this feature is still experimental.

Previous release notes are available here: http://sourceforge.net/project/shownotes.php?release_id=572635

Download: https://sourceforge.net/project/downloading.php?group_id=112183&filename=gnome-schedule-2.1.0.tar.gz

Bugs: http://bugzilla.gnome.org/simple-bug-guide.cgi?product=gnome-schedule

For more information and screenshots see our homepage: http://gnome-schedule.sourceforge.net

git: git://github.com/gauteh/cruxports.git
web: http://github.com/gauteh/cruxports/tree/master

It mostly contains fixed and/or updated ports from various official and larger repos:

• rxvt-unicode – with 256 colors and packaged for nn_NO locales
• git
• libiconv
• ntfs-3g
• p5-xml-simple
• awesome

By using the experimental git driver for ports you can sync with this config:

/etc/ports/gaute.git:
# Collection by Gaute Hope <eg@gaute.vetsj.com>

URL=git://github.com/gauteh/cruxports.git
BRANCH=master
DESTINATION=/usr/ports/gaute

put the driver in the file /etc/ports/driver/git, you might have to change the git commands to use spaces and not ‘-’. I.e.: git-clone -> git clone.

Clone url: git://github.org/gauteh/gauteh.git
Tree: http://github.com/gauteh/gauteh/tree/master

• x11-utils/unclutter
• media-sound/cmus
• media-sound/mpeg4ip
• media-libs/libmpcdec
• media-libs/libart
• media-libs/libmodplug
• text-libs/libiconv
• sys-fs/ntfsprogs
• x11-apps/wbar
• x11-apps/wbarconf
• x11-apps/obmenu

- gaute

If something works; don’t proceed through the rest of the steps – they are meant as suggestions to solutions. And if you have it working they might break it. That means; no guarantees!

Gnome-schedule is a front-end to crontab and atd, and it is those that actually start the tasks. They have both been around since the beginning of time and were made for the command line, and don’t have any graphical interface.

Crontab is responsible for recurring tasks, scheduled for instance for ‘Every minute’ or ‘Every hour’.. but also quite complex expressions like every second minute of every fifth hour every 13th day of the month, but only if its wednesday. Atd schedules one-time tasks like ‘tomorrow‘ or 24th of December.

Crontab

First you need to have crontab installed (there are several; vixie-cron and dcron works well) use your package manager for this. After having installed it you have to tell your system that the cron daemon should be started at system start, check with your distro on how to do this.

To figure out if the crontab daemon is running you can do the following in a terminal:

$ ps aux | grep cron

This should give you a line ending with something similar to:  ‘/usr/sbin/crond’ .  If not; crontab is not running and you should make sure it is set up like your distro told you.

To check if it is installed you can do:

$ crontab -l

If this command is found; crontab is installed. (The output: no crontab for [username] means crontab is installed)

You need to make sure the crontab command has its SETUID bit set; to check do:

$ ls -l `which crontab`

The output should be similar to (the first -rwsr-xr-x letters should be exactly like this):

-rwsr-xr-x 1 root root 10076 2007-11-15 19:21 /usr/bin/crontab

You can fix this by doing (as root):

$ chmod +s `which crontab`

The cron.allow and cron.deny files, According to the Ubuntu wiki your user must either be in /etc/cron.allow (if it exists) or not be in /etc/cron.deny (if it exists). If neither exist only root can use crontab – this is not true for my system, but might be for Ubuntu.

To make a test task manually you can do the following commands:

$ crontab -e

You now get to edit a file, write this line:

* * * * * echo “Does this work?” > ~/test

See this crunchbang tutorial for details on what this does.

.. wait a minute ..

Check if there exists a file in you home directory, test, with the contents “Does this work?”. If it does, crontab is set up correctly. In that case, delete your crontab:

$ crontab -d

At

Install at and set it up, refer to you distributions documentation.

Check if atd is running:

$ ps aux | grep atd

As with crontab; this should give you a line ending with ‘/usr/sbin/atd‘. If not; at is not running, make sure it is installed and refer to your distro for starting the atd service.

To check if at is installed do:

$ at -V

This should give you:

at version 3.1.9
Bug reports to: rmurray@debian.org (Ryan Murray)
Garbled time

If not; at is not installed, refer to your distro for installing it through the package manager.

At should also have the SETUID bit set;

$ ls -l `which at`

This should give (the -rwsr-sr-x part should be exactly like this):
-rwsr-sr-x 1 daemon daemon 37660 2006-05-31 06:40 /usr/bin/at

Add it with (as root):

$ chmod +s `which at`

To try and make a task; do:

$ at 22:00 19.02.2009 # replace the date with something in the very near future

You know get a at prompt:

at> echo “I work” > ~/at_test
at> <Ctrl>+D

To list current jobs try:
$ atq

If a job shows up now it worked.

Wait for the scheduled time to pass and check the contents of at_test in your home dir; if it is there it worked.

Make sure that you are not listed in /etc/at.deny and that if you have something like an /etc/at.allow file, you are listed. Refer to the at man page.

Other resources:

http://en.wikipedia.org/wiki/At_(Unix)
http://en.wikipedia.org/wiki/Cron

Crontab man page – http://www.manpagez.com/man/5/crontab/
At man page – http://linux.die.net/man/1/at

Ubuntu Wiki – https://help.ubuntu.com/community/CronHowto
Crunchbang Tutorial – http://crunchbang.org/archives/2007/10/26/howto-setup-a-crontab-file/

X output

The X output feature for Gnome Schedule is now ready for testing, this means that you can easily schedule graphical applications without worrying about the DISPLAY variable. Gnome Schedule also checks before each run if there is a working X connection; in other words that you are logged in.

There is still needed some testing before the next version will be released and it would be great if you could try out the current development branch.

To get the sources do:
$ svn checkout http://svn.gnome.org/svn/gnome-schedule/trunk gnome-schedule

You can build and install it into a temporary directory by doing:
$ cd gnome-schedule/
$ ./autogen.sh –prefix=/path/to/tmp
$ make; make install

to run it from there do:
$ cd /path/to/tmp/bin
$ ./gnome-schedule

If you have any problems or suggestions file them on the gnome bugzilla. More details on how to build can be found in the README.

- gaute

07.02.2009 – Horndalsnuten, 1460 moh.

Vi kom til ca 1350m, før skodda stoppa oss. Meget bra å køyre ned igjen.. spesielt når det letta igjen.