Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <40F511B2.3050701@x-ray.at> Date: Wed, 14 Jul 2004 12:57:54 +0200 From: Reini Urban User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.7) Gecko/20040616 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: cat /proc/registry/HKEY_PERFOMANCE_DATA/@ hangs References: <40F3ED68 DOT 6030304 AT x-ray DOT at> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Igor Pechtchanski schrieb: > On Tue, 13 Jul 2004, Reini Urban wrote: > > >>cat /proc/registry/HKEY_PERFOMANCE_DATA/@ >>hangs forever. > > > According to MSDN > (): > > ...although you use the registry to collect performance data, the > data is not stored in the registry database. Instead, calling the > registry functions with the HKEY_PERFORMANCE_DATA key causes the > system to collect the data from the appropriate system object > managers. > > To obtain performance data from the local system, use the > RegQueryValueEx function, with the HKEY_PERFORMANCE_DATA key. > The first call opens the key; you do not need to explicitly open > the key first. However, be sure to use the RegCloseKey function > to close the handle to the key when you are finished obtaining > performance data. > > This tells me that reading from HKEY_PERFORMANCE_DATA never returns EOF, > so that you have to terminate it explicitly from the outside. So your > behavior sounds absolutely normal. > > >>Win2K (no win98 OS) >>Shouldn't HKEY_PERFOMANCE_DATA be disabled on NT systems, or does it work? > > > If the key is present, it'll be in /proc/registry. FWIW, the MSDN web > page above doesn't mention any restrictions on the systems that this key > is present on. > > >>This cat has pid 560: >>$ cat /proc/560/status >>[snip] >> >>kill 560 >>doesn't help, /bin/kill.exe neither. >>pskill works ok. > > > "/bin/kill -f 560". $ cat /proc/registry/HKEY_PERFOMANCE_DATA/@ /bin/kill -f doesn't work. (W2K SP4, all updates) $ ps PID PPID PGID WINPID TTY UID STIME COMMAND 1432 1 1432 1432 0 1000 11:47:24 /usr/bin/bash 636 1432 636 1724 0 1000 11:47:37 /usr/bin/cat 1732 1 1732 1732 1 1000 11:49:10 /usr/bin/bash 1772 1732 1772 1784 1 1000 11:49:14 /usr/bin/ps $ /bin/kill -f 636 couldn't open pid 636 If the registry handler should follow the stream semantics it should react on signals at least. But neither Ctrl-D nor Ctrl-C work. next attempt: (still no killall script? then it would be simply killall cat) $ /bin/kill -9 -f 1748 couldn't open pid 1748 but here cat and the parent bash windows are killed. -- Reini Urban http://xarch.tu-graz.ac.at/home/rurban/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/