From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4405 invoked by alias); 22 Mar 2019 18:53:00 -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 4393 invoked by uid 89); 22 Mar 2019 18:52:59 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00,KAM_NUMSUBJECT,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 spammy=sk:2019031, elevated, advised, unique X-HELO: smtp-out-so.shaw.ca Received: from smtp-out-so.shaw.ca (HELO smtp-out-so.shaw.ca) (64.59.136.137) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 22 Mar 2019 18:52:57 +0000 Received: from [192.168.1.114] ([24.64.172.44]) by shaw.ca with ESMTP id 7PHhhslavo7SQ7PHihNnFi; Fri, 22 Mar 2019 12:52:54 -0600 Reply-To: Brian.Inglis@SystematicSw.ab.ca Subject: Re: ps -W now showing STIME Dec 31 To: cygwin@cygwin.com References: <20190321145237.GF2167@calimero.vinschen.de> <20190321190826.GV3908@calimero.vinschen.de> From: Brian Inglis Openpgp: preference=signencrypt Message-ID: <50fa5b02-3470-d8fb-92a0-98e88ec70d62@SystematicSw.ab.ca> Date: Fri, 22 Mar 2019 18:53:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.0 MIME-Version: 1.0 In-Reply-To: <20190321190826.GV3908@calimero.vinschen.de> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2019-03/txt/msg00543.txt.bz2 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