This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: ps weirdness...
- From: <cygwin at kosowsky dot org>
- To: cygwin at cygwin dot com
- Date: Thu, 24 Oct 2013 10:21:49 -0400
- Subject: Re: ps weirdness...
- Authentication-results: sourceware.org; auth=none
- References: <21093 dot 42532 dot 550364 dot 992074 at consult dot pretender> <20131023082535 dot GA5134 at calimero dot vinschen dot de> <21095 dot 51020 dot 811223 dot 778148 at consult dot pretender> <CAFO6C=xn=h9jtkDcfTHxCevTOYD-xz-oR1ynXZwZfOCj_WsTBQ at mail dot gmail dot com> <52690B60 dot 1050404 at cygwin dot com>
Larry Hall (Cygwin) wrote at about 07:58:24 -0400 on Thursday, October 24, 2013:
> On 10/24/2013 6:03 AM, Anthony Geoghegan wrote:
> > I was intrigued by Jeff's post so I tried a couple of experiments of
> > my own and was able to duplicate the same behaviour - including the
> > bash process being shown as a Windows process - on my Cygwin
> > installation. The only difference was that I was getting Jan 1 instead
> > of Dec 31 for the STIME.
> >
> > FWIW, I'm running 32-bit version of Cygwin on 64-bit Windows 7 and can
> > supply the output of cygcheck if it's useful. Also, I started my
> > Cygwin shell yesterday so "Oct 23" is the correct STIME for the bash
> > and ssh-agent processes.
>
> As for the date issue, what you're seeing is the traditional UNIX/POSIX
> start time (the number of seconds since Jan 1, 1970). It's nothing strange.
>
I still don't understand the following:
1. Why there are occasional duplicate ssh-agent processes?
(the forking by grep of a bash process only explains the duplicate
bash process behavior)
2. Why is the start time Jan 1, 1970 (or in my case Dec 31 1969?) when
the process was only started today?
--
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