Copyright 1994, 1998 The Open Group Permission to use, copy, modify, distribute, and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS"...
NAMEsmproxy - Session Manager Proxy
SYNOPSISsmproxy [-clientId id] [-restore saveFile] [-version]
- -clientId id
- Specifies the session ID used by smproxy in the previous session.
- -restore saveFile
- Specifies the file used by smproxy to save state in the previous session.
- Prints the program version and exits.
smproxy allows X applications that do not support X11R6 session
management to participate in an X11R6 session.
In order for smproxy to act as a proxy for an X application, one of
the following must be true:
- The application maps a top level window containing the
WM_CLIENT_LEADER property. This property provides a pointer to
the client leader window which contains the WM_CLASS, WM_NAME,
WM_COMMAND, and WM_CLIENT_MACHINE properties.
- The application maps a top level window which does not contain the WM_CLIENT_LEADER property. However, this top level window contains the WM_CLASS, WM_NAME, WM_COMMAND, and WM_CLIENT_MACHINE properties.
An application that support the WM_SAVE_YOURSELF protocol will receive a WM_SAVE_YOURSELF client message each time the session manager issues a checkpoint or shutdown. This allows the application to save state. If an application does not support the WM_SAVE_YOURSELF protocol, then the proxy will provide enough information to the session manager to restart the application (using WM_COMMAND), but no state will be restored.