How to remotely invoke an xterm on a SUSE Linux Enterprise Server 11

linux-networkingpermissionssles11xterm

I need to invoke an xterm on a SLES 11 machine (machine A) from another SLES 11 machine (machine B). Currently it doesn't work. So I decided to test some stuff.

On machine A the following works: DISPLAY=:0.0 xterm
However this doesn't: DISPLAY=localhost:0.0 xterm

I'm working on the assumption that if the latter doesn't work then a remote connection won't either.

To me it looks like a permissions issue.

Any help will be greatly appreciated.

Thanks!

Best Answer

Are you sure that the X server on machine B is configured to accept the connection from machine A ? ("xhost +" and firewall off)

btw on my machine with default settings, therer is no "localhost" keyword, just the 1st line just like your mentioned it.

Related Solutions

Linux – Ubuntu file permissions

This isn't a permissions problem. The two clues are:

rm: cannot remove 'admin.php' : Read-only file system
everything was working until yesterday afternoon. At that point a coworker took out the SAN that the virtual machine file was on, and the web server had a less than graceful shutdown.

Somehow the filesystem containing /var/www dropped to "read only" probably when the SAN went away. The output of the mount command should identify this filesystem with a (ro) flag at the end.

The fix is to figure out why it happened, make sure it's corrected, and remount the filesystem rw with this command:

mount -oremount,rw $filesystem

Linux – Samba, Apache and SVN. Getting the permissions right

Have the files and directories owned by a group, which Apache runs as. Make the directories SGID.

chgrp -R group1 /path/to/htdocs
find  /path/to/htdocs -type d -exec chmod 2775 {} \;

Specify this group under the SAMBA share, which can be done with force group=group1.

Make the user you authenticate to SAMBA with a member of this group. Specify this user within valid users and write list within your share in SAMBA. This should also allow you commit to SVN.

Also, specify create mask=0664 and directory mask=2775 within smb.conf, which will set the appropriate permissions upon creation. If the files are owned by the same user as Apache, you can set the final bit to 0 on both settings.

If everything is applied consistently, you should be able to perform all desired actions without negatively impacting any functionality.

Best Answer

Related Solutions

Linux – Ubuntu file permissions

Linux – Samba, Apache and SVN. Getting the permissions right

Related Topic