Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Date: Mon, 30 Dec 2002 17:50:39 -0500
From: Christopher Faylor <cgf-cygwin@cygwin.com>
To: cygwin@cygwin.com
Cc: gbourgeois@yaccom.com
Subject: Re: setitimer failure
Message-ID: <20021230225039.GB16336@redhat.com>
Reply-To: cygwin-apps@cygwin.com
Mail-Followup-To: cygwin@cygwin.com, gbourgeois@yaccom.com
References: <GHEDJDAGJGMFPNAOIIBHEECJCAAA.gbourgeois@yaccom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <GHEDJDAGJGMFPNAOIIBHEECJCAAA.gbourgeois@yaccom.com>
User-Agent: Mutt/1.5.1i

On Mon, Dec 30, 2002 at 11:11:50AM +0100, gilles BOURGEOIS wrote:
>hello.
>I really have to know if the setitimer() primitive works well using cywgin
>dll
>I am currently using NT5.0 (2000)
>I call setitimer(ITIMER_VIRTUAL, &interval, NULL) and it returns -1 with bad
>argument as errno .
>I do not understand why, because my arguments seemes to be ok to me !
>Any help very appreciated.
>gilles

ITIMER_VIRTUAL is not implemented.

Sergey Okhapkin suggested changing the errno setting for this scenario to
ENOSYS, which I've done for the next release.

Btw, I've removed cygwin-apps from this discussion since this has nothing
whatsoever to do with cygwin-apps.

cgf
--
Please use the resources at cygwin.com rather than sending personal email.
Special for spam email harvesters: send email to aaaspam@sources.redhat.com
and be permanently blocked from mailing lists at sources.redhat.com

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

