Michael Lueck wrote:
A Williams wrote:
Michael Lueck wrote:
One remaining question... is there some command line way to instruct SM
to gracefully exit if possible (no unsaved emails open, etc...)? I would
require that if I am to automate a daily local backup.
That sounds very risky. Why not test for the existence of the SM
lock-file? There has to be a better solution.
I leave SM up "all the time". To do nightly automated backups, I would
have to send SM a message to exit, do the backup, the restart it.
I would check for the mentioned lock-file, and if that still exists,
skip the backup and log the error.
Seems pretty straight forward to me.
Sincerely,
My backup program allows issuance of a command (Windows .bat or .cmd
file) prior to running a scheduled backup. Before any of my systems
image their system drive (where the SM profile is stored) a "kill
SeaMonkey process" batch file runs, checks for an instance of SM in
memory, kills the process (if it exists), and then the backup program
executes the scheduled backup.
I use similar conditional testing for copying my master calendar program
(which is maintained on my server) to my laptops. That is, the batch
file checks to see if the calendar program is running on the laptop
before trying to copy the calendar file. If needed it kills the
calendar program's process and then copies the file.
If you want more info just ask.
--
Ed Mullen
http://edmullen.net/
"I'm too shy to express my sexual needs except over the phone to people
I don't know." - Garry Shandling
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
