Jobs Log

bbildman · 09-04-2016, 01:35 PM

Is there such a thing as a log file (or a way to access it) for jobs from previous days; for instance, jobs are emptied after calibre closes down. I want ofttimes to look for a previous job I did, but once it closes, it's gone.

Any help appreciated.

eschwartz · 09-04-2016, 01:51 PM

No, as you observed, the jobs are emptied after calibre closes down.

However, job logs are printed to stdout when you run via the command-line with calibre-debug.

On Linux, I use the following script, to ensure I always run in debug mode and preserve a log of everything that happened:

Code:

[eschwartz@arch ~]$ cat ~/bin/calibre
#!/bin/bash

if [ $# -eq 0 ] || [[ "$1" = "--detach" ]]; then
    echo -e "\n\n\nStarting calibre at $(date).\n\n\n" >> "/tmp/calibre-debug-$USER.log" 2>&1
    calibre-debug -g 2>&1 | tee -a "/tmp/calibre-debug-$USER.log"
else
    /usr/bin/calibre "$@"
fi

DaltonST · 09-04-2016, 01:51 PM

Find the temporary directory where Calibre stores its job logs. Example: "C:\Windows\Temp\calibre_bws0wv\threaded_job_logs\ ..." The "bws0wv" is a random sequence that changes every time Calibre starts. You will have to copy all of the job logs to a permanent directory before exiting from Calibre.

DaltonST

bbildman · 09-04-2016, 01:54 PM

Ok, thanks guys

BetterRed · 09-04-2016, 05:33 PM

You can give calibre an alternate location for its temporary files via the CALIBRE_TEMP_DIR environment variable, see ==>> Environment variables

I would advise against using %systemroot%\Temp for this purpose. On Windows 10 at least, one has to jump though hurdles to open it, this to deter users from removing stuff Windows has written there, and I wouldn't 'trust' Windows not to delete data that an application might put there.

BR

09-04-2016, 01:35 PM	#1
bbildman Member Posts: 12 Karma: 10 Join Date: Jun 2010 Device: Kindle	Jobs Log Is there such a thing as a log file (or a way to access it) for jobs from previous days; for instance, jobs are emptied after calibre closes down. I want ofttimes to look for a previous job I did, but once it closes, it's gone. Any help appreciated.

09-04-2016, 01:51 PM	#2
eschwartz Ex-Helpdesk Junkie Posts: 19,421 Karma: 85400180 Join Date: Nov 2012 Location: The Beaten Path, USA, Roundworld, This Side of Infinity Device: Kindle Touch fw5.3.7 (Wifi only)	No, as you observed, the jobs are emptied after calibre closes down. However, job logs are printed to stdout when you run via the command-line with calibre-debug. On Linux, I use the following script, to ensure I always run in debug mode and preserve a log of everything that happened: Code: [eschwartz@arch ~]$ cat ~/bin/calibre #!/bin/bash if [ $# -eq 0 ] \|\| [[ "$1" = "--detach" ]]; then echo -e "\n\n\nStarting calibre at $(date).\n\n\n" >> "/tmp/calibre-debug-$USER.log" 2>&1 calibre-debug -g 2>&1 \| tee -a "/tmp/calibre-debug-$USER.log" else /usr/bin/calibre "$@" fi

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Can we move jobs up when running many news fetch jobs ?	mixedbag	Recipes	3	03-18-2016 12:26 AM
Where does self.log output to?	ireadtheinternet	Recipes	1	10-22-2014 01:42 PM
New Member Log In	rcota@ec.rr.com	Introduce Yourself	3	05-03-2008 10:46 AM

09-04-2016, 01:51 PM	#3
DaltonST Deviser Posts: 2,265 Karma: 2090983 Join Date: Aug 2013 Location: Texas Device: none	Find the temporary directory where Calibre stores its job logs. Example: "C:\Windows\Temp\calibre_bws0wv\threaded_job_logs\ ..." The "bws0wv" is a random sequence that changes every time Calibre starts. You will have to copy all of the job logs to a permanent directory before exiting from Calibre. DaltonST

09-04-2016, 01:54 PM	#4
bbildman Member Posts: 12 Karma: 10 Join Date: Jun 2010 Device: Kindle	Ok, thanks guys

09-04-2016, 05:33 PM	#5
BetterRed null operator (he/him) Posts: 21,633 Karma: 29710510 Join Date: Mar 2012 Location: Sydney Australia Device: none	You can give calibre an alternate location for its temporary files via the CALIBRE_TEMP_DIR environment variable, see ==>> Environment variables I would advise against using %systemroot%\Temp for this purpose. On Windows 10 at least, one has to jump though hurdles to open it, this to deter users from removing stuff Windows has written there, and I wouldn't 'trust' Windows not to delete data that an application might put there. BR

Advert

Advert