1/12/2024 0 Comments R xquartzIf you would not like to change defaults by terminal commands, use XtraFinder. Rprofile, you should make dot-files invisible again by typing in the terminal: defaults write AppleShowAllFiles FALSE Do not edit (or even try to open) the dot-files other than. To show them, type in the terminal: defaults write AppleShowAllFiles TRUE On Mac, dot-files are treated as hidden files and not shown in Finder. On Windows (7 or later), it should be C:/Users/YOUR_USER_NAME/ (sorry, but I’m not sure about Windows). On Mac, the home directory is normally /Users/YOUR_USER_NAME/. You should save it in you home directory. Rprofile without an extension (not “.Rprofile.txt” or “.Rprofile.R”). Rprofile every time you start a new R session. R automatically reads the settings written in. Dot-files, files beginning with “.” (full stop), are used to keep the settings of software packages. In that case, we can save the options in. It continues to increment over time, judging by a sequence of these reports overnight.However, if you always use the same options, you wouldn’t like to type the same commands every time. In this report, everything is the same between status reports except the port number used by connection #7 which I believe is the Linux client - the only one still maintaining a display connection. With "LogLevel DEBUG3" set on the remote machine (sshd server), and no change made in the client connections by me, /var/log/auth.log shows one slight change in connection status reports overnight, which is the port number used by the one successful ssh session from the Linux machine (I think), connection #7 below: When logging in from a Linux 11.10 laptop to the same remote host over the same network and switch, this problem does not occur - an xterm can be invoked successfully hours later from the same ssh login shell while the same experiment from the Mac fails (tested this morning to be sure), so it would appear to be a Mac-specific issue. Nothing obvious has changed in either client or server configuration although I have tried changing a few options to try to debug this, like setting sshd_config's TCPKeepAlive to no, and setting "host +localhost" (you can tell I've been Googling). I am by no means an X11 or SSH expert but have good UNIX/Linux experience. Until recently (a few days ago) this setup worked perfectly so I am mystified as to where to look next. The systems are connected on an Ethernet LAN with a single switch between them. Particulars: OpenSSH sshd server running on Ubuntu 8.04, display forwarded to a Mac running Lion (10.7.2) with the default Apple X server. If I ssh -X to the server again, starting a new shell and getting assigned a new display (localhost:11.0), the same process repeats: the X11 applications started early on run just fine for as long as I keep them open (days), but after a few hours I cannot start any new ones from that shell. Sshd: channel 8: open failed: administratively prohibited: open failed I turned on verbose logging in sshd_config and I see this in the /var/log/auth.log file in response to the failed xterm startup attempt: Xterm Xt error: Can't open display: localhost:10.0īut the X11 application I started right when I logged in is still running along just fine, using that exact same display (localhost:10.0), just that it was started earlier. When attempting to start xterm, for example, I get the usual message about a bad DISPLAY setting, such as: What has recently started happening is that additional invocations of X11 applications from that same shell, after a while (on the order of hours), are unable to start because the forwarded display is being blocked (I presume). I have no trouble using ssh -X to log in to the remote machine and starting an X11-based application from that shell. I have a new and vexing problem with ssh forwarding my X11 connection when logging in from a Mac (10.7.2) to Linux (Ubuntu 8.04).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |