| To: | nv-l@lists.us.ibm.com |
|---|---|
| Subject: | Re: [nv-l] Problem with dying event windows |
| From: | Bartlomiej Grenda <Bartlomiej.Grenda@pl.ibm.com> |
| Date: | Tue, 12 Oct 2004 14:07:37 +0200 |
| Delivery-date: | Tue, 12 Oct 2004 13:29:49 +0100 |
| Envelope-to: | nv-l-archive@lists.skills-1st.co.uk |
| In-reply-to: | <OF76B782F6.52B6E754-ONC1256F2A.004D8FD6-C1256F2A.004E47E6@pl.ibm.com> |
| Reply-to: | nv-l@lists.us.ibm.com |
| Sender: | owner-nv-l@lists.us.ibm.com |
> This sounds like something X-related. I would be looking at the > logs on the machines themselves for information from Reflection-X. > Or see if there is any way to trace or debug Reflection-X. Have you > recently installed any updates to R-X or the NetView server? Do you > have the latest patches for R-X? I've checked R-X logs. Unfortunately, there is nothing interesting there. It seems that that this is on the server side... As far as I understand - all Event Viewer windows for single user are served by single nvevents process, so - if its die then all Event Viewer windows will dissappear. How can I track nvevent process (log. debug, trace)? Regards Bartlomiej Grenda |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [nv-l] NetView archive, Jane Curry |
|---|---|
| Next by Date: | Re: [nv-l] V7.1.3 FixPack3, syoung |
| Previous by Thread: | Re: [nv-l] Problem with dying event windows(TOYS), Paul |
| Next by Thread: | Re: [nv-l] Problem with dying event windows, James Shanks |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
Archive operated by Skills 1st Ltd
See also: The NetView Web