MobileRead Forums - View Single Post

chaley · 04-20-2010, 01:34 PM

Try running 'calibre-debug -g' instead of calibre.

I built a task specification to run a .bat file that sets a few environment variables (because I didn't want the test to touch my real library), then runs calibre-debug -g. It runs it every 5 minutes, killing it after 1. It has been happily doing this for 20 minutes. I haven't tried running it when I am not logged in, so can't say whether not having a screen will cause the GUI difficulties.

I suspect that running calibre-debug gives the task scheduler a convenient process to kill.

04-20-2010, 01:34 PM	#5
chaley Grand Sorcerer Posts: 12,456 Karma: 8012886 Join Date: Jan 2010 Location: Notts, England Device: Kobo Libra 2	Try running 'calibre-debug -g' instead of calibre. I built a task specification to run a .bat file that sets a few environment variables (because I didn't want the test to touch my real library), then runs calibre-debug -g. It runs it every 5 minutes, killing it after 1. It has been happily doing this for 20 minutes. I haven't tried running it when I am not logged in, so can't say whether not having a screen will cause the GUI difficulties. I suspect that running calibre-debug gives the task scheduler a convenient process to kill.