View Single Post
Old 04-07-2014, 04:19 PM   #2
aleyx
Addict
aleyx can self-interpret dreams as they happen.aleyx can self-interpret dreams as they happen.aleyx can self-interpret dreams as they happen.aleyx can self-interpret dreams as they happen.aleyx can self-interpret dreams as they happen.aleyx can self-interpret dreams as they happen.aleyx can self-interpret dreams as they happen.aleyx can self-interpret dreams as they happen.aleyx can self-interpret dreams as they happen.aleyx can self-interpret dreams as they happen.aleyx can self-interpret dreams as they happen.
 
Posts: 245
Karma: 20386
Join Date: Sep 2010
Location: France
Device: Cybook Diva
You're welcome ^_^

Some ideas:

After the update one-liner, it may be useful to test for the success (or failure) of the update, then run a separate .sh containing the calibre-server command(s) for your particular libraries. That way you don't have to relaunch the servers manually. You can also use that separate .sh at boot time.

Maybe also sending a mail with a little blurb (whether there was an update, whether it succeeded...)

Also, between the killall and the oneliner, a backup.sh would be nice. Although anyone savvy enough to use this script should already have a nigthly backup in place, so maybe not?

For those who are a little wary about messing with their crontab, just linking calibre-update.sh into /etc/cron.daily (or /etc/cron.weekly) can be an adequate solution.

N.
aleyx is offline   Reply With Quote