uli42
commented
7 years ago So what is this ticket about? Do you want to contribute? Or do you want to extend nxagent to skip nxclient handling if nxclient cannot be found?
Please note that Mike#1 is already working on replacing the NX_CLIENT stuff completely, see here: #387
BTW: neatx offers a nxdialog tool, that may be used here: https://github.com/wk8/neatx/blob/master/lib/app/nxdialog.py
BTW2, here's the help of the original nxclient, in case you want to extend your code (however, the --parent option is missing here, so it might not be the most current version):
NXCLIENT - Version 3.5.0-7
Usage: nxclient [OPTIONS]
--config FILENAME | DIRECTORY
Run nxclient reading global configuration settings from the file
FILENAME. FILENAME can either be an absolute or relative path. In
the latter case the path is searched for starting from the current
directory. If no FILENAME is found in the current directory then
FILENAME is searched for starting from the user's home directory.
If DIRECTORY is given and a file 'client.cfg' is found in that di-
rectory, then the global configuration settings are read from this
file. The filename does not need to end with the string '.cfg'.
--dialog TYPE [--caption TITLE] [--message MESSAGE] [--local]
[--window ID] [--class {info|warning|error}]
[--allowmultiple]
Show a dialog box. The option must be followed by a 'type' parame-
ter which specifies the type of dialog.
TYPE can be either:
yesno
ok
error
panic
quit
pulldown
The user should specify a caption and a message to be shown. The
option --local can be used to specify the proxy mode.
The 'pulldown' dialog is a special tiny window that is embedded in
the window specified in the --window parameter, to allow the user
to suspend or terminate a session running in seamless mode.
The --class option specifies the class of the message. When no class
is specified the message will be assumed to be of the class 'Info'.
The --allowmultiple option specifies the possibility to launch more
than one dialog with the same message.
--monitor [--owner USERNAME]
Run the "NX Shadow Monitor" application for tracking users when
connected either to the local display or to the master session.
This application allows to send a message to the selected user
and to disconnect him/her.
--help
Display this help and exit.
--printer PRINTER_NAME
Show a dialog box with the list of CUPS printer drivers found on
the server.
It may return:
- Exit code 0 and the name of the driver selected by the user.
The name of the driver is written on the STDIN.
- Exit code 1 in the case of an error. The error message is
printed on the STDERR.
- Exit code 2 and no error message, if the user chose to abort
the operation.
--session FILENAME
Run a session reading the configuration settings from FILENAME.
--plugin FILENAME
Run the client in the special 'plugin' mode, reading the configu-
ration settings from FILENAME.
--version
Output version information and exit.
--wizard
Guide the user through the steps required to configure a session.
--admin
Run the "NX Session Administrator" interface. The interface can be
used to perform administrative tasks on the NX sessions run by the
user, for example viewing the logs, printing the statistics or
closing the session.
--display
Specify the X11 display where the client must connect. The option
is only useful on platforms where the client is using the X-Window
protocol for the display.
All options can be given with a single dash (as in 'nxclient -help').
This is for backward compatibility with older versions. Note that the
single-dash format is deprecated and will be likely removed in future
versions.
sunweaver
mviereck
Ionic
I'm using nxagent as a standalone nested X server. If any applications are running in nxagent, I can not close nxagent desktop window. I get this error message:
As nxclient does not exist, I'm using a workaround. I can specify a fake nxclient with environment variable NX_CLIENT. nxagent sends this cli options:
Switch --parent provides the process id of nxagent. Parsing the output, I can kill nxagent: