This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: ps questions
- From: Warren Young <wyml at etr-usa dot com>
- To: cygwin at cygwin dot com
- Date: Thu, 18 Dec 2014 11:40:50 -0700
- Subject: Re: ps questions
- Authentication-results: sourceware.org; auth=none
- References: <CAO2ddnZChb-n9+Z1YEWCFSA=WTaYfkmHdjMZk7Te5JYckUDE+Q at mail dot gmail dot com> <5492EDFC dot 5080608 at gmail dot com> <CAO2ddnZHs=4GxUJtjgoyTXO2Or3oKzY6Rck=m9Mqfj6DgWUQUg at mail dot gmail dot com> <20141218171116 dot GF10824 at calimero dot vinschen dot de> <8F8B22BA-B007-4F10-9B4F-9BD963D17059 at etr-usa dot com> <20141218173346 dot GH10824 at calimero dot vinschen dot de>
On Dec 18, 2014, at 10:33 AM, Corinna Vinschen <corinna-cygwin@cygwin.com> wrote:
> On Dec 18 10:26, Warren Young wrote:
>>
>> ...Cygwin doesn’t do something similar?
>
> Cygwin isn't a kernel and the process
> information is kept in shared memory regions held by the parent process
> and the process itself. This model has limitations you don't have on a
> real kernel.
I’m aware of that, but can’t the DLL see both the birth and death of every Cygwin process? Birth via either DllMain() or execvp(2), and death via one of the methods here:
http://stackoverflow.com/questions/4242469/
--
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