The Bacula manual recommends that you test your conf files with ./bacula-xx -t ...
This will clearly indicate what is wrong and where (in 99.9% of the cases). If you run Bacula as a daemon, due to the flexibility in Bacula error message handling, it is very hard to get the user's attention, so Bacula attempts to produce a traceback, which for some reason in your case seems to be configured incorrectly. This also would have indicated what the problem is. Finally, yes Bacula does use SEGFAULT to generate tracebacks when it aborts, because it is the only portable way of doing so (the Unix abort() is not portable). This is not a bug and should be closed. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
