Re: [foxboro] go global access
- From: Ron Deen <r.deen@xxxxxxxxx>
- To: foxboro@xxxxxxxxxxxxx
- Date: Tue, 14 May 2002 06:39:04 +0200
The "ia" account works fine with any X-server but you will need to tweak it a
little.
Soemwhere in the beginning of the .profile file the "server display variable"
is set to the station calling the DM which is fine for programs like exceed
which run their X-server on that remote machine
Programs like go_global en Exceed on Demand install an additional "X-server"
locally on the 51 box. This server is thus the second server on the box as
the SUN openwindows thingy is the first. (And our kind of people start
numbers at 0 because we don't want to waste anything)
So you end up with a server 0 which is the local one on the 51 AND a server 1
which is the second one.
You want DM for remote stations to go to server 1.
Have a look at the .profile or go_dm file in /opt/ia. The place to look is
where the variables "REM_STATION" and "DISPLAY" are filled.
I have not played with it for sometime but this is about where to look.
If you want to use the "ia" account for exceed AND go_global at the same time
I would take the easy way out and clone the "ia" account to have one for
exceed and one more for go_global.
Regards
Ron Deen@home
On Monday 13 May 2002 23:25, you wrote:
> As I understand, "ia" account is intended only for Exceed, it'll not work
> with Go-Global, programming of new user accounts will provide
> secured/controlled access.
>
> Mohamed
>
> -----Original Message-----
> From: Ron Deen [mailto:r.deen@xxxxxxxxx]
> Sent: Monday, May 13, 2002 3:20 PM
> To: foxboro@xxxxxxxxxxxxx
> Subject: Re: [foxboro] go global access
>
>
>
> Try to avoid using the "root" account. Foxboro provides the "ia" account
> for
>
> remote terminals. It's installed on every UNIX system. It does not have
> "root" privileges but usually fits the needs and a qualified engineer could
> always "su".
> For some sites I made a copy of the "ia" account with higher priviliges to
> be
> used when needed. Just log in with that "iaroot" account and you are in
> business.
>
> Also as a nice bonus: the remote terminals keep working after you modify
> the
>
> "root" password which you do every week or so I guess :-)
>
> Just my opinion
>
> Ron Deen@home
>
> On Monday 13 May 2002 19:22, you wrote:
> > Brain,
> >
> > You'll need to program user accounts for each user, so remote users can
>
> and
>
> > /or cannot log-in as 'root', you may use Admintool to program those
> > accounts, refer to SUN administration guide for more details on how to
> > program user accounts. Also you may use useradd/groupadd commands if you
>
> do
>
> > not have admintools.
> > You may also need to program different environments to each remote user,
>
> so
>
> > you can control their access to configurations i.e. ICC/FOXDRAW...etc.
> > refer to Foxboro BO193WZ, Sun System Admin Guide-Volume I chapter 1 and 2
> > and HH876, those documents include valuable data about what you need to
>
> do.
>
> > Mohamed Nasif
> > Process Control & Instrumentation Engineer
> > Air Liquide Canada Inc.
> >
> >
> > -----Original Message-----
> > From: Brian Long [mailto:blong@xxxxxxx]
> > Sent: Monday, May 13, 2002 11:18 AM
> > To: Foxboro
> > Subject: [foxboro] go global access
> >
> >
> >
> >
> > I'm in need of advice on the most secure way to allow go-global users
>
> acces
>
> > to an AW51b box.
> >
> > Thanks,
> >
> > Brian Long
> > Green Bay Packaging
> > Arkansas Kraft Division
> >
> >
> >
> > _______________________________________________________________________
> > 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
>
> _______________________________________________________________________
> 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
_______________________________________________________________________
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:
