Kern Sibbald wrote:
Can you confirm either by testing or from your knowledge of the problem that
it does not occur if there are not simultaneous jobs using Python. If this
is the case, let me know and I'll work on adding a correct recursive lock
that allows only one Bacula thread at a time in the Python libraries ...
Hmm... tricky. Of course, any change I make has a good chance of
preventing the segfault, so I'm not sure if this proves anything, but
here 'ya go: I spaced the three jobs out to start one minute apart and
changed the file sets to back up more data (enough to make the backup
jobs take about ten minutes to run). This ensured the Python init
scripts wouldn't run at the same time, but made sure that (after the
third minute) all three jobs would be "active" (running or waiting) at
the same time. Sure enough, the segfault was prevented, however I'm not
sure if this was because there was only one instance of Python running
at any given time or because I'd simply perturbed the race condition. I
think that's the best test I can do, but if you have an alternate
suggestion, I'd be happy to try it out.
Thanks,
- Cedric
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
