Steen Jansdal wrote: > Maybe it would be a good idea to implement some sort of > nightly backup routine into James, especially if we are > going to use an embedded database like derby or hsqldb. > Then we have a self contained mail server that doesn't > depend on external programs.
Personally I feel that adding non-mail processing behaviour to James is a bad thing. Far better to use the right tool for the job adding hooks to James to put it in the correct state as required. To halt the services using a database, put a database into backup mode, back it up and then reverse these actions use a scheduler. On *nix you could use cron, on most platforms you could use the far more capable Open Symphony Quartz scheduler (http://www.opensymphony.com/quartz/). -- Steve --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
