On Sun, Sep 17, 2006 at 02:00:34PM +0400, Vladimir Stavrinov wrote: > There was few first lines (it is job resource) joined. But no > matter. There may be unlimited number of config errors. In any > way broken config should not cause segfault. Config should be > parsed and exact source of error (line number) should be > explicitly reported to stdout or log. Imagine, if apache segfault
Yes, I agree, and that is what Bacula normally does. However, if we don't have the config file that caused the segfault, I will have to close this bug report. Without that file, I don't think that anyone will have any chance of tracking down the root cause of the segfault. Do you still have the file available? -- John -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
