DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:references:date:in-reply-to
	:message-id:mime-version:content-type; q=dns; s=default; b=yotRz
	aZaoNWbZgvn4GQwt/Ki0EIFjzAYa3iNar4BnbJnCMVT1AKLdbr2IvkmnW0klR9SW
	3f8XeW5ujgV1IROv1eyghdH2ofAMOemnpuYaIKqkK5selL0wg2nMVl1tm3LCLA3U
	pYyJ6lG7k/+EG5jHoGRE2PzDZDllFnNXXyvv6U=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: [PATCH] default ps -W process start time to system boot time when inaccessible, 0, -1
References: <20190323034522.9688-1-Brian.Inglis@SystematicSW.ab.ca>	<87d0mh5x3u.fsf@Rainer.invalid>	<20190323183653.GB3471@calimero.vinschen.de>	<874l7tbfh6.fsf@Rainer.invalid>	<4dfdfce1-245d-98fe-0c49-890ba8ec8dd4@SystematicSw.ab.ca>	<874l7s65yv.fsf@Rainer.invalid>	<bacddf44-e71b-08a2-9e93-0da8d98cc540@SystematicSw.ab.ca>
Date: Sun, 24 Mar 2019 19:15:17 +0100
In-Reply-To: <bacddf44-e71b-08a2-9e93-0da8d98cc540@SystematicSw.ab.ca> (Brian	Inglis's message of "Sun, 24 Mar 2019 10:17:55 -0600")
Message-ID: <871s2wm956.fsf@Rainer.invalid>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain

Brian Inglis writes:
> Boot time is neither magic nor pulled out of thin air.

No, but other than a lower limit of the process start time it has no
correlation whatsoever to the start time of a process that I am not
proviledged to get the start time from.

> Checking *my* system processes using wmic queries and elevated powershell
> scripts, the boot time is at most a few seconds off from process start times
> from other sources.
> I understand that other systems may run processes where that is not the case.
> Please explain why you think this is misleadingly not useful, or where or which
> processes have unvailable start times that are not very close to boot time.

System processes get started and re-started all the time, as do
processes from other users (interactive or otherwise).

So again: in the case under discussion we _know_ that "0" is a bogus
timestamp value that no process ever got started on, even if it can be
translated to "Jan 1st 1970" if it were indeed a valid timestamp.  All
I'm asking is that ps shows something like "N/A" instead of trying to
print something that looks like it might be a valid time, but still
isn't.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Waldorf MIDI Implementation & additional documentation:
http://Synth.Stromeko.net/Downloads.html#WaldorfDocs

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