I think that the corrent manner is to have a clean shutdown on James. I don't have a database to store mailing. If someone doesn't have a database, the kill-down method keeps old messages in the inboxes folders permanently until you do a manual cleanup (rm or del.....)
+--------------------------------------------------------------------------+ Aujac (Associaci� d'Usuaris de Java de Catalunya) WWW: http://www.aujac.org F�rum Aujac: http://www.aujac.org/serveis/nexus?ACTION=FORUM&ID_FORUM=1 Adreces electr�niques de contacte: Informaci� general: [EMAIL PROTECTED] Per establir un conveni amb l'Aujac: [EMAIL PROTECTED] Per establir projectes amb les universitats: [EMAIL PROTECTED] Per fer-vos soci : https://www.aujac.org/seccioSocis/altaSoci.xml Si sou una empresa, instituci� o organitzaci� i voleu fer-vos socis, feu-ho a trav�s de: https://www.aujac.org/seccioSocis/altaSociEmp.xml Gr�cies!!! +--------------------------------------------------------------------------+ ----- Original Message ----- From: "Oki DZ" <[EMAIL PROTECTED]> To: "James Users List" <[EMAIL PROTECTED]> Sent: Wednesday, May 15, 2002 8:39 AM Subject: Re: A very simple question On 05/11 14:28 Jordi Pujol wrote: > I know that the only feature to stop James is throught the RemoteManager > (telnet). > > But what's happen under a system reboot? The stop script for James basically kills the JVM where James runs on; since I put the repositories on a database, everything seems to be allright. On a system reboot, the stop script will be executed. Oki -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
