I just realised I made the mistake of replying to Ayan directly so now here is my reply (again) to the list: I've had the same problem. Some time ago I modified the code to randomize the wait period but that doesn't seem to have helped all that much as a quick grep of todays logs shows 12 occurences of this error. Having it ignore the error (at least as an option) would be great IMHO. I really don't care if the user manages to check their mail once without getting a bulletin but would prefer not to have to live without the feature altogether. Perhaps I'll dig in the code again at a later date if someone else hasn't done it for me. Right now I'm trying to sort out a new PABX system whilst investigating SLB & NAS solutions. Jon Ayan George wrote: > I've read that this is a locking issue and I see that it makes > multiple attempts to read the database. I wonder if it makes sense > to make the inability to read the bulldb a reason for a catastrophic > failure. If not, then is there a way to make popper ignore errors > reading the bulldb and continue to allow access to the user's mail > spool? -- Jonathan Benson Systems Administrator Ocean Internet http://www.ocean.com.au/
