From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: ps -W now showing STIME Dec 31
Date: Thu, 21 Mar 2019 19:08:00 -0000 [thread overview]
Message-ID: <20190321190826.GV3908@calimero.vinschen.de> (raw)
In-Reply-To: <f0a29c26-2c1a-7104-d832-a6ae0bda5e2b@SystematicSw.ab.ca>
[-- Attachment #1: Type: text/plain, Size: 1308 bytes --]
On Mar 21 10:02, Brian Inglis wrote:
> On 2019-03-21 08:52, Corinna Vinschen wrote:
> > On Mar 21 08:07, Brian Inglis wrote:
> >> With latest Cygwin ps -W is now showing STIME Dec 31 for Windows startup
> >> processes - these should be limited to actual start or uptime if possible.
> > It's not possible. Starttime requires ability to open process.
>
> Everything on Cygwin updated Mar 18.
> Running ps under bash from mintty launched from XDG.
> Ran cygcheck on ps below, and attached strace not showing much useful.
> Running under gdb, ps appears never to call GetProcessTimes on startup processes
> including my own startup scheduled tasks, so start_time is always zero, and is
> offset -7 to MST.
> Showing below also unique startup programs, unique other programs with normal
> times from System32, running Cygwin processes, and installed releases FYI.
> I could rebuild ps with debugging and add logging if not reproducible.
Sorry, but I really can't follow. It's really simple: If the user
can open a process, starttime is available, if the user can not open
the process, starttime is not available. Just check the ps source.
If you see another solution (no WMI, Bill is right there), feel free
to providea patch.
Corinna
--
Corinna Vinschen
Cygwin Maintainer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-03-21 19:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 14:07 Brian Inglis
2019-03-21 14:52 ` Corinna Vinschen
2019-03-21 15:58 ` EXT: " Garber, Dave (BHGE, Non-GE)
2019-03-21 16:07 ` Bill Stewart
2019-03-21 17:45 ` Brian Inglis
2019-03-21 20:35 ` Andrey Repin
2019-03-21 16:03 ` Brian Inglis
2019-03-21 19:08 ` Corinna Vinschen [this message]
2019-03-22 18:53 ` Brian Inglis
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=20190321190826.GV3908@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--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).