| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
We have the spanning tree map fm (stm_fm) which allows users to create a spanning tree map of their network and autoregister the bridges, etc that have been found in a domain. Now, the stm_fm creates several files. One being the map file which can be brought up and displayed through mcc_iconic_map. The other files being created are a script file and a log from running that script file. The script file contains commands to register the bridges found on the network. Currently it is set up to just create these files in the current directory. Which works fine on VMS but not under ULTRIX (due to DECmcc's execution model on ULTRIX). Instead, the files are created in whatever directory the user was in when our fm was enrolled. So, for instance, say that user x enrolled the stm_fm while in /usr/users/x/test/subtest. Then user y performs an automap command - the resulting files end up in /usr/users/x/test/subtest. But we want the files to end up in user y's current directory (or home directory). Does anyone have ideas on the best way to handle this? Does anyone else have an FM which creates files? Thanks for any input. Karen
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2155.1 | TOOK::SWIST | Jim Swist LKG2-2/T2 DTN 226-7102 | Tue Jan 21 1992 16:50 | 14 | |
As you have noted the concept of "current" directory is vague given
various execution models for MMs. It will get even more vague as we
go distributed.
A reasonable interim strategy is to either require a full pathname,
or if given a relative pathname, prepend the home directory rather
than setting it default. getpwuid(getuid()) will return the
current user's password record within which you can find the home
directory in field "pw_dir".
VMS tactics are trickier due to the plethora of logical name and rooted
directory options. The simplest thing to do is require that only a
simple filename be given (not a logical), and then stick on sys$login
to force it into the home directory.
| |||||