NoMachine Support

Your questions answered

Knowledge Base

Searching in: Feature Requests
Filter the search results
Target version:
Products:
Status:
Last update:
Searching in: Feature Requests
ID: FR10E01906
Added on:  2007-10-08
Last update: 2019-07-11
Priority: Low
Products: NoMachine Server
Target: 6
Status:  Approved
Giving the possibility to specify some server commands on a per-node basis

In a multinode setup, it may be useful to have the possibility of sending some server commands to a specific remote node only, for example to terminate all sessions on that node or to send a broadcast message to all user connected there.

The NoMachine server usage in detail:


--list [<username> | <sessionid> | <node:port>] [--client-type]
       [--client-version] [--client-platform]

  List all the running sessions. If <username> is provided, list only
  sessions run by the user. If <sessionid> is given, show the complete
  set of information about the session. In a multi-node setup, if
  <node:port> is specified, list only sessions running on that node.
 
  Specify --client-version, --client-type, --client-platform to show
  information about version type (UI or web) and platform.
 

--history [<sessionid> | <username> | <node:port> | clear]
          [--client-type] [--client-version] [--client-platform]
          [--stats] [ --file <file>]

  Show history of all sessions on standard output, including those
  that are terminated or failed. Redirect the output to a given
  file if --file is given, this can be used in conjunction with all
  the other options. The history backlog lasts for the number of
  seconds specified in the server configuration, reset it by using
  the 'clear' option. In a multi-node setup, if <node:port> is given,
  show history of sessions related to that node only.
Use <sessionid>
  to show information about the session, included debug logs if the
  session is failed. Provide <username> to list only sessions of that
  user. When --client-type, --client-version and --client-platform
  are given, show information about the client. Provide the --stats
  option to elaborate sessions statistics.  
 

--terminate [<sessionid> | <display> | <username> | <node:port>]

  Terminate the given session. Sessions are univocally identified by
  <sessionid>. If <display> is given, terminate all session running
  on the display. When <username> is provided, terminate all sessions
  run by the user. In a multi-node setup, if <node:port> is provided,
  terminate all sessions running on that node.

 

--disconnect [<sessionid> | <display> | <username> | <node:port>]

  Disconnect the given session. Sessions are univocally identified by
  <sessionid>. If <display> is given, disconnect all session running
  on the display. When <username> is provided, disconnect all sessions
  run by the user. In a multi-node setup, if <node:port> is provided,
  disconnect all sessions running on that node.

--suspend [<sessionid> | <display> | <username> | <node:port>]

  See --disconnect command.
 
 
--kill [<sessionid> | <display> | <username> | <node:port>]

  Kill hard the given session. Sessions are univocally identified by
  <sessionid>. If <display> is given, kill -9 all sessions running
  on the display. When <username> is provided, kill -9 all sessions
  run by the user. In a multi-node setup, if <node:port> is provided,
  kill all sessions running on that node.

 
--broadcast <message> [--node <node:port>]

  Send a broadcast message to all the running sessions. In a multi-
  node setup, provide --node <node:port> to send the message only to
  sessions running on that node.

 
 

 


Notify me when the FR is implemented.