From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 15:29:28 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0A95116A417 for ; Thu, 23 Aug 2007 15:29:28 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id CE40C13C468 for ; Thu, 23 Aug 2007 15:29:27 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id B0C9E47BA7; Thu, 23 Aug 2007 11:29:26 -0400 (EDT) Date: Thu, 23 Aug 2007 16:29:26 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Peter Jeremy In-Reply-To: <20070823101737.GA1161@turion.vk2pj.dyndns.org> Message-ID: <20070823162802.T2662@fledge.watson.org> References: <20070823101737.GA1161@turion.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: idprio(1) broken in recent -current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Aug 2007 15:29:28 -0000 On Thu, 23 Aug 2007, Peter Jeremy wrote: > Following my latest -current update (to 17th August), setiathome stopped > working and started complaining about missing heartbeats. After rebuilding > all the ports and a bit of hair removal, I tracked the problem to the > 'idprio' command in /usr/local/etc/rc.d/boinc - without that, all works > fine. If I include that, boinc_client stops sending heartbeat messages. > > This was working correctly in late June. > > Has anyone else seen anything similar? When I run "idprio 20 echo hi", it seems to execute per normal as root, and not at all as an unprivileged user, which I think is the desired symptom of using it. I've not tried checking that things execute occasionally with a mostly busy system, so could you be more specific about what you're seeing? If you're running things with idprio, is it definitely the case that your system is sometimes idle allowing the program to run once in a while? Robert N M Watson Computer Laboratory University of Cambridge