Xmanager supports command line options to interface with other user applications. When you run Xmanager directly, it does not read an Xstart or Xbrowser session and you should specify the connection method and display number as command line options.
Xmanager command line usage:
Xmanager [-query hostname|-broadcast|-indirect hostname] [:digit]
Some examples are listed below.
| Usage | Description |
| Xmanager | Runs as a passive mode with the default Xstart profile. The display number is 0 by default; if it is not available, another number is allocated automatically. |
| Xmanager :1 | Runs as a passive mode with the default Xstart profile. The display number is 1; if it is not available, Xmanager aborts. |
| Xmanager -query host | Connects to the host with the XDMCP query method. It uses the default XDMCP profile. The display number is 0 by default; if it is not available, another number is allocated automatically. |
| Xmanager -query host :2 | Connects to the host with the XDMCP query method. It uses the default XDMCP profile. The display number is 2; if it is not available, Xmanager aborts. |
| Xmanager -broadcast | Sends an XDMCP broadcast message to the local network and displays all available XDMCP hosts in a Chooser dialog box. It uses the default XDMCP profile. The display number is 0 by default; if it is not available, another number is allocated automatically. |
| Xmanager -indirect host | Connects to the host with the XDMCP indirect method. The remote host opens a chooser window through Xmanager. It uses the default XDMCP profile. The display number is 0 by default; if it is not available, another number is allocated automatically. |
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.
More information about this error may be available in the server error log.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.