[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 2 problems using screen with sshfs and symlinks

From: Ken Steen
Subject: Re: 2 problems using screen with sshfs and symlinks
Date: Sun, 10 Aug 2008 21:50:45 -0700
User-agent: Mutt/1.5.17+20080114 (2008-01-14)

On Sun, Aug 10, 2008 at 09:18:21PM -0400, Andy Harrison wrote:
> On Wed, Aug 6, 2008 at 10:44 AM, Ken Steen <address@hidden> wrote:
> > I have a small file manager that uses screen to open programs in new
> > screen windows.  It works correctly except when using screen on a
> > directory mounted with sshfs or when using screen on a directory that is
> > a symbolic link.  If the program is started with 'screen program-name',
> > and the current directory is a symbolic link to another directory
> > opening a new screen window changes the pwd to the directory that is
> > pointed to by the symbolic link instead of the symbolic link directory.
> > If the program is started in the shell without screen and then opens a
> > screen window the pwd is the symbolic link directory.  A similar problem
> > occurs when a directory  is mounted with sshfs.  If the program is
> > started with 'screen program-name' screen will give a permission denied
> > message when trying to open a new screen window.  If the program is
> > started in a shell without screen and trys to open a sshfs mounted
> > directory in a screen window it works correctly.
> >
> > I am not sure what is happening.  I am guessing that the environ
> > variable is not being set correctly.  The screen command is passed with
> > execve() and works correctly except in the previous two examples.  Any
> > ideas into what I am doing wrong would be greatly appreciated.
> >
> Although completely unrelated to screen, I had similar permission
> problems with one of my sshfs mounts.  I finally solved it with the
> following sshfs params:
> sshfs address@hidden:/path /mount/point -o allow_root -o
> idmap=user -o uid=1000 -o gid=1000
> I would suggest trying that, or change allow_root to allow_other, and
> see if that helps.

I had to use the -o allow_other and -o default_permissions with sshfs to
get it to work properly with screen.  The symlink directory problem was
fixed by calling "screen -X setenv PWD /full/path/to/directory"  before
calling screen to open a new window.  I don't know why it is needed only
on symlink directories but it works.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]