They can do keylogging, screenshots, and input into other programs’ windows it can use all X server extensions like accelerated graphics. Trusted ones have full access to the entire DISPLAY. These two keys are for untrusted and trusted connections correspondingly. Instead of -X, we may use the -Y key, but it makes sense only if this sshd is suitably configured. Last login: Wed Dec 1 14:32: from home on pts/4 The typical DISPLAY value is localhost:10.0: :~> ssh -X That’s all, of course, if the ssh daemon sshd runs on the remote end and its configuration file, sshd_config, includes the line X11Forwarding yes. So, we’ll ssh -X our_remote_host and, after logging in, we start X11 applications. It's a bit more of a hassle but it works.The best way to start a remote X client is to use ssh with the so-called X Forwardingto direct the X protocol packets over the same connection we use for the commands. I will speak to the admins here about the apparent permissions issue with my user account.ĭo you have any thoughts or suggestions? I'm just glad to have a working version of paraview, regardless of whether or not I can run it through paraFoam or not. When I installed this, I could run Paraview as root! Because it only works as root, and is a different install and is not setup to work with OpenFOAM yet, I can't run the paraFoam command, but at least I have paraview itself working! I've just been running the foamToVTK command and then opening up the files as root to do visualization. After thinking about it awhile I went and downloaded an older version of Paraview (v 3.10). I then deleted the newer libstdc++ version 17 file and relinked it to the original v13 one. When I linked the libstdc++.so.6 to this newer version, Paraview worked! However, it broke other things - the man command no longer worked, and I could no longer open Firefox, for example. 17 that I found online in the aforementioned discussion, though it was not a native RHEL file, it was for Debian instead - the online help indicated this wouldn't be an issue, and I am new to Linux so I took their word for it). I found similar errors searching online (for other programs) and one of the suggestions was to download a newer libstdc++.so and link it (I think the only I have linked here is. I checked into this a bit, and it appears that the libstdc++.so.6 with RHEL6 here only has up through GLIBCXX_3.4.13. home/*username*/OpenFOAM/ThirdParty-2.2.2/platforms/linu圆4Gcc45/paraview-3.12.0/lib/paraview-3.12/paraview: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.14' not found (required by /home/*username*/OpenFOAM/ThirdParty-2.2.2/platforms/linu圆4Gcc45/paraview-3.12.0/lib/paraview-3.12/libvtkPVServerManager.so) This gives me a completely different error: When I login as root, since my bashrc is different, I can't simply enter "paraFoam", so I went to the folder where paraview is located and entered. ![]() (OpenFOAM is installed under my user account). However, logging in as root did not fix my Paraview issue. I'll have to speak to the admins here about that. I think this error is related to my user permissions, because if I login as root I can run gedit just fine. Yes, echo $DISPLAY shows :0.0, and trying to run gedit also gives an error. ![]() Paraview: cannot connect to X server :0.0 - CFD Online Discussion Forums
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |