Session Ends When (--endswhen)

Objects with this attribute

Object Manager	Session Ends When	Choose a setting from the list.
Command line	`--endswhen lastclient \| windowmanager \| windowmanageralone \| loginscript \| nowindows \| loginscriptnowindows`	Specify a valid setting.

This attribute determines when an emulator session ends.

Object Manager	Command line	Description
Last client exits	`lastclient`	The server keeps track of the number of X clients running within the session, and ends the session when this reaches zero.
Window Manager exits	`windowmanager`	The server ends the session when the Window Manager exits, no matter how many X clients may be running.
Only Window Manager remains	`windowmanageralone`	The server ends the session when the only remaining X client is the Window Manager. Some Window Managers (such as OpenLook) run X clients in the background, which means that this condition is never met. If you encounter this problem, you should use the No Visible Windows setting (`--endswhen nowindows`).
Login script exits	`loginscript`	The server ends the session when the login script completes. Use this in conjunction with Keep Launch Connection Open if an application has problems shutting down.
No visible windows	`nowindows`	The server ends the session when no windows are visible. This is useful for window managers (such as OpenLook) that run X clients in the background.
Script exits or no windows	`loginscriptnowindows`	The server ends the session when either the login script completes or no windows are visible. Use this for applications that are always resumable and that use X clients as this forces a session to close if an application server is re-booted or disconnected from the network. Use this in conjunction with Keep Launch Connection Open if an application has problems shutting down.

--endswhen nowindows

The emulator session ends when no windows are visible.

Related topics
Keep launch connection open (--keepopen) Understanding webtop and emulator sessions