In message <[EMAIL PROTECTED]>,
Kent Stewart <[EMAIL PROTECTED]> wrote:
>It also sounds like he isn't getting enough outside air. You can't
>cool if the inside air is hot.
Right!
I have bought three ``slot fans'' now for different systems I own, and I'm
very happy with them. Two I bought fro
> I had one system with two VERY hot SCSI drives in it, and one of these
> slot fans really made a major difference. (Both drives are now always
> only just barely warm to the touch, whereas before, they were practically
> on fire.)
Got a couple of those (DEC RZ26 & RZ28) with old 486 cooling f
On Wed, 29 Dec 1999, Ted Sikora wrote:
> Marc Nicholas wrote:
> >
> > You're referring to the temps reported via an LM78 or similar, yes?
> The machines bios with Winbond W83782d IC
>
That may explain it, then.
> > not reporting that the machine is actually getting HOTTER under FreeBSD?
>
Marc Nicholas wrote:
>
> You're referring to the temps reported via an LM78 or similar, yes?
The machines bios with Winbond W83782d IC
> not reporting that the machine is actually getting HOTTER under FreeBSD?
It is HOTTER under FreeBSD. Immediatelly upon boot-up it's 26F
hotter under FreeBSD
Kent Stewart wrote:
>
> David Kelly wrote:
> >
> > Peter Wemm writes:
> > > Ted Sikora wrote:
> > >
> > > > During the night periodically my temp warning has been going off.
> > > > I have it set to 118F. This happens only under FreeBSD. Linux continues
> > > > to run cool at the old temperatures
I'm trying to find some information on reasonable settings for
debug.max_softdeps on a recent FreeBSD-stable system.
It seems that if you have a machine that is able to generate disk IO
much faster than can be handled, has a large amount of RAM (and therefore
debug.max_softdeps is large), an
Daniel O'Connor wrote:
> On 29-Dec-99 Ken Bolingbroke wrote:
>> From my own experience, altho I'm not that skilled a programmer,
>> sleep()
>> is not thread-safe. I believe sleep() sets a global SIGALARM, which
>> is
>> reset by every thread that calls it, and thus only the last one ever
>>
On 29-Dec-99 Ken Bolingbroke wrote:
> From my own experience, altho I'm not that skilled a programmer,
> sleep()
> is not thread-safe. I believe sleep() sets a global SIGALARM, which
> is
> reset by every thread that calls it, and thus only the last one ever
> returns. Replacing sleep() w
In the last episode (Dec 29), Charlie Root said:
> I expect (want) a runtime error but I do expect it to compile when
> linked with the openldap libraries. Here's my quandery:
>
> vv# gcc -L/usr/local/lib -I/usr/local/include -lldap -llber test.c
> /tmp/ccj67244.o: In function `main':
> /tmp/ccj6
David Kelly wrote:
>
> Peter Wemm writes:
> > Ted Sikora wrote:
> >
> > > During the night periodically my temp warning has been going off.
> > > I have it set to 118F. This happens only under FreeBSD. Linux continues
> > > to run cool at the old temperatures. Apparantly some code change has
>
Peter Wemm writes:
> Ted Sikora wrote:
>
> > During the night periodically my temp warning has been going off.
> > I have it set to 118F. This happens only under FreeBSD. Linux continues
> > to run cool at the old temperatures. Apparantly some code change has
> > caused this. Does anyone know exa
Hello all,
In an attempt to help Cameron get newpcm to support widest array of
soundcards available we're trying to collect as many as possible for
testing and development.
Below is a list of chipsets that we're still lacking. If you have any
cards that have these chips on them, and would like
I have a tiny little snippit of code here (test.c):
char ldap_init();
int main(int argc, char **argv)
{
ldap_init();
return 0;
}
I expect (want) a runtime error but I do expect it to compile when
linked with the openldap libraries. Here's my quandery:
vv# gcc -L/usr/local/lib -I/usr/local/i
>From my own experience, altho I'm not that skilled a programmer, sleep()
is not thread-safe. I believe sleep() sets a global SIGALARM, which is
reset by every thread that calls it, and thus only the last one ever
returns. Replacing sleep() with nanosleep() or something else that is
thread-safe
Hello,
first let me thank all of you for all your great help and the dozens
of responses I got.
Unfortunately I have a very strange problem in a multithreaded
programm I'm writing now. I want to write a programm which
checks if a server is up by pinging it. I looks like that:
###
Ted Sikora wrote:
> During the night periodically my temp warning has been going off.
> I have it set to 118F. This happens only under FreeBSD. Linux continues
> to run cool at the old temperatures. Apparantly some code change has
> caused this. Does anyone know exactly where I should look?
The
You're referring to the temps reported via an LM78 or similar, yes? And
not reporting that the machine is actually getting HOTTER under FreeBSD?
-marc
---
Marc Nicholas netSTOR Technologies, Inc. http://www.netstor.com
"Fast, Expan
Here's a strange problem. I run Linux stable/development kernels
and FreeBSD-3-STABLE on a SMP dual-boot workstation. The machines
temperatures have always been in this range with either system:
87F CPU #0
87F CPU #1
95F Case Temp
Sometime last week or early this week the temperature under FreeB
I seem to remember someone else asking about this a couple weeks back.
Does anyone know a good place to go to buy a cheap server system? This
is a sit-in-the-corner box that is a compute-processor and a very
lightly loaded WWW server, similar to what freefall does.
I'd like to spend around $500
you were subscribed to only one list "freebsd-hackers-digest".
i have removed you from that list.
jmb
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
I just wanted to say thanks to those who responded to my questions on
the topic of SIGFPE and X_INV vs X_OFL. I found the answers most
helpful, especially the references to Bruce's mail in the archives. ;-)
Ciao,
Sheldon.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebs
Please, remove my name from your mailing lists.
Thank you.
Jean Drabbe
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
22 matches
Mail list logo
