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 |
HUBWATCH V4.1 SUPPORTED FOR DIGITAL UNIX V4.0? I've recently upgraded my d-Unix platform to V4.0. I see a segmentation failure? (I'm at home and don't have exact syntax) followed by a core dump. I'm typing # HUBWATCH -X 166.34.121.244 to get to my hub with the same IP address. Is HUBWATCH supported in d-Unix V4.0??? thanks, /Mic
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
3768.1 | is CDE supported??? | SCASS1::GALVIN | The Energizer Bunny's Trainer... | Mon Aug 12 1996 17:52 | 21 |
Ok, I guess everyone else has switched to ClearVISN... 8^) There error I was getting was - X Toolkit Warning: No type converter registered for 'String' to 'Pointer' conversion. [1] Segmentation fault hubwatch -x 166.34.121.244 ( core dumped ) What I found out was, (in case we're still selling d-Unix hubwatch) You have to exit out of the CDE on d-Unix V4.0 and run the Dxsession Session... This is NOT a pain, and in my client's case... *acceptable*... I guess the bigger question is when will CDE be supported... /Mic | |||||
3768.2 | clearVISN & CDE support | SLINK::HOOD | Your bad news bear | Fri Aug 16 1996 14:26 | 9 |
Mic, I forwarded your note to Jack NAC::Forrest, the clearVISN product manager. You might want to get in touch with him directly if you'd like to add that requirement to the Digital UNIX ports of clearVISN. Tom Hood clearVISN (VLAN Manager) eng |