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:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=nSKI5BgnEYdnef3JcRK0lHIxTbjfjWDGkcIPiOOgciQMhU5PxY7G7
	d37GcXQnAJkZ6YwqjKwcSxpCgOrBCbjDThl42jD8jWRD9AsVv7s5reT6o0lMxS6T
	lZrJEalqMuVYsGDbWVpF7p5A+nrLPVf/x5wVfbzvHEo6MRw7NSuSUA=
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:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	 bh=S7uxJYm24Jxkt0oA5CWMUSQ5sO8=; b=CVPdXeP11qo8wNrlE3X/L8FqgDQm
	yX3fxsr7zxFgAvxRaxkIh2hBth8EXumF3//I9WF1rPGlZDJEUxYVcQVbwwJsdUGP
	kLpbHvLfPbKzjHoa5UzuY2+YQGWO5sE2MO/Hvc04yVOlW3/IIB6sfwnsK5bibWsq
	NyV1KbMiYWVWjHs=
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=0.2 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2
X-HELO: mho-01-ewr.mailhop.org
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Report-Abuse-To: abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX1/i4WOb2It5dTK4rHoM0FZ5
Date: Fri, 18 Oct 2013 16:14:17 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: [ANNOUNCEMENT] Updated: procps-3.2.8-1
Message-ID: <20131018201417.GA784@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <announce DOT 20131016161501 DOT GE18358 AT calimero DOT vinschen DOT de> <loom DOT 20131016T211907-532 AT post DOT gmane DOT org> <20131017091355 DOT GM18358 AT calimero DOT vinschen DOT de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20131017091355.GM18358@calimero.vinschen.de>
User-Agent: Mutt/1.5.20 (2009-06-14)

On Thu, Oct 17, 2013 at 11:13:55AM +0200, Corinna Vinschen wrote:
>On Oct 16 19:33, Kurt Franke wrote:
>> Corinna Vinschen <corinna-cygwin <at> cygwin.com> writes:
>> 
>> > Hi folks,
>> > 
>> > I took over maintainership for the procps package, which hadn't been
>> > updated since 2007.  I now update the package to the last procps package
>> > 3.2.8 from 2009, added a few tweaks, and especially built it for 32 and
>> > (tada!) 64 bit.
>> > 
>> > Please note that with the current Cygwin 1.7.25, procps -f/-l will print
>> > two question marks in place of the controlling tty for processes which
>> > don't have a controlling tty.  Usually it should only print a single
>> > question mark in this case, but the reason here is a minor bug in the
>> > Cygwin DLL which will be fixed in the next release.  I hope that's not
>> > too disturbing for the time being.
>> > 
>> > Have fun,
>> > Corinna
>> 
>> Hi Corinna,
>> 
>> could you have a look on the formatting when displaying a sid column, i. e.
>> 
>> $> procps -eo user,pid,ppid,pgrp,tty,stime,cputime,sid,cmd
>> 
>> if now setsid is done, the -1 is used, which is correct displayed in
>>  /proc/*/sid
>> but displayed as unsigned value in procps which reads as 4294967295 and 
>> thus will break the formatting of output.
>> 
>> Or would there be a chance to implement sid handling during
>> process creation, initialize the sid to pid if there is no one
>> inherited by parent which should only occure if a cygwin program
>> is called by a windows program, and always inherit it if the parent
>> is a cygwin process ?
>
>Yeah.  I'm wondering why our process sid is -1 at all.  This never
>occurs on Linux, afaics.
>
>I'll investigate.  Thanks for the heads up.

This should be fixed in the upcoming snapshot.  It's one of those "how
did this ever work?" bugs.

Thanks for the heads up.

cgf

--
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