how to run process monitor remotely over putty

1Īnother example of an 64bit ubuntu installation with NVidia drivers and 32bit libraries available:

so lrwxrwxrwx 1 root root 17 aug 19 13 : 48 / usr / lib64 / libGL. 0 lrwxrwxrwx 1 root root 15 aug 19 13 : 48 / usr / lib64 / libGL.

0 lrwxrwxrwx 1 root root 14 jun 6 13 : 40 / usr / lib64 / mesa / libGL. 352.93 lrwxrwxrwx 1 root root 15 aug 19 13 : 33 / usr / lib64 / nvidia / libGL. # first 3 lines are the NVidia lib # second set of 3 lines are the mesa lib # last two lines are the generic symlinks that point towards the NVidia lib - rwxr - xr - x 1 root root 1220472 apr 6 02 : 51 / usr / lib64 / nvidia / libGL. Which mode you decide to use is up to you of course, but if something doesn’t work always try using -X -Y (or -XY) before asking for help. The security extensions are there for good reason, but they can break so many things that some distros (Debian for example) disable them by default, even if you use -X and not -Y. The -Y flag enables trusted X11 forwarding, which does not enable the additional security extensions. The default -X flag enables X11 forwarding, but with extended security restrictions to protect LocalBox from malicious behavior of people on the RemoteBox. Sidenote on ssh -X and -Y: There are two ways of enabling X forwarding with SSH, -X and -Y. Another thing to check is “xhost”, which might also get in the way. Check if the RemoteBox allows X11 Forwarding (/etc/ssh/sshd_config should contain “X11Forwarding yes”), and try both the -X and -Y flag on the ssh command. If you got any errors and no window, most likely something fundamental is broken. If you got a terminal and a clock popping up in separate windows, you have working X11 forwarding over SSH.

How to run process monitor remotely over putty