You may recommend that, although humbly of course ;-), but there is a catch however. The standard "ia" account utilizes the "bourne- shell" and as a result also always processes the .profile file.. Executing the "go_dm" will in this case follow the execution of the .profile which can lead to undesired results. If "moving" the .profile to go_dm is a problem because of the other users it may be a better idea to create similar users like ia_remote etc. which will all have their own home directory, just like the "ia" user has /opt/ia for a home. We have sometimes done this to have one remote ia user have "root" privileges while with the standard other one the operator has access to, has the usual limited access. So we ended up with a directory /opt/ia and one with /opt/iaroot. A different use but the idea can be used i guess. Hope this helps, apologies if I missed the point or misunderstood (it's weekend yeah!) Best regards Ron Deen On Friday 1 September 2006 16:35, William C Ricker wrote: > > I would suggest you rename the ".profile" to "go_dm" or "remote_dm" > > and run that script from your exceed terminal. > > May I humbly recommend that instead of renaming the ".profile" > script, that you copy it to a new "go_dm" or "remote_dm". That > way the login functionality of user IA remains intact. > > Also note that the copy, used as "go_dm" or "remote_dm", may need > to be modified to get the correct DISPLAY variable setting. When > used as ".profile", a login script for user IA, it extracts login > information to identify the remote station and builds a DISPLAY > variable setting from that information. That only works if the > remote station logged in using telnet. > > William C Ricker > FeedForward, Inc. > > > > > > _______________________________________________________________________ > 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 _______________________________________________________________________ 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