> - stop assp > - remove the 'tmpDB' folder > - remove all griplist files in the assp-base folder > - start assp > > If assp crashes - some times the griplist files (e.g. BDB) are > destroyed . ASSP will redownload the griplist after the startup.
Thomas... given my own "been there done that", I think that ASSP should have some mean to tell if the last "shutdown" was correct, for example, by adding some "marker record" to the tables upon shutdown (removing it upon startup); this shouldn't cause too much startup slowdown but will, in turn, avoid "strange crashes" since in case ASSP crashed, such a code will tell it which tables /may/ be corrupted, so the code may then deal with that; all in all, it may even suffice checking for the "pid", it it's there, then ASSP crashed and, in such a case, some tables can't be trusted and may either be thrown away or ignored (till recovery); this includes the tmpDB (which may be deleted/re-created) and the griplist (which, as you said, will be re-downloaded) along with any other similar "DB" ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test
