Skip site navigation (1)Skip section navigation (2)

FreeBSD Manual Pages


home | help
dtsession(user cmd)					   dtsession(user cmd)

       dtsession -- the	CDE Session Manager

       dtsession [-norestore]  [-session session_name]

       The  dtsession client provides X11R6 XSMP and (by proxy)	ICCCM 1.1 com-
       pliant session management functionality during a	user session, which is
       the  time from login to logout. It launches a window manager and	allows
       for saving a session, restoring a session, locking a session, launching
       screen savers and allocating colors for desktop compatible clients.

   Key Supported Tasks
       The dtsession client supports the following key tasks:

	  o  Initializing a session.

	  o  Launching a window	manager.

	  o  Restoring a home, current,	display-specific home, or display-spe-
	     cific current session.

	  o  Providing session locking on command or timeout.

	  o  Providing session screen saving on	command	or timeout.

	  o  Acting as a color allocation server for other DT clients.

	  o  Saving a home, current, display-specific  home,  or  display-spe-
	     cific current session.

	  o  Displaying	confirmation dialog at logout.

	  o  Displaying	session	selection dialog at logout.

	  o  Terminating a session.

   A Session
       A  session  is  the  collection of applications,	settings and resources
       that are	present	on the user's desktop. Session management is a set  of
       conventions  and	protocols that allow a special session manager such as
       dtsession to save and restore a user's session. A user is able  to  log
       into  their system and be presented with	the same set of	running	appli-
       cations,	settings and resources as were present when  the  user	logged
       off.  When  a  user logs	into the desktop for the first time, a default
       initial (new user) session is loaded.   Afterward,  dtsession  supports
       the  notion of a	current, a home, and a display-specific	session, which
       may be either current or	home.

   The Initial Session
       When a user logs	into the desktop for the first	time,  dtsession  will
       generate	 the  user's initial session using system default values.  The
       initial session is sometimes referred to	as the "new user" session. Re-
       fer  to	Session	Resource Management and	Session	Application Management
       for more	information.

   The Current Session
       The user's running session is always considered	the  current  session,
       whether	restored upon login from a saved home session, a saved current
       session or the system default initial  session.	Based  on  the	user's
       Style  Manager  Startup	settings, when the user	exits the session, the
       current session is automatically	saved. When the	user  next  logs  into
       the  desktop,  dtsession	allows the user	to select the previously saved
       current session as the session to start.	This means  that  the  desktop
       will  be	restored to the	same state it was in when the user last	logged

   The Home Session
       Another option is having	the desktop be restored	to the same state  ev-
       ery time	the user logs in, regardless of	its state when the user	logged
       out. The	user may save the state	of the current session,	then  via  the
       Style Manager Startup settings, have the	desktop	start that session ev-
       ery time	the user logs in. Alternatively, dtsession will	allow the user
       to select the home session as the session to start at login.

   Display-specific Sessions
       To  run	a specific session for a specific display, a user can create a
       display-specific	 session.  To  do  this,  the  user   can   copy   the
       $HOME/.dt/sessions  directory  to the $HOME/.dt/sessions/display	direc-
       tory where display is the  real,	 unqualified  hostname	(for  example,
       pablo:0	is  valid, or	local:0	is not). When the user
       logs in,	dtsession will allow the user  to  select  a  display-specific
       home  or	 current session as the	session	to start. Dtsession will actu-
       ally launch the session only if it is compatible	with the user's	 login

   The X11R6 XSMP Session Management Protocol
       For an application to be	saved upon logout and restarted	upon login, it
       must participate	in a simple  session  management  protocol.  dtsession
       supports	the X11R6 XSMP Session Management Protocol.

       Applications  that  wish	 to  save  their  state	 can  take part	in the
       WM_SAVE_YOURSELF	protocol. To do	this, an application needs to set  the
       WM_SAVE_YOURSELF	property on one	and only one of	its top-level windows.
       When the	user presses the Set Home Session button in the	Style Manager,
       dtsession  sends	a SaveYourself message to the top-level	window of each
       of its clients. The message sets	the save-type to Local,	shutdown to 0,
       interact-style to None and fast to 0.

       When  an	 application  receives	the  message, it sends a SaveYourself-
       Phase2Request message to	the Session Manager, which will	reply  with  a
       SaveYourselfPhase2  message.  Only when the Window Manager receives the
       SaveYourselfPhase2 message will it save	its  state.   The  information
       saved  by  the  Window  Manager for each	of its client's	set of windows
       will include: geometry, icon state and workspace.

       If interact-style on the	initial	SaveYourself message is	None, the  ap-
       plication  cannot interact with the user	in any way as it is saving its
       state. If it is Any, the	application can	interact with the user for any
       purpose.	 This includes the ability to de-iconify itself, as well as to
       change its current workspace.  To minimize confusion, the Session  Man-
       ager  issues  a	ToolTalk  message to the Window	Manager	requesting the
       recommended order to interact. The Window  Manager  responds  with  the
       list  of	 SM_CLIENT_IDs	and  their  associated	workspace  numbers  in
       workspace order.	After receiving	an Interact  message  (with  interact-
       style  set  to  Any),  an application should go system-modal to prevent
       other, less well-behaved	 non-interacting  applications	from  allowing
       user interaction	while the application is interacting with its user.

       Because	an  application	 will  usually save its	state into a file, the
       Session Manager provides	DtSessionSavePath as  a	 convenience  function
       that returns a full pathname of a file in which an application can save
       its state. While	the application	is saving its state, dtsession	awaits
       notice from the application that	it is done. To tell dtsession that the
       state save is complete, the application updates the WM_COMMAND property
       on its top-level	window.

       The WM_COMMAND property on an application's top-level window serves two
       purposes. First,	a change of this property is the indication to	dtses-
       sion  that  an  application  is done saving its state and dtsession can
       proceed to the next application.	Second,	the WM_COMMAND property	 value
       is  expected  to	 contain  the  command line that dtsession will	use to
       restart the application	at  session  startup.  If  an  application  is
       launched	 with  a  full	pathname, then it should use the full pathname
       when setting WM_COMMAND.	Applications that do not need  to  save	 their
       state,  but  wish to be restarted, can simply set WM_COMMAND during ap-
       plication startup and forget about it.

       Refer to	the XmAddWmProtocols, XmAddWMProtocolCallback, and XSetCommand
       APIs for	more information.

       In  addition  to	the "save-yourself" client session management support,
       the X11R6 XSMP protocol provides	the following features (which are  not
       found in	the ICCCM protocol):

	  o  It	 allows	 applications  to interact with	the user during	normal
	     shut down to confirm or discard unsaved changes.

	  o  It	provides a mechanism to	explicitly tell	applications to	exit.

	  o  Most importantly, it provides a common framework to  support  ap-
	     plications	 that are not X	clients	and applications that exit be-
	     fore the session is saved but that	must remain part of  the  ses-
	     sion for restart purposes (for example, an	input method server).

   The ICCCM Session Management	Protocol
       dtsession  implements  the  X11R6  XSMP session management protocol and
       provides	backward compatibility by acting as a proxy for	client	appli-
       cations	that continue to use the older ICCCM session management	proto-

   Restoring A Session
       At session startup time,	dtsession presents a dialog  that  allows  the
       user to select which of the following sessions to start:

       Current	 Start the user's most recent session.

       Home	 Start the user's home session.

       display-name - Current
		 Create	 a new display-specific	session	and start the first of
		 the following sessions	that exists:

		    0. display-specific	Home

		    1. generic Home

		    2. new user	(initial) session

       display-name - Home
		 Create	a new display-specific session and  start  the	user's
		 generic  home	session	 if  it	exists.	Otherwise, start a new
		 user session.

       Fail-safe Session
		 Start a fail-safe session (Xfailsafe)

       Although	a user's list of sessions is not known until  after  the  user
       logs  in, the dialog presents all of the	session	choices. If a user se-
       lects a session that does not exist, dtsession takes the	following  ac-
       tions. If the user selects:

       Home	 dtsession starts a new	user session.

       Current	 dtsession starts the user's home session if it	exists.	 If it
		 does not, it starts a new user	session.

       If the user selects a display-specific session and one does not	exist,
       dtsession  posts	 a  warning  dialog stating that a new session will be
       created.	The warning dialog contains three buttons:

       Cancel Login
		 Cancels the login and returns the user	to the login screen.

       OK	 If a display-specific Home session  was  selected,  dtsession
		 creates  a new	display-specific session and starts the	user's
		 generic home session if it exists. If it does not  exist,  it
		 starts	a new user session.

		 If a display-specific Current session was selected, dtsession
		 creates a new display-specific	session	and starts a  display-
		 specific  home,  generic home,	or new user session, depending
		 on which it finds first.

       Help	 Displays help text about the warning dialog.

   Session Resource Management
       The session manager uses	the  X	Server	RESOURCE_MANAGER  property  on
       which to	make available desktop resources to all	applications. The ses-
       sion manager will load the RESOURCE_MANAGER in the following manner:

	  o  load the system default resources,	AND

	  o  merge any system administrator specified resources, AND

	  o  merge any user specified resources.

       The desktop  default  resources	can  be	 found	in  /usr/local/dt/con-
       fig/$LANG/sys.resources.	  These	 resources  will  be made available to
       each user's session via the RESOURCE_MANAGER property. This file	should
       not be edited as	it will	be unconditionally overwritten upon subsequent
       desktop installations.

       A system	administrator may augment the system default resources by cre-
       ating  /usr/local/etc/dt/config/$LANG/sys.resources.  In	 this  file, a
       system administrator may	override system	default	resources  or  specify
       additional  resources.  As this file is merged into the desktop default
       resources during	session	startup, it is preferable that only new	or up-
       dated  resource	specifications	be  placed in this file, rather	than a
       copy being made of the desktop default resource file. Resources	speci-
       fied in this file will be made available	to each	user's session via the
       RESOURCE_MANAGER	property. Resources specified in this file take	prece-
       dence over those	specified in the desktop default resource file.

       A  user	may  augment  the desktop default and system administrator re-
       sources via their $HOME/.Xdefaults file.	Resources  specified  in  this
       file  will  be  made  available to only that user's session via the RE-
       SOURCE_MANAGER property.	Resources specified in this file  take	prece-
       dence over those	specified in the desktop default or system administra-
       tor resource files.


	      The X Toolkit Intrinsics specifies that it will  load  resources
	      for   an	 application  from  either  RESOURCE_MANAGER  or  from
	      $HOME/.Xdefaults,	but not	both. Ordinarily, this would mean that
	      the  user's $HOME/.Xdefaults file	would be ignored. However, the
	      session manager accommodates $HOME/.Xdefaults by merging it into
	      the RESOURCE_MANAGER at session startup as described above. If a
	      user changes $HOME/.Xdefaults, the changes will not  be  visible
	      to  new  applications until the user invokes the ReloadResources

       The ReloadResources action will instruct	the session manager to	reload
       the  RESOURCE_MANAGER  with  the	system,	system administrator, and user
       specified resources. This is useful to make available to	 new  applica-
       tions  changes  made to system administrator or user specified resource

       See also	dtresourcesfile(4) and dtsessionaction(5).

   Session Application Management
       At session startup, the session manager will restart  any  applications
       that  were  saved as part of the	session. The system default set	of ap-
       plications to be	restored as part of the	user's Initial Session can  be
       found  in  /usr/local/dt/config/$LANG/sys.session. This file should not
       be edited as it will be	unconditionally	 overwritten  upon  subsequent
       desktop installations.

       See also	dtsessionfile(4).

       A system	administrator may replace the set of applications that are re-
       stored as part of the user's Initial Session by creating	a  file	 named
       /usr/local/etc/dt/config/$LANG/sys.session.  Unlike the resource	files,
       this file will be used as a complete replacement	for  the  desktop  de-
       fault  file,  so	 it is valid to	make a copy of the system default file
       and make	any necessary modifications.

   Session Manager Authentication
       The Session Manager uses	ICE-based authentication as described  in  the
       Inter-Client Exchange (ICE) Library v1.0.

       The  Session  Manager is	built with a table of available	authentication
       protocols. Selection of the protocol is done via	the AuthName resource.
       The AuthName default is the string MIT-MAGIC-COOKIE-1. The Session Man-
       ager supports the same protocols	as the Login Manager.

   The Window Manager
       dtsession is responsible	for starting the window	 manager.  By  default
       /usr/local/dt/bin/dtwm  is  started. An alternate window	manager	can be
       specified with the wmStartupCommand resource. Refer  to	the  Workspace
       Manager specification for more information.

   The Style Manager
       The  style  manager  provides  the interface by which a user can	change
       various desktop and X server settings for the current session. Refer to
       the Style Manager specification for more	information.

   The Color Server
       dtsession serves	as the color server for	the desktop and	provides a set
       of resources that can be	used to	configure it.  The foregroundColor re-
       source  controls	whether	a pixel	is allocated for the foreground	color.
       The dynamicColor	resource specifies whether read-only colors are	 allo-
       cated.  The  shadowPixmaps  resource specifies whether colors are allo-
       cated for top shadow or bottom shadow.  The  colorUse  resource	limits
       color  allocation.  Finally,  the  writeXrdbColors  resource  specifies
       whether the *background and *foreground resources are placed in the re-
       source database.	See the	Color Server Resources section for more	infor-

   The Color Sharing Protocol
       The CDE desktop makes use of a color sharing protocol between dtsession
       and  the	 rest  of  the desktop (dtstyle	in particular) and Motif. This
       protocol	allows:

	  o  Non-CDE (non Motif/XmColorObject) applications to make use	of the
	     CDE color scheme.

	  o  Applications  (Motif  or  not) that create	their own private col-
	     ormap to copy the dtsession desktop pixels	 and  avoid  or	 limit
	     technicolor effect.

	  o  Motif  applications  to  easily share the desktop GUI pixels when
	     they use a	private	colormap.

       The color sharing protocol involves:

	  o  The selection name	(CUSTOMIZE_DATA), type (TYPE_OF_MONITOR),  and
	     format used by dtsession to communicate the monitor characteriza-
	     tion to dtstyle (or any other style manager).

	  o  The selection name	(CUSTOMIZE_DATA), type (PIXEL_SET), and	format
	     used  by  dtsession  to  communicate its palette pixel ids	to the
	     ColorObject (in libXm) and	to dtstyle.

	  o  Two functions (XmeGetColorObjData and  XmeGetColorObjCells)  that
	     deliver  the  desktop  pixels to the application in a form	easily
	     suitable for its use (XColor).

       A Color Set is a	set of five colors that	are used to represent a	single
       logical color in	the Motif toolkit. For each background color (the log-
       ical color), there are associated  top  shadow,	bottom	shadow,	 fore-
       ground,	and  select  colors,  all generated from the background	color.
       These associated	colors are the mechanism for giving widgets their  3-D

       A Color Palette is a named set of a maximum of eight background colors.
       A single	palette	is used	to color the desktop components. A list	of de-
       fault palettes is provided from which the user can select. The user can
       also add	and delete palettes, as	well as	modify an existing palette.

       dtsession, the color server, uses ICCCM X Selection based mechanisms to
       communicate  color  use,	palette	and color set pixel information	to the
       desktop clients.

       The name	of  the	 (CUSTOMIZE_DATA)  selection  is  the  atom  Customize
       Data:i, where i is the screen number.

       The names of the	targets	are the	atoms Type Of Monitor and Pixel	Sets.

   Type	of Monitor Target
       The  Type  Of  Monitor  target  is used to convey color settings	to the
       desktop clients,	such as	dtstyle	or the Motif toolkit, that  need  this
       information.  The  content  corresponds	to  the	value of the dtsession
       color usage resources.

       When asked to convert the screen	Customize Data:i selection to the tar-
       get  Type  Of Monitor, the format and content encoding used is the fol-

	  o  type: STRING

	  o  length: 20

	  o  format: 8

	  o  content: a	series of 4 numbers, in	hexadecimal format,  separated
	     by	 the underscore	(_) character (that is,	using the printf/scanf
	     format %x_%x_%x_%x), and including	from left to right:

		o  The colorUse	resource, which	corresponds  to	 the  type  of
		   monitor in use by the desktop.

			     B_W = 0

			     LOW_COLOR = 1

			     MEDIUM_COLOR = 2

			     HIGH_COLOR	= 3

		o  The	shadowPixmaps  resource,  which	 controls  if dithered
		   pixmaps are used to render the shadows in the target	GUI.

			     FALSE = 0

			     TRUE = 1

		o  The foregroundColor resource, which controls	whether	or not
		   a  pixel  was allocated for the foreground or if WhitePixel
		   or BlackPixel is used.

			     DYNAMIC = 0

			     BLACK = 1

			     WHITE = 2

		o  The dynamicColor resource, which controls  whether  or  not
		   the pixels allocated	are read/write or read-only cells.

			     FALSE = 0

			     TRUE = 1

       This  information,  especially  dynamicColor, is	currently used only by
       dtstyle in CDE to implement the color manager GUI.

   Pixel Sets Target
       The Pixel Sets target is	used to	convey palette and color set pixel in-
       formation  to  the  desktop  clients. The content is always 8 color set
       values, but depending on	the color usage	settings, some entries will be
       the  duplicated.	For the	receiver of this information, however, it sim-
       ply means it can	access the  index  as  specified  in  the  high	 color

       When asked to convert the screen	Customize Data:i selection to the tar-
       get Pixel Sets, the format used is the following:

	  o  type: STRING

	  o  length: 400

	  o  format: 8

	  o  content: a	first number (%x_)  for	 the  colorUse	resource  (see
	     "Type  of	Monitor	 Target" above for encoding) and a series of 8
	     (corresponding to the maximum number of color sets	in  CDE)  sets
	     of	 5  numbers,  in hexadecimal format (%x_%x_%x_%x_%x), each de-
	     scribing from left	to right:

		o  background pixel (bg)

		o  foreground pixel (fg)

		o  top_shadow pixel (ts)

		o  bottom_shadow pixel (bs)

		o  select_color	pixel (sc)

       The mapping between color set Ids and colorUse is as follows:


		3. Active window borders.

		4. Inactive window borders.

		5. Switch for workspace	1 and every fourth additonal workspace
		   (workspace 5, 9,...).

		6. Text	and list areas.

		7. Main	 window	 background (primaryColorSetId)	and switch for
		   workspace  4	 and   every   fourth	additional   workspace
		   (workspace 8, 12,...).

		8. Dialog  box	background  and	menu bar (secondaryColorSetId)
		   and switch for workspace  3	and  every  fourth  additional
		   workspace (workspace	7, 11,...).

		9. Switch  for workspace 2 and every fourth addional workspace
		   (workspace 6, 10, ...).

		   Front panel background.


		   Active window borders.

		   Window bodies:

		      o	 Inactive window borders

		      o	 Main window and dialog	box backgrounds	and menu bar

		      o	 Front Panel background

		   Workspace switches and backgrounds

		   Text	and list backgrounds

		   same	as 2

		   same	as 2

		   same	as 3

		   same	as 2


		   Active window borders.

		   Everything else.

		   .. to 8: same as 2.

       For each	color set, the cell allocation scheme is the following (dynam-
       icColor	determines  if	the  pixels  are allocated read/write or read-

       colorUse		    shadowPixmaps	foregroundColor	      Cells allocation	 Number
       HIGH_COLOR	    FALSE		DYNAMIC		      (fg,bg,ts,bs,sc)	 5*8 = 40
       HIGH_COLOR	    FALSE		BLACK or WHITE	      (bg,ts,bs,sc)	 4*8 = 32
       HIGH_COLOR	    TRUE		DYNAMIC		      (fg,bg,sc)	 3*8 = 24
       HIGH_COLOR	    TRUE		BLACK or WHITE	      (bg,sc)		 2*8 = 16
       MEDIUM_COLOR	    FALSE		DYNAMIC		      (fg,bg,ts,bs,sc)	 5*4 = 20
       MEDIUM_COLOR	    FALSE		BLACK or WHITE	      (bg,ts,bs,sc)	 4*4 = 16
       MEDIUM_COLOR	    TRUE		DYNAMIC		      (fg,bg,sc)	 3*4 = 12
       MEDIUM_COLOR	    TRUE		BLACK or WHITE	      (bg,sc)		 2*4 = 8
       LOW_COLOR	    FALSE		DYNAMIC		      (fg,bg,ts,bs,sc)	 5*2 = 10
       LOW_COLOR	    FALSE		BLACK or WHITE	      (bg,ts,bs,sc)	 4*2 = 8
       LOW_COLOR	    TRUE		DYNAMIC		      (fg,bg,sc)	 3*2 = 6
       LOW_COLOR	    TRUE		BLACK or WHITE	      (bg,sc)		 2*2 = 4
       B_W		    TRUE		opposite	      BG		 0

   Session Lock
       Dtsession provides session locking. The current session can  be	locked
       directly	 by pressing the lock icon on the front	panel. If supported by
       the X server, the current session can be	locked after a	specified  pe-
       riod  of	 inactivity.  To unlock	the session, the user must enter their
       login password.

       By default, dtsession supports traditional  local  UNIX	authentication
       for  unlocking the session. Additional re-authentication	functions such
       as those	required by DCE	may be added by	individual vendors.

   Screen Savers
       Dtsession provides support for the launching of external	screen	savers
       as  a  part of session locking from the front panel or, if supported by
       the X server, after a specified period  of  inactivity.	Refer  to  the
       Screen  Saver specification for information as to how screen savers are
       integrated into the desktop.

   X Server Screen Saver Extensions
       Dtsession's ability to provide session lock or screen saver launch  af-
       ter  a  specified period	of inactivity depends upon the availability of
       an X server screen saver	extension. dtsession supports two such	exten-

	  o  X Consortium Sample X11 Screen Saver Extension 1.0

	  o  HP	X Screen Saver Extension

       The ability of dtsession	to recognize both, either or none of these ex-
       tensions	is vendor specific.

   Launching The Session Manager
       dtsession should	be launched from the Xsession script.  Xsession	is de-
       scribed	in  the	 login	manager	 specification.	It is recommended that
       Xsession	be launched from dtlogin as part of the	login sequence as  the
       default,	but there are alternative methods of starting Xsession:

       dtlogin	 the  default  dtlogin	configuration launches Xsession	when a
		 user logs in

       proxy	 some systems will allow programs such as xinit,  x11start  or
		 startx	to start Xsession

   Starting Services Before the	Session	Manager
       If  you must start a service after login	but before the Session Manager
       (for example, an	input method server), start the	service	by  placing  a
       script in the fdirectory	/usr/local/dt/config/Xsession.d.

       To  avoid  being	 restarted  by	the  Session Manager when a session is
       started,	a service that must be	started	 before	 the  Session  Manager
       should  explicitly  set	the  RestartStyleHint property to RestartNever
       (possibly by setting an Xt resource).

       The dtsession client is automatically invoked by	the DT	Login  Manager
       (dtlogin).  If  desired,	dtsession may also be started on an existing X
       server. Note that dtsession automatically starts	a window manager.

       The following options are available:

		 Instructs dtsession not to restore  a	previous  session  nor
		 save the session upon logout.

       -session	session_name
		 Instructs  dtsession  to  start the specified session.	 Valid
		 session names are:

		    o  current

		    o  home

		    o  display_name:display_number /current

		    o  display_name:display_number /home

		 where display_name is the unqualified display host  name  and
		 display_number	is the display number.

       Exit values are:

       0	 Successful completion.

       >1	 Error condition occurred.

   dtsession -norestore
       Start session manager from command line without restoring previous ses-

   Color Server
       Name		 Class		   Type		Default
       colorUse		 ColorUse	   String	DEFAULT
       dynamicColor	 DynamicColor	   Boolean	True
       foregroundColor	 ForegroundColor   String	DYNAMIC
       shadowPixmaps	 ShadowPixmaps	   String	DEFAULT
       writeXrdbColors	 WriteXrdbColors   Boolean	True

   Screen Lock/Screen Save
       Name		 Class		    Type	    Default
       keys		 Keys		    unsigned char   NULL
       passwordTimeout	 passwordTimeout    unsigned int    10

       Name		      Class		    Type	      Default
       AuthName		      AuthName		    String	      DEFAULT
       IgnoreEnvironment      IgnoreEnvironment	    String	      NULL
       queryServerSettings    QueryServerSettings   Boolean	      False
       NumSessionsBackedup    NumSessionsBackedup   unsigned int      2
       saveFontPath	      SaveFontPath	    Boolean	      False
       wmStartupCommand	      WmStartupCommand	    executable path   NULL

       This resource specifies the authentication protocol that	 dtsession  is
       to  use.	 The  default is the string MIT-MAGIC-COOKIE-1.	dtsession sup-
       ports the same protocols	as dtlogin.

   colorUse - DEFAULT
       This resource specifies the number of colors to use for the user	inter-
       face.   Valid  types  are:  Color server	will determine type of monitor
       based upon number of display planes of the screen as follows:

       1,2	 B_W

       4	 LOW_COLOR

       6	 MEDIUM_COLOR

       7+	 HIGH_COLOR

		 B_W - Specifies a black and white system. The color  palettes
		 will use two color cells for the user interface. In this con-
		 figuration only two color palettes are	available:  BlackWhite
		 and  WhiteBlack. These	palettes cannot	dynamically change. To
		 change	a palette, all applications using that	color  palette
		 must  be  restarted. This resource value forces ShadowPixmaps
		 to True, and ForegroundColor to either	black or white depend-
		 ing on	the palette chosen.

		 LOW_COLOR  - Specifies	a low color system. The	color palettes
		 will have two color sets and use a maximum of 12 color	 cells
		 for  the  user	 interface,  including	black and white	(color
		 cells 0 and 1). The number  of	 co  ShadowPixmaps  and	 Fore-

		 MEDIUM_COLOR  -  Specifies  a	medium color system. The color
		 palettes will have 4 color sets and use a maximum of 22 color
		 cells	for  the  user	interface,  including  black and white
		 (color	cells 0	and 1).	The number of color cells can  be  re-
		 duced	by  using  the resources ShadowPixmaps and Foreground-

		 HIGH_COLOR - Specifies	a high color system.  The  color  pal-
		 ettes	will  have  8 color sets and use a maximum of 42 color
		 cells for the	user  interface.  including  black  and	 white
		 (color	 cells	0 and 1). The number of	color cells can	be re-
		 duced by using	the resources  ShadowPixmaps  and  Foreground-

       This resource can have values of	True or	False. dynamicColor is used to
       reduce the number of color cells	being used. Once a  palette  has  been
       selected	and it is not likely to	be changed, dynamicColor can be	set to
       False. If set to	False colors cannot be dynamically changed  using  the
       DT  style  manager.   A selected	palette	will take effect the next ses-
       sion. The next time the session comes up, the color  server  uses  Read
       Only  color  cells that can be shared by	all clients, thus reducing the
       number of color cells used.

       This resource can have values of	White, Black or	 Dynamic.  Foreground-
       Color causes all	text (foreground) to use either	pixel 0	or 1 (Black or
       White) or to have a color cell dedicated	to foreground and  changes  in
       response	to the background color	(Dynamic) for each ColorSet. If	set to
       White or	Black, the number of color cells used per ColorSet is  reduced
       by 1.

       This  resource  is  a list of keyholders	who have the ability to	unlock
       the screen any time it is locked	by the user. The list  is  a  list  of
       user  id's separated by commas. For example if user kim has the follow-
       ing resource active during a session:

       Dtsession*keys: fred,keith
		 Users fred and	keith have the ability to unlock  the  display
		 when kim locks	it.

       This  resource  specifies  (in  seconds)	 the amount of time before the
       password	dialog is removed from the screen. When	the display is locked,
       the  pointer  shows  a lock cursor, and a dialog	appears	which asks for
       the user	password.  If no activity from the pointer or keyboard is  de-
       tected  for  passwordTimeout  seconds,  the  dialog is removed from the
       screen. The dialog is redisplayed as soon  as  a	 pointer  or  keyboard
       event  is  detected. An passwordTimeout of 0 leaves the password	dialog
       in place	for the	entire time the	display	is locked.  The	default	 value
       is 10 seconds.

       This  resource specifies	whether	dtsession queries the server at	logout
       for all its settings or saves only those	settings set by	using  the  DT
       Style Manager. Querying the server ensures that all settings are	saved;
       however,	there is a degradation in performance when  a  full  query  is
       done.  The default value	is False, which	means that the server will not
       be queried.

       This resource specifies the number of checkpoints  to  keep.  When  the
       number of checkpoints for a session exceeds this	value, the DiscardCom-
       mand properties for the oldest session will be executed and the	oldest
       checkpoint will be removed. The default is 2.

       For color systems, this resource	can have a value of True or False.  If
       True, topShadowColor and	bottomShadowColor use the same pixel as	 back-
       ground and topShadowPixmap and bottomShadowPixmap are specified instead
       of solid	color to create	the 3D look. This reduces the number of	 color
       cells  per  ColorSet  by	 2. ShadowPixmaps defaults to True for systems
       with 4 or less color planes (16 or less color  cells),  and  False  for
       systems with more than 4	color planes.

       This  resource  allows for an alternate window manager to be started at
       login.  If  this	 resource   is	 NULL,	 dtsession   starts   /usr/lo-
       cal/dt/bin/dtwm.	 An  alternate	startup	might look like: Dtsession*wm-
       StartupCommand: /usr/bin/X11/mwm


	      The command should not have any commands to a shell in  it,  and
	      that  it	should not be surrounded by quotes. Also, if any other
	      window manager other than	dtwm is	 used,	clients	 will  be  re-
	      stored,  but may not be restored to the correct position.	By de-
	      fault, this resource contains a NULL value.

		 The desktop default set of applications for the  user's  Ini-
		 tial Session.

		 System	 Administrator	specified  set of applications for the
		 user's	Initial	Session.

		 The desktop default resources.

		 A log of processes started by the Xsession script. This  file
		 is used only to help diagnose session startup problems.

		 The CDE1.0 database file maintained for each session.

		 When  dtsession is started by the Xsession script, its	stderr
		 is duplicated to a session-specific  file  in	$HOME/.dt/ses-
		 sionlogs,  so	that all stderr	written	by apps	started	by dt-
		 session will get logged in this file.	The name of  the  file
		 that  is  used	is host_name_DISPLAY=$DISPLAY, where host_name
		 is the	name of	the host where the session was started.

		 The CDEnext database file maintained for each session,	 where
		 session_dir  is sessions or the display name for display-spe-
		 cific session_name is either home or current.	 CDEnext  ses-
		 sion databases	supersede CDE1.0 session databases.

		 System	administrator specified	resources.

		 User specified	resources.

		 Dtsession stores session information in $HOME/.dt/sessions or
		 $HOME/.dt/sessions/display. The content of these  directories
		 should	not be directly	edited by the user.

		 Default dtsession resources.

       See related specifications:

       dtstyle	 Customization of many session properties

       dtscreen	 Desktop screen	savers

       dtwm	 Window	manager

       dtlogin	 Login manager

		 Session manager actions

		 Format	and location of	CDEnext	session	database files

		 Format	and location of	CDE 1.0	desktop	session	files

		 Format	and location of	desktop	resource files

       startlog	 Log of	processes started by the Xsession script

							   dtsession(user cmd)


Want to link to this manual page? Use this URL:

home | help