On 8/10/05, Julien Gabel <[EMAIL PROTECTED]> wrote:
> >> Regrettably, i always encountered this problem. I spoke about that
> >> since the middle of 2004, and didn't really receive feedback on this.
> >> I try a lot of things but none worked better than the other.
> >>
> >> To not forget about it,
Julian Elischer writes:
| just placing an unmounted drive down on a hard table, even when
| not running, can ruin it. We lost hundreds that way at Whistle until
| we did a failure analysis. Just placing a rubber mat on the table.
| fixed it and instructing the staff to always put the drives on
| a
On Fri, 19 Aug 2005, Christophe Yayon wrote:
> Hi all
>
> You should know about freebsd and nagios 2.0b threads issues (100% cpu
> use by a forked process, lost check result, some pause of nagios main
> process in certains obscursives conditions...).
>
> Some Nagios developpers says that the probl
On Fri, 19 Aug 2005, Christophe Yayon wrote:
> Hi Daniel,
>
> i have already read this post, i am in freebsd 5.4-stable of August on a
> SMP server and i have the problem...
>
> The post which you suggest do not explain anything, or i missed something ?
The post said that nagios did not work with
Hi Daniel,
i have already read this post, i am in freebsd 5.4-stable of August on a
SMP server and i have the problem...
The post which you suggest do not explain anything, or i missed something ?
Daniel Eischen wrote:
On Fri, 19 Aug 2005, Christophe Yayon wrote:
Hi all
You should kn
On Fri, 19 Aug 2005, Christophe Yayon wrote:
> Hi all
>
> You should know about freebsd and nagios 2.0b threads issues (100% cpu
> use by a forked process, lost check result, some pause of nagios main
> process in certains obscursives conditions...).
>
> Some Nagios developpers says that the probl
Hi all
You should know about freebsd and nagios 2.0b threads issues (100% cpu
use by a forked process, lost check result, some pause of nagios main
process in certains obscursives conditions...).
Some Nagios developpers says that the problem is in FreeBSD and some
other says that the problem
Bill Vermillion wrote:
"Bits dont fail me now!" was what
[EMAIL PROTECTED] muttered as he hastily typed
this on Fri, Aug 19, 2005 at 12:00 :
1. Re: Parking disk drive heads (Glenn Dawson)
The setups for parking heads pretty much went away when the move
from MFM drive to ATA technology.
On Fri, Aug 19, 2005 at 10:11:30AM -0400, Bill Vermillion wrote:
> "Bits dont fail me now!" was what
> [EMAIL PROTECTED] muttered as he hastily typed
> this on Fri, Aug 19, 2005 at 12:00 :
>
> >1. Re: Parking disk drive heads (Glenn Dawson)
>
> > Message: 1
> > Date: Wed, 17 Aug 2005 12:47:32
On Friday 19 August 2005 14:26, Jeremie Le Hen wrote:
> Hi Hans,
>
> [ this topic should live on -current@ ]
>
> > I'm just wondering. Things used to work on my old 200MHz pentium, but
> > recent changes made to FreeBSD-6/7 current break things. This is what
> > dmesg shows:
>
> I understand that t
"Bits dont fail me now!" was what
[EMAIL PROTECTED] muttered as he hastily typed
this on Fri, Aug 19, 2005 at 12:00 :
>1. Re: Parking disk drive heads (Glenn Dawson)
> Message: 1
> Date: Wed, 17 Aug 2005 12:47:32 -0700
> From: Glenn Dawson <[EMAIL PROTECTED]>
> Subject: Re: Parking disk drive
Hi Hans,
[ this topic should live on -current@ ]
> I'm just wondering. Things used to work on my old 200MHz pentium, but recent
> changes made to FreeBSD-6/7 current break things. This is what dmesg shows:
I understand that trying multiple kernels on such a system is not an
option, unless - and
Hi,
Maybe someone more experienced than me could help me out with this...
(kgdb) bt
#0 doadump () at pcpu.h:159
#1 0xc060c5ef in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:410
#2 0xc060c915 in panic (fmt=0xc07fd250 "%s") at
/usr/src/sys/kern/kern_shutdown.c:566
#3 0xc07b26d4 in tr
Hi Michael,
> > If it should work, was it broken back in 4.8 and, if so, when
> > was it corrected? I'd rather not take the time up upgrade the
> > box to 4.11 if I'll then be forced to move to 5.4.
>
> There were changes in dummynet's configuration functions that, among
> other things,
Hi,
I'm just wondering. Things used to work on my old 200MHz pentium, but recent
changes made to FreeBSD-6/7 current break things. This is what dmesg shows:
atapci0: port
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 7.1 on pci0
ata0: on atapci0
ata1: on atapci0
fdc0: at port
On Thu, Aug 18, 2005 at 11:19:37PM +0200, Uwe Doering wrote:
> There were changes in dummynet's configuration functions that, among
> other things, dealt with protecting certain code sequences with the
> proper SPL. They went into the CVS repository after 4.8. I can't tell
> whether these fix
16 matches
Mail list logo
