Frame Lock Configuration
Quadro Sync
DU-06574-001_v01
| 16
LINUX DRIVER CONFIGURATION
The NVIDIA Control Panel on Linux allows one node to manage all nodes in the cluster.
To work properly the security settings need to be set properly or client nodes may not
appear.
Set Driver Security to Allow Remote Management
Any X Server can be added to the frame lock group, provided that
1.
The system supporting the X Server is configured to support frame lock and is
connected via RJ45 cable to the other systems in the frame lock group.
2.
The system driving nvidia-settings can communicate with the X server that is to be
included for frame lock. This means that either the server must be listening over TCP
and the system's firewall is permissive enough to allow remote X11 display
connections, or that you've configured an alternative mechanism such as ssh(1)
forwarding between the machines.
For the case of listening over TCP, verify that the "-nolisten tcp" commandline option
was not used when starting the X server. You can find the X server commandline
with a command such as
% ps ax | grep X
If "-nolisten tcp" is on the X server commandline, consult your Linux distribution
documentation for details on how to properly remove this option.
For example, distributions configured to use the GDM login manager may need to
set "DisallowTCP=false" in the GDM configuration file (e.g., /etc/gdm/custom.conf,
/etc/X11/gdm/gdm.conf, or /etc/gdb/gdb.conf; the exact configuration file name and
path varies by the distribution). Or, distributions configured to use the KDM login
manager may have the line
ServerArgsLocal=-nolisten tcp
in their kdm file (e.g., /etc/kde3/kdm/kdmrc). This line can be commented out by
prepending with "#".
