Giuseppe,

> Is the locked "state" detectable in some way? Because if
> so, maybe there could be some special thing in the "init" script: it
> will start amavis in a way to preserve or create the DB
> (Amavis::DB::init(1)), and if after a certain timeout amavis is not yet
> started or would result locked, then it will try to start amavisd again
> with passing some command line option to tell to discard the DB as
> currently done (Amavis::DB::init(0)). WDYT? Is that feasible?

I haven't been able to find a way to detect it, except by trying to
open a database in a separate process, and kill it if it can't do it
in reasonable time. Even the bdb utility programs like db_dump and
db_recover just hang on such database.

  Mark

------------------------------------------------------------------------------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
is a gathering of tech-side developers & brand creativity professionals. Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, & 
iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian
Group, R/GA, & Big Spaceship. http://www.creativitycat.com 
_______________________________________________
AMaViS-user mailing list
AMaViS-user@lists.sourceforge.net 
https://lists.sourceforge.net/lists/listinfo/amavis-user 
 AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 
 AMaViS-HowTos:http://www.amavis.org/howto/ 

Reply via email to