From owner-freebsd-current@FreeBSD.ORG Thu Feb 3 11:18:20 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 209D016A4CE; Thu, 3 Feb 2005 11:18:20 +0000 (GMT) Received: from mail.qubesoft.com (gate.qubesoft.com [217.169.36.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4EB8943D2D; Thu, 3 Feb 2005 11:18:19 +0000 (GMT) (envelope-from dfr@qubesoft.com) Received: from [192.168.1.254] (dhcp254.qubesoft.com [192.168.1.254]) by mail.qubesoft.com (8.13.1/8.13.1) with ESMTP id j13BHRvO031666; Thu, 3 Feb 2005 11:18:14 GMT (envelope-from dfr@qubesoft.com) In-Reply-To: <20050203021603.L583@localhost> References: <20050201101113.J572@localhost> <200502011913.j11JDXsf084862@khavrinen.lcs.mit.edu> <20050202094256.K88344@localhost> <200502031012.22602.dfr@nlsystems.com> <20050203021603.L583@localhost> Mime-Version: 1.0 (Apple Message framework v619.2) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Doug Rabson Date: Thu, 3 Feb 2005 11:18:13 +0000 To: Julian Elischer X-Mailer: Apple Mail (2.619.2) X-Spam-Status: No, score=-2.8 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.0.1 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on mail.qubesoft.com X-Mailman-Approved-At: Thu, 03 Feb 2005 12:53:32 +0000 cc: Peter Jeremy cc: freebsd-current@freebsd.org cc: current@freebsd.org cc: Garrett Wollman Subject: Re: cynchronised sleep capbilty.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 03 Feb 2005 11:18:20 -0000 On 3 Feb 2005, at 10:17, Julian Elischer wrote: > On Thu, 3 Feb 2005, Doug Rabson wrote: > >> On Wednesday 02 February 2005 17:44, Julian Elischer wrote: >>> very clever! >>> >>> however it doesn't phaselock to teh time and still drifts. >>> I need to trigger on (for example) 10 second boundaries across 50 >>> synchronised machines.. >>> (so thatthe machines agree about the sampling period.) >> >> How about a cron job which writes characters into a fifo every ten >> secconds. The script can wait for the next ten second mark by reading >> a >> single char from the other end of the fifo. > > how does a cron job run evey 10 seconds? > also this woudl seem something that is a bit beyond > a simple shell script in terms of trouble you would go to. A very good point - I forgot that cron only goes down to minute resolution :-) >