X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:message-id:from:to:cc:subject:references
	:in-reply-to:content-type; q=dns; s=default; b=bgrh8GtBwbcwKP2SJ
	SMOLEwESRphY9+3BlHIj9vbKnzTPRIH07xKrT2qRrZd3+aIuZ2f/do18Dytez3t4
	93hgNMwXsh2aGNkekYZjG4Xp3leiXJ+G6yXXrZTXy8ckM5Jeb2GoIOp8EZfTfHIz
	6zRHaD4DLSbY61qWNXTyR3Bxqg=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:message-id:from:to:cc:subject:references
	:in-reply-to:content-type; s=default; bh=V3GzKWo+7TTTlJmc7avHhf7
	/jJM=; b=r2EvLUkWBv5ju6EbyzCESnmiLbG68YN8LXOakKzrs1fTi/xUMFuq41s
	7Qf95eecMZVSzWXN4IAoPDuE7TXVPflyubh3XGm6OIaP2kVcVbXe4mEhebN80MMs
	N2ZdIDQP7OQ9FzjUvfA+uHXk6EwiA9wMEmgtko7C1V701xszLVHY=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-2.5 required=5.0 tests=AWL,BAYES_00,NORMAL_HTTP_TO_IP,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=H*F:D*nl
X-HELO:	lb3-smtp-cloud9.xs4all.net
Date:	Mon, 19 Feb 2018 16:45:21 +0100
Message-ID:	<d2844c5a58bdb4eb87e0ad597f3fa4a1@smtp-cloud9.xs4all.net>
From:	Houder <houder AT xs4all DOT nl>
To:	cygwin AT cygwin DOT com
Cc:	DiegoP2 AT VERIFONE DOT com
Subject:	Re: Problem with timeout command from bash
References:	<BN6PR03MB2596A3801F0B2387D0C521C79DC80 AT BN6PR03MB2596 DOT namprd03 DOT prod DOT outlook DOT com>
In-Reply-to:	<BN6PR03MB2596A3801F0B2387D0C521C79DC80@BN6PR03MB2596.namprd03.prod.outlook.com>
User-Agent:	mua.awk 0.99
X-CMAE-Envelope:	MS4wfLJZkaopGofk8shjmbMntvV3Xam42c5scO1hDE1vG93WE43zZY8KMZkBf+2P81Or6XG+G9RMDndyDgLrO3PdK6Q3rrC1CKDTQHllaGyGqQA2qzPFimdE LlfAQoBenz2jDAOx6B0Lt7Y21MQIv+as81N2Z1IdLo1hvx/N4OccEBuXKniP/nYcPP3XB3b+b8EK6j/1iVhTd+nUhTZhPYG7trkpE4i/SpP9ETbEzJOCU7h3

On Mon, 19 Feb 2018 15:32:28, Diego Pazos wrote:
> Whenever I try to run the timeout command from bash, it appears like it's b=
> eing relayed to cmd.exe's internal timeout command.
> 
> Attempting to run "timeout 123 ls" from bash throws:
> 
> ERROR: Invalid syntax. Default option is not allowed more than '1' time(s).
> Type "TIMEOUT /?" for usage.
> 
> Running the same command from the Cygwin command prompt works as expected.
> 
> Am I doing anything wrong?

Diego,

64-@@ which -a timeout # "using Cygwin"
/usr/bin/timeout
/drv/c/WINDOWS/system32/timeout
64-@@

Compare the definition of PATH after starting bash from the Explorer with the
definition of PATH after starting "using Cygwin".

Henri


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -