On Jul 19, 2006, at 10:08 PM, Ryan Novosielski wrote:
Providing proper information for FREE support from a bunch of
people who
are in the same boat you are really isn't too much to ask. I
suggest you
adjust your attitude.
Copying the same information back and forth between mailing lists
On Tue, 25 Jul 2006, Jo Rhett wrote:
Okay, now it's been what - 3 weeks? And as far as I can tell nobody
has even looked at this problem.
Bacula is user-supported software.
From what I've seen on the list, you have provided inadequate information
about what is going wrong, have not spent
On Jul 26, 2006, at 8:16 PM, Dan Langille wrote:
1. bacula-dir dies for reasons unknown when starting a backup that
uses identical configuration to other systems
Ouch. That's bad. Something must be different.
Nothing is different other than the hostname of the system and the
password
On 28 Jul 2006 at 9:36, Jo Rhett wrote:
On Jul 26, 2006, at 8:16 PM, Dan Langille wrote:
1. bacula-dir dies for reasons unknown when starting a backup that
uses identical configuration to other systems
Ouch. That's bad. Something must be different.
Nothing is different other than
On Jul 28, 2006, at 3:52 AM, Alan Brown wrote:
Bacula is user-supported software.
Thanks! I never knew that. Gee, this is my first open source
project, right?
From what I've seen on the list, you have provided inadequate
information
about what is going wrong, have not spent any time
On Jul 28, 2006, at 9:50 AM, Dan Langille wrote:
This email is a fine example of exactly why people are not queuing up
to help you.
I have raised dozens of legitimate issues repeatedly and constantly,
and received nothing but condescending replies. And when it
irritates me enough to call
On Fri, 28 Jul 2006 09:36:28 -0700, Jo Rhett said:
I
can't even get a simple answer on what library is used by the
traceback module so that I can find it, compile it, and get traceback
working.
Bacula doesn't use a
On Fri, 28 Jul 2006 09:36:28 -0700, Jo Rhett said:
can't even get a simple answer on what library is used by the
traceback module so that I can find it, compile it, and get traceback
working.
On Jul 28, 2006, at 1:07 PM, Martin Simmons wrote:
Bacula doesn't use a third-party library for
On Jul 28, 2006, at 1:55 PM, Jo Rhett wrote:
The manual is out of date. In particular, the mail commands don't
exist (it uses bsmtp now) and the traceback module uses a dbx
library/database of some sort. I can find no documentation for
what this is.
gcore -o /var/db/bacula/${PNAME}
On Fri, 28 Jul 2006 13:55:10 -0700, Jo Rhett said:
On Fri, 28 Jul 2006 09:36:28 -0700, Jo Rhett said:
can't even get a simple answer on what library is used by the
traceback module so that I can find it, compile it, and get traceback
working.
On Jul 28, 2006, at 1:07 PM, Martin
On Fri, 2006-07-28 at 13:55 -0700, Jo Rhett wrote:
The manual is out of date. In particular, the mail commands don't
exist (it uses bsmtp now) and the traceback module uses a dbx library/
database of some sort. I can find no documentation for what this is.
gcore -o
On 28 Jul 2006 at 9:59, Jo Rhett wrote:
On Jul 28, 2006, at 9:50 AM, Dan Langille wrote:
This email is a fine example of exactly why people are not queuing up
to help you.
I have raised dozens of legitimate issues repeatedly and constantly,
and received nothing but condescending
On 25 Jul 2006 at 12:18, Jo Rhett wrote:
Okay, now it's been what - 3 weeks? And as far as I can tell nobody
has even looked at this problem.
That may or may not be true What is true is that nobody is under any
obligation to do anything. We are volunteers.
What exactly needs to be done
On Wed, Jul 19, 2006 at 02:41:06PM -0400, Ryan Novosielski wrote:
Send them the information you have provided here.
Something tells me something is missing from this e-mail. ;) If not,
then I can completely understand why the bug report was closed. ;)
On Jul 20, 2006, at 12:44 AM, Kern
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bottom line now is that we've had HOW many e-mails go back and forth
without you sending any relevant or on-topic information? I'd still be
willing to take a crack at whatever is bothering you (despite the fact
that you suggested I was lacking in
On Thursday 20 July 2006 03:37, Jo Rhett wrote:
On Wed, Jul 19, 2006 at 02:41:06PM -0400, Ryan Novosielski wrote:
Send them the information you have provided here.
Something tells me something is missing from this e-mail. ;) If not,
then I can completely understand why the bug report was
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
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Send them the information you have provided here.
Something tells me something is missing from this e-mail. ;) If not,
then I can completely understand why the bug report was closed. ;)
Jo Rhett wrote:
On Sun, Jul 09, 2006 at 08:45:27PM +0200, Kern
On Wed, Jul 19, 2006 at 08:40:44PM +0200, Kern Sibbald wrote:
I'd say we are back to square zero.
Yes, I've given all of the information it is possible to provide (given
that the documentation on bug reporting is both out of date, and
irrelevant
for anything but Linux), and I have been
On Wed, Jul 19, 2006 at 02:41:06PM -0400, Ryan Novosielski wrote:
Send them the information you have provided here.
Something tells me something is missing from this e-mail. ;) If not,
then I can completely understand why the bug report was closed. ;)
Okay, so you've proved that you're a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've proven myself as a volunteer who does not have the time to look at
the bug report system in order to assist you with your problem. In fact,
I'm sure that there's been an occasion that I've been derilect myself as
far as reporting bugs even when
Hello,
The Broken pipe is a network error and is quite common if you are having
networking problems.
I've never seen the Director silently die as you say.
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
24 matches
Mail list logo