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
Date: Sun, 24 Mar 2019 18:15:00 -0000 [thread overview]
Message-ID: <871s2wm956.fsf@Rainer.invalid> (raw)
In-Reply-To: <bacddf44-e71b-08a2-9e93-0da8d98cc540@SystematicSw.ab.ca> (Brian Inglis's message of "Sun, 24 Mar 2019 10:17:55 -0600")
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
next prev parent reply other threads:[~2019-03-24 18:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190323034522.9688-1-Brian.Inglis@SystematicSW.ab.ca>
[not found] ` <87d0mh5x3u.fsf@Rainer.invalid>
[not found] ` <20190323183653.GB3471@calimero.vinschen.de>
[not found] ` <874l7tbfh6.fsf@Rainer.invalid>
[not found] ` <4dfdfce1-245d-98fe-0c49-890ba8ec8dd4@SystematicSw.ab.ca>
[not found] ` <874l7s65yv.fsf@Rainer.invalid>
2019-03-24 16:18 ` Brian Inglis
2019-03-24 18:15 ` Achim Gratz [this message]
2019-03-24 19:16 ` Brian Inglis
2019-03-24 19:48 ` Achim Gratz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871s2wm956.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).