[foxboro] DM/Foxview "view only" configuration question
- From: stan <stanb@xxxxxxxxx>
- To: Foxboro List <foxboro@xxxxxxxxxxxxx>
- Date: Wed, 27 Aug 2003 13:28:59 -0400
I've got a node running Foxview that we presently have the abilty to start
multiple "real" (omset enabled) copies of Foxview running localy on the
AW's. We can asl start sessions pointed to remote X servers which are "view
only" (omsets disabled).
I want to replace (or suplement) the remte X sessions with VNC sessions.
The problem is that since under VNC the X server is running on the AW, iut
starts up as a full working (omsets enabled) session. How can I get it to
diferentiate between the local Foxview sessiosn, and the "local" ones that
point to a remote VNC client?
I'm including the dmcfg file for reference.
#----------------------------------------------------------------------------
#----------------------------------------------------------------------------
#
# D I S P L A Y M A N A G E R C O N F I G U R A T I O N
#
# and
#
# A L A R M M A N A G E R C O N F I G U R A T I O N
#
#----------------------------------------------------------------------------
#----------------------------------------------------------------------------
#
# Use this file to configure additional Display Managers and Alarm Managers
# for workstations with multiple Display Manager support. Brief configuration
# instructions are provided for each section. Following the instructional
# sections is a template where actual configuration information should be
# entered.
#
# Refer to the document Display Engineering for 50-Series Workstations
# for complete instructions. An overview of the configuration process
# can be found in the file /usr/fox/customer/hi/dmcfg.man.
#
# With the V4.2 release of I/A, there is a configurator (DispAlarmCfg)
# available on the Model 51 Workstations accessible from under the Display
# Manager's "Config" menu pick.
#----------------------------------------------------------------------------
#----------------------------------------------------------------------------
#
# Display and Alarm Manager SCREEN configuration (optional section)
#
# Begin each line with the keyword SCREEN. List the monitors
# associated with each Screen Variable. Use this section to define
# a list of monitors to which a Display Manager and/or an Alarm Manager
# may dedicated. The screen variable is used in the monitor field of
# the NAME and AMNAME sections, described later.
#
#
# SCREEN <screen_variable> <monitor1> <monitor2> ....
# Example:
# SCREEN PLANT_MONITORS term100 term101 term102
#----------------------------------------------------------------------------
# Display Manager TYPE configuration (optional section)
#
# Use this section to assign customized attributes to all Display Managers
# of the same type. Display Manager types are assigned in the NAME
# section, which is described later. Sample TYPE definitions are
# provided at the end of this file. These types may be customized
# per application and new TYPEs added.
#
# Begin each line with the keyword TYPE, followed by an entry for each
# of the following fields. Options for each field are also identified.
#
# TYPE <type> <window attributes> <class> <environment>
#
# Window Size (pick 1):
# user- D Default B Boot Full path name of
# defined F Full O Operator environment file
# type Qxx Quarter E Engineer or path name
# name xx UL,UR,LL,LR V View Only relative to
# Ixx Intermediate - Operator /usr/fox/sys/Change_Env
# xx UL,UR,LL,LR " previous value
# Window Properties
# (pick any/all):
# S reSizeable
# M Min. resize
# is size Q
# - default = DSM
# " previous value
#----------------------------------------------------------------------------
# Alarm Manager AMTYPE configuration (optional section)
#
# Use this section to assign customized attributes to all Alarm Managers
# of the same type. Alarm Manager types are assigned in the AMNAME
# section, which is described later. Sample AMTYPE definitions are
# provided at the end of this file. These types may be customized
# per application and new AMTYPEs added.
#
# Begin each line with the keyword AMTYPE, followed by an entry for each
# of the following fields. Options for each field are also identified.
#
# AMTYPE <amtype> <class> <first environment>
#
# user- B Boot Full path name of
# defined O Operator environment file
# type E Engineer or path name
# name V View Only relative to /usr/fox/sys/Change_Env
# " previous value
# - default class (O)
#
# Note: Unlike Display Manager's TYPE specification, the AM's window
# size and position can be specified only by using the
# Display & Alarm Manager configurator ("DispAlarmCfg").
#----------------------------------------------------------------------------
# Display Manager NAME Assignment
#
# This section of the file is where individual Display Managers are
# identified. If no Display Manager type is assigned, default attributes
# are assigned as follows:
# window_attributes: DSM (default window size, resizable to quarter
# screen minimum.)
# class O
# environment -
#
# Begin each line with the keyword NAME, followed by an entry for each
# of the following fields. Options for each field are also identified.
#
# NAME <lbug> <dmname> <dedicated monitor(s)> <type>
#
# station unique 6- .0 primary head user-defined
# letterbug character .1 second head Display Manager
# " previous Display .- either local type (14
# value Manager head character maximum)
# name xxx Xserver name - no type
# of remote " previous value
# terminal
# $screen_variable
# user-defined
# SCREEN varaible
# - any monitor
# (undedicated DM)
# " previous value
#----------------------------------------------------------------------------
# Alarm Manager AMNAME Assignment (Optional)
#
# This section of the file is where individual Alarm Managers are
# identified. If no Alarm Manager type is assigned, default attributes
# are assigned as follows:
#
# class O
# environment -
#
# Begin each line with the keyword AMNAME, followed by an entry for each
# of the following fields. Options for each field are also identified.
#
# AMNAME <lbug> <amname> <dedicated monitor(s)> <amtype>
#
# station unique 6- .0 primary head user-defined
# letterbug character .1 second head Alarm Manager
# " previous Alarm .- either local type (14
# value Manager head character maximum)
# name xxx Xserver name - no type
# of remote " previous value
# terminal
# $screen_variable
# user-defined
# SCREEN varaible
# - any monitor
# (undedicated AM)
# " previous value
#
# Note: The AMTYPE definition must be defined before this section.
#----------------------------------------------------------------------------
#
# Display Manager to Alarm Manager Associations DMTOAM (optional)
#
# Use this section associates a Display Manager to a named version
# of Alarm Manager. If no Alarm Manager is named, then a default
# will be chosen. Note that multiple Display Managers may be associated
# to the same Alarm Manager.
#
# Begin each line with the keyword DMTOAM, followed by an entry for each
# of the following fields.
#
# DMTOAM <dmname> <amname>
#
# Display Alarm
# Manager Manager
# Name Name
# defined defined
# by NAME by AMNAME
#
# Note: Both NAME and AMNAME definitions must be defined before this section.
#
# Configuration of Multiple Display and Alarm Managers
#
#
# SCREEN <screen_variable> <monitor1> <monitor2> ....
#
#
# TYPE <type> <window attributes> <class> <environment>
#
TYPE _DEFAULT FSM B Proc_Op_Env
TYPE Operator - B Proc_Op_Env
TYPE AuxillaryOper QLRSM O Proc_Op_Env
TYPE RemoteOperator - O Proc_Op_Env
TYPE Engineer - E Proc_Eng_Env
TYPE View_Only - V -
#
# AMTYPE <type> <class> <environment>
#
AMTYPE Operator B Proc_Op_Env
AMTYPE AuxillaryOper O Proc_Op_Env
AMTYPE RemoteOperator O Proc_Op_Env
AMTYPE Engineer E Proc_Eng_Env
AMTYPE View_Only V -
#
# NAME <lbug> <dmname> <dedicated monitor(s)> <type>
#
NAME AW0101 AW0101 .0 _DEFAULT
NAME AW0101 DM0000 - _DEFAULT
NAME AW0101 DM0007 - _DEFAULT
NAME AW0102 AW0102 .0 _DEFAULT
NAME AW0102 DM0001 - _DEFAULT
NAME AW0102 DM0002 - _DEFAULT
NAME WP0103 WP0103 .0 _DEFAULT
NAME WP0103 DM0003 .1 _DEFAULT
NAME WP0104 WP0104 .0 _DEFAULT
NAME WP0104 DM0004 .1 _DEFAULT
NAME WP0105 WP0105 .0 _DEFAULT
NAME WP0105 DM0005 .1 _DEFAULT
NAME WP0106 WP0106 .0 _DEFAULT
NAME WP0106 DM0006 .1 _DEFAULT
NAME WP0107 WP0107 .0 _DEFAULT
NAME WP0108 WP0108 .0 _DEFAULT
NAME WP0109 WP0109 .0 _DEFAULT
# AMNAME <lbug> <amname> <dedicated monitor(s)> <amtype>
AMNAME WP0103 AM0003 .1 -
AMNAME WP0104 AM0004 .1 -
AMNAME WP0105 AM0005 .1 -
AMNAME WP0106 AM0006 .1 -
# DMTOAM <dmname> <amname>
DMTOAM DM0003 AM0003
DMTOAM DM0004 AM0004
DMTOAM DM0005 AM0005
DMTOAM DM0006 AM0006
--
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
-- Benjamin Franklin
_______________________________________________________________________
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: http://www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
Other related posts:
- » [foxboro] DM/Foxview "view only" configuration question