public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Garber, Dave (BHGE, Non-GE)" <dave.garber1@bhge.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: EXT: Re: ps -W now showing STIME Dec 31
Date: Thu, 21 Mar 2019 15:58:00 -0000	[thread overview]
Message-ID: <DM5P101MB01534A575C4C41F379FBBC04B5420@DM5P101MB0153.NAMP101.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20190321145237.GF2167@calimero.vinschen.de>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1019 bytes --]


> -----Original Message-----
> From: cygwin-owner@cygwin.com <cygwin-owner@cygwin.com> On Behalf
> Of Corinna Vinschen
> Sent: Thursday, March 21, 2019 10:53 AM
> To: cygwin@cygwin.com
> Subject: EXT: Re: ps -W now showing STIME Dec 31
> 
> 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.


Run from an elevated shell it shows correctly.

But Windows command 'wmic process get name, creationdate' in a non-elevated command prompt also works.  So it looks like it should be possible.

> 
> 
> Corinna
> 
> --
> Corinna Vinschen
> Cygwin Maintainer
\x03B‹KCB”\x1c›Ø›\x19[H\x1c™\^[ܝ\x1cΈ\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÜ\x1c›Ø›\x19[\Ëš\x1d^[[\x03B‘TNˆ\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÙ˜\KÃB‘^[ØÝ[Y[\x18]\x1a[ÛŽˆ\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÙ^[ØÜËš\x1d^[[\x03B•[œÝXœØÜšX™H\x1a[™›Îˆ\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÛ[\vÈÝ[œÝXœØÜšX™K\Ú[\^[\x19CBƒB

  reply	other threads:[~2019-03-21 15:58 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   ` Garber, Dave (BHGE, Non-GE) [this message]
2019-03-21 16:07     ` EXT: " 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

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=DM5P101MB01534A575C4C41F379FBBC04B5420@DM5P101MB0153.NAMP101.PROD.OUTLOOK.COM \
    --to=dave.garber1@bhge.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).