Peter Dufault wrote:
> It's probably almost safe to run a program
> rtprio or idprio if all you do is compute during that time and
> go back to time sharing before doing anything else, but be sure
> you're paged in, don't handle signals that way, etc...
I ran rc5des idprio'ed for well ov
> On Thu, 2 Mar 2000, Matthew Dillon wrote:
>
> > :> > merge. Until that point I was using the stock ntp4 from udel with no
> > :> > problems. But I tried the one shipping with 4.0 and it locks up completely
>
> > rtprio (and idprio) is virtually guarenteed to lockup your machine
> > ev
:
:On Thu, Mar 02, 2000 at 02:55:16PM -0800, a little birdie told me
:that Matthew Dillon remarked
:>
:> rtprio (and idprio) is virtually guarenteed to lockup your machine
:> eventually. Don't use either.
:
:Hm.
:I've run ntpd rtprio'd to 52 for over a year, under -CURRENT and
:RELENG_
On Thu, 2 Mar 2000, Matthew Dillon wrote:
> :> > merge. Until that point I was using the stock ntp4 from udel with no
> :> > problems. But I tried the one shipping with 4.0 and it locks up completely
> rtprio (and idprio) is virtually guarenteed to lockup your machine
> eventually. Don
On Thu, Mar 02, 2000 at 02:55:16PM -0800, a little birdie told me
that Matthew Dillon remarked
>
> rtprio (and idprio) is virtually guarenteed to lockup your machine
> eventually. Don't use either.
Hm.
I've run ntpd rtprio'd to 52 for over a year, under -CURRENT and
RELENG_2_2. Never
:> > merge. Until that point I was using the stock ntp4 from udel with no
:> > problems. But I tried the one shipping with 4.0 and it locks up completely
:> > (looks like a hardware lockup). The ntp4 from udel works completely
:> > though. Odd :)
:>
:> Yes, that's odd. I've never seen that... Ca
On Wed, 1 Mar 2000, Ollivier Robert wrote:
> According to Wes Morgan:
> > merge. Until that point I was using the stock ntp4 from udel with no
> > problems. But I tried the one shipping with 4.0 and it locks up completely
> > (looks like a hardware lockup). The ntp4 from udel works completely
> >
According to Wes Morgan:
> merge. Until that point I was using the stock ntp4 from udel with no
> problems. But I tried the one shipping with 4.0 and it locks up completely
> (looks like a hardware lockup). The ntp4 from udel works completely
> though. Odd :)
Yes, that's odd. I've never seen that
> On Mon, 28 Feb 2000, Matthew Frost wrote:
>
> > I'm experiencing some problems with ntpd. It would appear that a few
> > (10-15) minutes after I start it, the machine crashes completely...
> >
> > Feb 28 14:10:02 egrorian ntpd[153]: ntpd 4.0.99b Mon Feb 28 12:12:17 GMT 2000 (1)
> > Feb 28 14:
On Mon, 28 Feb 2000, Matthew Frost wrote:
> I'm experiencing some problems with ntpd. It would appear that a few
> (10-15) minutes after I start it, the machine crashes completely...
>
> Feb 28 14:10:02 egrorian ntpd[153]: ntpd 4.0.99b Mon Feb 28 12:12:17 GMT 2000 (1)
> Feb 28 14:10:02 egrorian
I'm experiencing some problems with ntpd. It would appear that a few
(10-15) minutes after I start it, the machine crashes completely...
Feb 28 14:10:02 egrorian ntpd[153]: ntpd 4.0.99b Mon Feb 28 12:12:17 GMT 2000 (1)
Feb 28 14:10:02 egrorian ntpd[153]: using kernel phase-lock loop 2040
Feb 28
11 matches
Mail list logo
