From owner-freebsd-current Thu Mar 2 22:45:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 4866137B611 for ; Thu, 2 Mar 2000 22:45:36 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gorean.org (doug@master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id WAA73444; Thu, 2 Mar 2000 22:45:00 -0800 (PST) (envelope-from Doug@gorean.org) Message-ID: <38BF5F6B.98D801AC@gorean.org> Date: Thu, 02 Mar 2000 22:44:59 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 4.0-CURRENT-0229 i386) X-Accept-Language: en MIME-Version: 1.0 To: Peter Dufault Cc: Bruce Evans , Matthew Dillon , Wes Morgan , Ollivier Robert , freebsd-current@FreeBSD.ORG Subject: Re: ntpd hanging machine References: <200003030045.TAA42128@hda.hda.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 over a year on 2.2.8, 3.2+ and 4.0 systems and never had a problem. Sounds like it fell just into your parameters here though. Perhaps a stern warning in the man page(s) is in order here? I had no idea I was making land mines for myself here. :) Doug -- "Welcome to the desert of the real." - Laurence Fishburne as Morpheus, "The Matrix" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message