Re: [foxboro] /usr/fox/wp/data/wp51_cmds
- From: Terry Doucet <doucet427@xxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Wed, 31 Mar 2010 11:02:39 -0400
Stan,
The wp51_cmds will run for all display managers on this station whether remote
or local.
As Alex and others have stated, you can select a View_Only type of display
manager for floating or assigned display managers in the dmcfg file and when
started, the display manager will have the omsets disabled. Any environment
change or command line (pref) can enable omsets on this display manager. Some
users have a inactivity timeout so that with no keyboard or mouse activity for
x minutes, the environment is changed back to Initial where omsets are
disabled. If you select an Inital Display with zero connections, then all om
connections should be released for this display manager.
The key thing is that you need to prevent someone without a valid password
environment like the engineers environment from accidentally changing this
(View_Only) display manager back to omsets capability. The right-mouse click in
FoxView has some selections that need to be deleted from environments where
omsets are disabled. There may be others such as the command or cmd prompt in
Windows. You need to pick everything in the protected environment to ensure
that there is no link to enabling omsets.
The VT-100 selection has different properties depending on where it is called
from. For example, directly on the AW51 when you select VT100 local, you get
certain Unix variables but when you are connected via Exceed on a PC and you
select VT100 local, you do not get the same Unix variables as directly on the
AW51. So when directly on an AW51 in VT100 you may run progams that work as you
intended but if you try to run the same program while sitting in front of a PC
and Exceed connection to the AW51 VT100, the program may not work.
Terry
> Date: Wed, 31 Mar 2010 09:06:38 -0500
> From: stanb@xxxxxxxxx
> To: foxboro@xxxxxxxxxxxxx
> Subject: [foxboro] /usr/fox/wp/data/wp51_cmds
>
> I am trying to redesign how wee do remote access to our UNIX based DM and
> oxview machines to acomodate some changes on the IT side.
>
> One of the things I need to acomplihs is make certain sessions started this
> way have omsets disabled. I was pointed to the posibilty of doing this in
> /usr/fox/wp/data/wp51_cmds.
>
> Looking at this file, it does look like this is a posible place to
> acomplish this. However, i have never dealt with this file before, so I
> have a couple of questions.
>
> It appears that this is a dmcmd script that is automaticaly executed whne a
> DM sessions is started. s this correct?
>
> If so, is there a way I can evalute, from the command line, what a given
> variable is that this script examines. For instance there is a line that I
> beleive says "if the DM is not local disable omsts". it looks like this:
>
> == $DM_LOCAL N dmcmd disable clralm
>
> is his assumption correct?
>
> If so, can I test DM_LOCAL from a shell prompt (IE in a vt100 window)? I
> would have thought I could do this with omget, but if I can then I must not
> know how to sue omget, which is posible.
>
> In addition, how can I determine what variables are available to test
> against in this script?
>
> Thanks.
>
> --
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?
>
>
> _______________________________________________________________________
> This mailing list is neither sponsored nor endorsed by Invensys Process
> Systems (formerly The Foxboro Company). Use the info you obtain here at
> your own risks. Read http://www.thecassandraproject.org/disclaimer.html
>
> foxboro mailing list: //www.freelists.org/list/foxboro
> to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
> to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
>
_________________________________________________________________
Stay in touch.
http://go.microsoft.com/?linkid?12959
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
Other related posts:
