On Saturday 08 April 2006 15:31, Frank Sweetser wrote:
> On Sat, Apr 08, 2006 at 09:10:05AM +0200, Kern Sibbald wrote:
> > In any case, LD_ASSUME... should not be used with current 2.6 kernels.
> > In fact, if I am not mistaken, FC5 has removed support for old pthreads
> > so who knows what kinds
On Sat, Apr 08, 2006 at 09:10:05AM +0200, Kern Sibbald wrote:
> In any case, LD_ASSUME... should not be used with current 2.6 kernels. In
> fact, if I am not mistaken, FC5 has removed support for old pthreads so who
> knows what kinds of problems one will have.
Having tried it under FC5 on a di
On Saturday 08 April 2006 02:22, Joshua Kugler wrote:
> Sorry! I guess getting a SIGUSR2 isn't a big deal. I typed "continue" in
> gdb, and things resumed.
Yes, it is occassionally used by Bacula to "brutally" wake up another thread
-- usually in timers with the purpose of making that thread ex
Sorry! I guess getting a SIGUSR2 isn't a big deal. I typed "continue" in
gdb, and things resumed.
Sorry for the noise.
j- k-
On Friday 07 April 2006 16:20, Joshua Kugler wrote:
> On Friday 07 April 2006 13:18, Martin Simmons wrote:
> > > On Fri, 7 Apr 2006 10:56:53 -0800, Joshua K
On Friday 07 April 2006 13:18, Martin Simmons wrote:
> > On Fri, 7 Apr 2006 10:56:53 -0800, Joshua Kugler
> > <[EMAIL PROTECTED]> said:
> >
> > On Friday 07 April 2006 10:41, Kern Sibbald wrote:
> > > On Friday 07 April 2006 20:29, Joshua Kugler wrote:
> > > > Well, I rebooted with the nosm
> On Fri, 7 Apr 2006 10:56:53 -0800, Joshua Kugler <[EMAIL PROTECTED]> said:
>
> On Friday 07 April 2006 10:41, Kern Sibbald wrote:
> > On Friday 07 April 2006 20:29, Joshua Kugler wrote:
> > > Well, I rebooted with the nosmp kernel command line parameter, so there
> > > was only one processor
On Friday 07 April 2006 10:41, Kern Sibbald wrote:
> On Friday 07 April 2006 20:29, Joshua Kugler wrote:
> > Well, I rebooted with the nosmp kernel command line parameter, so there
> > was only one processor visible. Still had the same crash.
>
> Given where the problem is occuring, that is not to
On Friday 07 April 2006 20:29, Joshua Kugler wrote:
> Well, I rebooted with the nosmp kernel command line parameter, so there was
> only one processor visible. Still had the same crash.
Given where the problem is occuring, that is not too surprising.
> With bsmtp again.
> Is it time to give u
Well, I rebooted with the nosmp kernel command line parameter, so there was
only one processor visible. Still had the same crash. With bsmtp again. Is
it time to give up and install 1.38?
Any ideas? Any comments?
j- k-
[Thread 278542 (LWP 6596) exited]
Cannot find thread 278542: in
