Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
NNM Read Only Map Access
- Thread starter cookieman
- Start date
Hi there cookie man, sure, you can open it by typing "ovw -ro" and this brings up a read only copy of your default map.
You may create an alias for the operators like this or use it on their .profile
Even better you can change the registration files and restrict also the tools that the operators are going to access, by making a copy of your OVwregDir to a different path and exporting this in their .profile
Hope this helps, regards,
vlan52
![[sunshine]](/data/assets/smilies/sunshine.gif "[sunshine] [sunshine]")
vlan52
The end of wisdom is freedom. The end of culture is perfection. The end of
education is character. The end of knowledge is love.
You may create an alias for the operators like this or use it on their .profile
Even better you can change the registration files and restrict also the tools that the operators are going to access, by making a copy of your OVwregDir to a different path and exporting this in their .profile
Hope this helps, regards,
vlan52
vlan52The end of wisdom is freedom. The end of culture is perfection. The end of
education is character. The end of knowledge is love.
- Thread starter
- #3
Thanks. I have tried adding ovw -ro -map default to the .profile and it has solved the "never get RW issue", however, this has opened up what appears to be graphics and/or environment variable problems. Map colors have changed and once a map is brought up you can't close out of it ! It looks there is more to this than meets the eye. If you have some insight as to why this is happening I would appreciate any advice you can give.
Thanks again,
Cookieman
Thanks again,
Cookieman
Great, seems like we've solved the first issue then, reagrding the colors, there is an option (you may look into ovw's man for it), which is a switch/flag you may add when you open ovw -ro, it is -ncols #.
-ncols # takes care of color allocation, by default will try to use 128 colors, but go ahead and play a little with it and see how it goes.
You can´t close the map once it opens?This is weird, is it a new map that you are creating/opening or is it a copy of the default map?
It should not be happening at all cookieman...
Regards,
vlan52
vlan52
The end of wisdom is freedom. The end of culture is perfection. The end of
education is character. The end of knowledge is love.
-ncols # takes care of color allocation, by default will try to use 128 colors, but go ahead and play a little with it and see how it goes.
You can´t close the map once it opens?This is weird, is it a new map that you are creating/opening or is it a copy of the default map?
It should not be happening at all cookieman...
Regards,
vlan52
vlan52
The end of wisdom is freedom. The end of culture is perfection. The end of
education is character. The end of knowledge is love.
- Thread starter
- #5
Sorry vlan52, I should have made myself a bit clearer. Not only are the colors messed up but there are no borders, I can't expand or contract a window nor move it around the desktop. I CAN delete maps. As soon as I click on an icon to bring up another map the background goes black. ??? I've tried different combinations of the -ncols # variable but still no luck. Note, this only happens when I start ovw from the .profile file. If I execute ovw from a terminal window all is fine. Any thoughts??
No problem, could you send me the .profile file just to check waht could be missing there?
Regards,
vlan52
vlan52
The end of wisdom is freedom. The end of culture is perfection. The end of
education is character. The end of knowledge is love.
Regards,
vlan52
vlan52The end of wisdom is freedom. The end of culture is perfection. The end of
education is character. The end of knowledge is love.
- Thread starter
- #7
Hi cookieman,
I think that your colors or enviroment problems doesn't depending on "-ro" option.
However, if you'll never open your maps by user root, you can change your map's permission with "ovwchmod" and "ovwchown" command.
So, if you set
ovwchmod 444 <map name>
ovwchown root:<group> <map name>
your maps will can be open by all user in read only mode and in read/write mode only by user root.
Regards
I think that your colors or enviroment problems doesn't depending on "-ro" option.
However, if you'll never open your maps by user root, you can change your map's permission with "ovwchmod" and "ovwchown" command.
So, if you set
ovwchmod 444 <map name>
ovwchown root:<group> <map name>
your maps will can be open by all user in read only mode and in read/write mode only by user root.
Regards
I have little knowledge of HP OPEN VIEW, I will appreciate very much you can help me with my problem.
The fact is that I need to establish security levels of remote access to the network without considering the telnet option. In order to do it a dedicated 2 Mbit/s link has been established between the Sun server and the remote point, which must have only read- only access . Nowadays there are two users created in Solaris: the administrator with total access and the other that has telnet restriction.
I did tests with this "monitor" user waiting that the Sun server validates it and access the map as read- only but this doesn´t occur and I need to know what is the problem and what I need at both stations, such as a license or software configurations in order to the new read- only user function properly. We need in three days to have ready this configuration functioning properly.
The following are the technical data of our managemente system:
Solaris version: 5.7
Solaris HP OV: 6.1
SUN Server: Ultra 5
Please consider in your solution that the remote "monitor" doesn't have access to telnet.
We apreciate your inmediate answer to this problem.
Yours sincerely
perazo
The fact is that I need to establish security levels of remote access to the network without considering the telnet option. In order to do it a dedicated 2 Mbit/s link has been established between the Sun server and the remote point, which must have only read- only access . Nowadays there are two users created in Solaris: the administrator with total access and the other that has telnet restriction.
I did tests with this "monitor" user waiting that the Sun server validates it and access the map as read- only but this doesn´t occur and I need to know what is the problem and what I need at both stations, such as a license or software configurations in order to the new read- only user function properly. We need in three days to have ready this configuration functioning properly.
The following are the technical data of our managemente system:
Solaris version: 5.7
Solaris HP OV: 6.1
SUN Server: Ultra 5
Please consider in your solution that the remote "monitor" doesn't have access to telnet.
We apreciate your inmediate answer to this problem.
Yours sincerely
perazo
- Status
Similar threads
- Locked
- Question