Okay, now it's been what - 3 weeks? And as far as I can tell nobody has even looked at this problem.
What exactly needs to be done to get these issues investigated? 1. bacula-dir dies for reasons unknown when starting a backup that uses identical configuration to other systems 2. bacula traceback documentation is incorrect and out of date 3. bacula traceback apparently only works on linux due to undocumented dependancies I've sent documentation on all of these problems to the list DOZENS of times. About one in every 12 messages actually reaches the list, so 4. WTF is happening with sourceforge? Time to move the mailing list? On Jul 19, 2006, at 11:40 AM, Kern Sibbald wrote: > On Wednesday 19 July 2006 20:07, Jo Rhett wrote: >> On Sun, Jul 09, 2006 at 08:45:27PM +0200, Kern Sibbald wrote: >>> The seg fault, is not good. However, I cannot do anything without >>> the proper >>> kind of information as indicated on the Support page as well as a >>> traceback >>> as described in the Kaboom chapter of the manual. If you have that >>> information (traceback and your system info) and the problem is a >>> seg fault, >>> then please open a bug report in the bugs database. >> >> I did what you suggested and opened a bug and then you turned right >> around >> and close the bug with this: >> >> kern - 07-14-2006 02:44 PDT >> This is a configuration error. Please ask for help on the bacula- >> users >> list and send them the information you have provided here. >> >> Okay, so we're back to square one. > > I'd say we are back to square zero. > >> Can we try again? > > Yes, of course, but please note: Your first email did not contain > all the > information that was in the bug report, which is why in the bug > report, with > more information, I concluded that the problem was *most likely* a > configuration error. I then asked you to: "ask for help on the > bacula-users > list and send them the information you have provided here", so now > you need > just provide the info you put into the bug report, and perhaps > someone will > point you to the permissions error that Bacula reported, which is > clearly the > starting point for resolving the problem. > > ---------------------------------------------------------------------- > --- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to > share your > opinions on IT & business topics through brief surveys -- and earn > cash > http://www.techsay.com/default.php? > page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users -- Jo Rhett senior geek Silicon Valley Colocation ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
