From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: ps -W now showing STIME Dec 31
Date: Fri, 22 Mar 2019 18:53:00 -0000 [thread overview]
Message-ID: <50fa5b02-3470-d8fb-92a0-98e88ec70d62@SystematicSw.ab.ca> (raw)
In-Reply-To: <20190321190826.GV3908@calimero.vinschen.de>
On 2019-03-21 13:08, Corinna Vinschen wrote:
> 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 provide a patch.
Tried in PS and system startup process and task StartTime is not available:
Get-Process | where {$_.StartTime} | Format-Table Id, StartTime, Name
with or without the StartTime filter, in a unelevated process not in a domain;
an elevated process shows it for all but the System Idle Process.
It is available from WMI as shown by SysInternals ProcExp64 and directly by:
$ wmic process get processid, creationdate, name # rearranged with awk
Proce CreationDate Name
104 20190315065342.676287-360 Registry
4 20190315065436.434418-360 System
0 20190315065436.434418-360 System
408 20190315065436.891830-360 smss.exe
560 20190315065500.672209-360 csrss.exe
660 20190315065502.159992-360 wininit.exe
780 20190315065502.406370-360 services.exe
824 20190315065502.618164-360 lsass.exe
928 20190315065504.236736-360 svchost.exe
952 20190315065504.262313-360 svchost.exe
976 20190315065504.364113-360 fontdrvhost.exe
In Cygwin ps, think zero could be subbed by what goes out as /proc/stat btime.
I will try to pull it together and remember how git format-patch and send-email
work. ;^>
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
--
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
prev parent reply other threads:[~2019-03-22 18:53 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
2019-03-22 18:53 ` Brian Inglis [this message]
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=50fa5b02-3470-d8fb-92a0-98e88ec70d62@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).