From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27297 invoked by alias); 24 Mar 2019 18:15:37 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 27190 invoked by uid 89); 24 Mar 2019 18:15:29 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00,KAM_NUMSUBJECT,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.1 spammy=translated, explain, HX-Spam-Relays-External:ESMTPA X-HELO: vsmx012.vodafonemail.xion.oxcs.net Received: from vsmx012.vodafonemail.xion.oxcs.net (HELO vsmx012.vodafonemail.xion.oxcs.net) (153.92.174.90) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sun, 24 Mar 2019 18:15:26 +0000 Received: from vsmx004.vodafonemail.xion.oxcs.net (unknown [192.168.75.198]) by mta-8-out.mta.xion.oxcs.net (Postfix) with ESMTP id 86E4BF34C1A for ; Sun, 24 Mar 2019 18:15:24 +0000 (UTC) Received: from Gertrud (unknown [87.185.218.207]) by mta-8-out.mta.xion.oxcs.net (Postfix) with ESMTPA id 5762919AD8B for ; Sun, 24 Mar 2019 18:15:22 +0000 (UTC) From: Achim Gratz 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> Date: Sun, 24 Mar 2019 18:15:00 -0000 In-Reply-To: (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 X-SW-Source: 2019-03/txt/msg00559.txt.bz2 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