nx
Execute commands on remote NX server
TLDR
Build a specific project
Test a specific project
Execute a target on a specific project
Execute a target on multiple projects
Execute a target on all projects in the workspace
Execute a target only on projects that have been changed
SYNOPSIS
nxplayer [OPTIONS] [SESSION_FILE | --url URL]
Note: Running nxplayer without arguments typically launches the graphical user interface to create or manage connections.
PARAMETERS
--session
Loads a specific NoMachine session configuration file (.nxs).
--url
Connects to a remote host specified by a NoMachine URL (e.g., nx://host:port).
--attach
Attaches to an existing remote session by its ID.
--login
Specifies the username for authentication without prompting.
--password
Provides the password for authentication directly (use with caution due to security).
--key
Specifies the path to an SSH private key for key-based authentication.
--full-screen
Starts the remote desktop session in full-screen mode.
--geometry
Sets the initial resolution of the remote desktop window (e.g., 1024x768).
--protocol
Specifies the connection protocol (e.g., NX, SSH, VNC, RDP).
--display
Connects to a specific X display on the local machine.
--disable-audio
Disables audio redirection for the session.
--enable-mic
Enables microphone redirection.
--file-transfer disable
Disables file transfer capabilities.
--print-transfer disable
Disables printer redirection.
--usb-transfer disable
Disables USB device redirection.
--help
Displays a concise help message with common command-line options.
--version
Shows the installed NoMachine client version.
DESCRIPTION
NoMachine NX is a powerful, cross-platform remote desktop technology designed for fast and secure graphical access over networks. The nxplayer command on Linux launches the NoMachine client application, enabling users to establish highly responsive connections to remote NoMachine NX servers. It excels at delivering a smooth graphical experience even on high-latency or low-bandwidth connections, leveraging sophisticated compression, caching, and display rendering techniques. Beyond basic remote access, it supports features like session recording, desktop sharing, file transfer, and device redirection (e.g., USB, printers). While primarily a graphical application, nxplayer can also be driven with command-line arguments for specific session configurations or automation. It serves as a robust alternative to traditional X11 forwarding, VNC, or RDP for those prioritizing performance and security.
CAVEATS
nxplayer is part of the proprietary NoMachine software suite, not a standard open-source utility bundled with most Linux distributions. Installation requires downloading the NoMachine package from their official website. While robust, its functionality is tightly coupled with the NoMachine server software. Command-line usage for complex scenarios can be extensive, and the primary mode of interaction for most users is via its intuitive graphical interface. Providing sensitive information like passwords directly on the command line is generally discouraged due to security risks.
SESSION FILES (.NXS)
nxplayer often uses `.nxs` files to store connection configurations. These XML-based files can be created and managed through the GUI, or manually edited for advanced settings. They encapsulate details like the remote host, port, authentication methods, display settings, and redirected devices, simplifying the process of re-connecting to frequently used sessions.
GUI-CENTRIC OPERATION
While nxplayer accepts command-line arguments, its primary design emphasizes a rich graphical user interface. The GUI provides an intuitive way to discover servers, create and manage sessions, configure advanced options, and interact with features like file transfers and device redirection, making it highly accessible for users who prefer visual interaction over command-line scripting.
HISTORY
The NX technology was originally developed by NoMachine. Early versions gained significant traction through the FreeNX project, an open-source implementation of the NX server, and NXClient which was also provided by NoMachine. This period saw widespread adoption, particularly on Linux, due to its superior performance over VNC. Over time, NoMachine shifted its focus more towards its proprietary solutions, and while the core technology evolved, the open-source FreeNX project became less actively maintained. The modern nxplayer command represents the evolution of the official NoMachine client, offering enhanced features, broader platform support, and tighter integration within the NoMachine ecosystem.