| Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE |
| Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 |
| Moderator: | NETCAD::COLELLA DT |
| Created: | Wed Nov 13 1991 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4455 |
| Total number of notes: | 16761 |
Hello All, I have a customer running Probe watch V322 on a Digital Unix work station. He says it is no longer capturing data. He claims this used to work then it quit. He wants to know what daemon is responsable for capturing data and how is it started? I just atarted looking at Rmon under win 95 and I dont have any information on Probe watch under Unix. So any help would be appreciated. Under RMON it looks like you actually have to do an UPload. Is this the same under Probe watch? Is there a particular script that needs to be run to start the data collection? Or is it part of the probewatch startup? Is there a process that is necessary for the data collection? If there is what is its name? Thanks for any assistance Alan S. Anderson Digital Equipment Corp.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3801.1 | is it nslogd? | CX3PST::NOTAMI::A_ANDERSON | CX03 2/H13 NSU/VAX MacGhille Aindrais | Wed Aug 21 1996 16:49 | 10 |
I found a pointer to the Use Manual and printed it out. In section 4.3.8 is mentions a C:\PROBEW\BIN\NSLOGD. This path sounds like DOS and not Unix but I'll have the customer try and locate a NSLOGD file on his system and we will try to run it and see what happens. Right now the customer is not returning my phone calls. If I am on the wrong track feel free to correct me. Alan | |||||
| 3801.2 | looks like its an undocumented daemon dvlogd | CX3PST::NOTAMI::A_ANDERSON | CX03 2/H13 NSU/VAX MacGhille Aindrais | Fri Aug 23 1996 13:50 | 19 |
I finally got back in touch with the customer. He does not have a nslogd file. So he reinstalled probewatch, still no nslogd, and logging still does not work. Finally he deinstalled the product blew away all the remnants and reinstaleld the product. Still no nslogd, but logging is now functioning. He has located a dvlogd that appears to do the logging. I have a question. We are supposed to support this product. We do not have access to the product and the manual is WRONG so how the heck do you expect us to help our customer? All this is going to do is help them buy another companys product. This customer is not a happy camper. Alan | |||||