Justin Forest wrote: >> This is the way to do it (although better use "crontab -e" like >> Sebastian suggested). Just make sure that you don't accidentally start >> gPodder while this console process is running. Currently, we do not >> check for other running instances, so if you happen to have gPodder >> running while this command is executed, expect unexpected behaviour :) > > Actually, you can't run two instances: the second attempt will fail with > an "SQLite: database is locked" error. So, no unexpected behaviour this > time. ;) Neat! This means we get single instance checking for free :) Now we just have to catch that error and display a nice error message so the user knows what's going on (instead of just erroring out). Thomas