On Friday 19 March 2010 20:46:30 Eric Bollengier wrote: > Le Vendredi 19 Mars 2010 20:41:40, Kern Sibbald a écrit : > > On Friday 19 March 2010 20:31:34 Hugh Brown wrote: > > > Kern Sibbald wrote: > > > > On Friday 19 March 2010 19:19:29 Eric Bollengier wrote: > > > > By the way, Hugh: If you are 99.9% sure that the problem comes from > > > > "alert" please don't submit a bug report. If there is a race > > > > condition, we definitely would like to see it. > > > > > > Sorry, I submitted a bug before I saw this. > > > > No problem, it was my oversight in the beginning ... > > > > > However, I'm able to > > > duplicate the hang fairly regularly; it shouldn't take too long to see > > > if the alert is the problem, and if it is the bug can be closed. > > > > If you are not convinced already 99.9% convinced it is the alert, which > > seems to be the case, then it is worth us looking at the details of the > > tracebacks > > I already looked the bactrace and the traceback file, and the thread who > have all locks is waiting for the alert command (bfgets in bsys.c).
Thanks. OK, I think the solution is for Hugh to: 1. Figure out why his alert command is broken 2. Create a script with a timer 3. Disable the alert Kern PS: I suppose that in some future version of Bacula, we could add a timer that triggers at 5 or 10 minutes. ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
