> Most likely it's a contention issue on the bulletin database.  The 
> current architecture requires each session to obtain an exclusive 
> lock on the bulldb for a short time.  With many simultaneous 
> connections, some won't be able to do so before they time out.  This 
> is discussed in the Administrator's Guide.  You can (a) increase the 
> number of attempts each session makes, (b) turn on 'bulldb-nonfatal' 
> option, or (c) stop using a database to store the last seen bulletin.

Thanks.
Well, (b) should take care of the problem.  

What DB format does qpopper use for storing bulletin information?  In
the event that I decide to switch away from using the bulldb, I would
like to be able to dump the output so I can update the users .popbull
files.  I tried db_dump, but it was the wrong format.



> 
> (One long-term solution would be to have a Qpopper bulletin database 
> process which owns the lock and serves requests by the other Qpopper 
> processes.)

Any possibility of this happening in the near future?  :-)

                                                      .~.
                                                      /v\
--                                                   // \\
JA                                                  /(   )\
                                                     ^`~`^
                                                   L I N U X
[-----------------------------------------------------------]
 Justin Ainsworth                    Systems Administrator &
 PHONE: (530) 879-5660x108      Technical Support Supervisor
 FAX:   (530) 879-5676                        Sunset Net LLC
 WEB:   http://www.sunset.net              1915 Mangrove Ave   
 EMAIL: [EMAIL PROTECTED]                       Chico, CA 95926  
[-----------------------------------------------------------] 

Reply via email to