From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S267979AbUH2OrN (ORCPT ); Sun, 29 Aug 2004 10:47:13 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S267974AbUH2OrN (ORCPT ); Sun, 29 Aug 2004 10:47:13 -0400 Received: from lamity.org ([212.13.197.69]:2200 "HELO lamity.org") by vger.kernel.org with SMTP id S267976AbUH2Onl (ORCPT ); Sun, 29 Aug 2004 10:43:41 -0400 Date: Sun, 29 Aug 2004 15:43:38 +0100 From: "Simon Brackenboro'" To: linux-kernel@vger.kernel.org Subject: setitimer and timeval truncation Message-ID: <20040829144338.GA14679@lamity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6+20040803i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org This email relates to a discussion on prjware@multivac.cwru.edu You can receive a digest of the thread by sending a email to prjware-get.560_569@multivac.cwru.edu I would expect setitimer to work over the range of time allowed by struct timeval. This is not always the case as as timeval is truncated in timeval_to_jiffies to MAX_SEC_IN_JIFFIES (~25 days in my case). Is this right ? -- sb