Maybe not, I am not certain. Let me elaborate. I am planning on having IT's terminal server box use ssh to execute a script on the AW. This works just like "rsh script". This script will take an argument that represents the "session number" from the terminal server. I need to do this, as there will be more than one connection from this one IP address, so I can't just set the DISPLAY environment variable to {IP_ADDRESS):1 for instance. I will have to set it to {IP_ADDRESS):$SESSION_NIMBER. Clear so far? Now, since I am doing all this work, I plan on using vnc, so that I don't have to deal with all the setup issues of having a X server on the terminal server. Particularly since not all of our nodes have the same color pallet and symbols. My concern is that We have run VNC with a simple startup script in the past, as root and this scenario has resulted in this instance having omsets enabled. I am not familiar with the dmcfg file, but it was configured by Foxboro to allow remote access suing the i1/remote standard, so I would have thought that this would already have been done. Where is this file? > -----Original Message----- > From: Stan Brown [mailto:stanb@xxxxxxxxx] On Behalf Of Jeremy Milum > Sent: Wednesday, March 31, 2010 10:26 AM > To: foxboro@xxxxxxxxxxxxx > Subject: Re: [foxboro] /usr/fox/wp/data/wp51_cmds > > As Alex suggested earlier, why can't you just set the remote DMs to > the "view only" type in the dmcfg file (which disable omsets) and then > use the environment files and their associated passwords to renable > omsets for any users that need to have them? That's the way we do it. > I have one unix box setup to serve remote foxviews, the dmcfg is > configured to make them "view only", the environment that starts up > maintains that and then if anyone needs more access they have a > password to get into a more secure environment that re-enables omsets > and such. > > Is there a reason this method would not work for you? > > -- > Jeremy > > > _______________________________________________________________________ > 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 > The information contained in this message and any attached files may be privileged and/or confidential and protected from disclosure. If you are not the intended recipient, any disclosure, copying, distribution or use of any of the information contained in or attached to this transmission is strictly prohibited. If you have received this transmission in error, please so notify the sender immediately without reading it. Also, please promptly destroy the original transmission and its attachments. Any views or opinions presented in this message or attachments are those of the author and do not necessarily represent those of KapStone Paper and Packaging Corporation or its subsidiaries. _______________________________________________________________________ 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