| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2447.1 | HUBwatch V4 for Digital UNIX ?? | ZTOIS1::VISTA | Renato VISTA/SI France/ZTO | Thu Jun 29 1995 08:44 | 9 |
|
Hi Robert,
Are you using HUBwatch V4.0 for Digital UNIX ? If so, may I have the
network pointer of the kit ?
Thank you.
Renato
|
| 2447.2 | Add to your .cshrc file | NETCAD::SKABO | Expect Nothing U never disappointed | Thu Jun 29 1995 10:13 | 11 |
|
Hello Robert,
You should have this defined in your .cshrc file and PROBEwatch
will lauch correctly (Change directories for your set-up):
setenv XLIBI18N_PATH /usr/kits/PROBEwatch/X
setenv NSHOME /usr/kits/PROBEwatch
setenv XUSERFILESEARCHPATH /usr/kits/PROBEwatch/X/%N
Tom
|
| 2447.3 | Hi | BACHUS::VANDENBERGHE | | Thu Jun 29 1995 10:14 | 7 |
| Renato,
It should be on bhub (16.21.16.156) /usr/users/ftp/hubwatch_osf/
same for the DOS version (other directory).
Phone me if you need a quick copy (856.8837).
Bien a toi,
Robert
|
| 2447.4 | Some answers and pointers | NETCAD::FORINO | | Thu Jun 29 1995 10:28 | 24 |
| See note 2346 for the kit pointer. If you use the command
dir/key=kits
you will get all the notes marked with the "KITS" keyword.
To answer the original problem PROBEWATCH uses an environmental
variable to point where the executable was installed. Unfortunately,
it was not implemented before HUBwatch went out the door so HUBwatch
always tries to execute out of the default installation directory
for PROBEwatch. (We'll fix this in V4.1). What you can do is
create a softlink on your system from where the really nsman is to
the place where HUBwatch thinks it should be. I think that should
do it. For example, if your nsman is in /xxx/nsman go into the
/xxx directory and
ln -s nsman /usr/kits/PROBEwatch/bin/nsman
This assume you have created the /usr/kits/PROBEwatch/bin directory
beforehand.
John
|
| 2447.5 | | BACHUS::VANDENBERGHE | | Thu Jun 29 1995 12:02 | 3 |
| Thanks John,
That's the way I did it, but I thought that they was a better way.
Robert
|