This appears to have been caused by a user error. I am closing the bug
report, and if this is a problem in the latest version of Ubuntu, please
change the status in the yellow line above back to "New". Thank you and
please continue to report bugs you find.
** Changed in: sshfs-fuse (Ubuntu)
Well, there is a difference.
In short, the disk file system only knows about the uid and gid numbers.
The operating system then matches these values with user and group
names, based on its user database. As long as you are only working
against a local hard drive this is seldom something which you
Not apart from that names are strings and id's are integer values :)
Which basically refer to the same thing, the representation just is
different?
On Thu, Jul 30, 2009 at 11:39 PM, Andreas Olsson wrote:
> @T-Co:
>
> Just to be on the clear; are you familiar with the difference between
> user name
@T-Co:
Just to be on the clear; are you familiar with the difference between
user names and group names compared to uid:s and gid:s?
--
sshfs using wrong user/group
https://bugs.launchpad.net/bugs/315034
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Sorry for the late answer.
I think I misunderstood the problem I was having.
Apparently when mounting with a user that does not exist in a system
fuse would create a virtual user for it instead?
So if sshfs notau...@host:/path/to/ ./path/
The filesystem would show the user/group to be 1001/1001
We'd like to figure out what's causing this bug for you, but we haven't
heard back from you in a while. Could you please provide the requested
information? Thanks!
--
sshfs using wrong user/group
https://bugs.launchpad.net/bugs/315034
You received this bug notification because you are a member of
@T-Co: Could you please provide the different user- and group names, as
well as uid and gid on the machines involved?
** Changed in: sshfs-fuse (Ubuntu)
Status: New => Incomplete
--
sshfs using wrong user/group
https://bugs.launchpad.net/bugs/315034
You received this bug notification beca
This behavior can be influenced by using the "-o idmap=user" option with
sshfs. When using this option, the the owner is always set if possible
to the local user's uid.
Might this also solve the original bug reporter's problem?
--
sshfs using wrong user/group
https://bugs.launchpad.net/bugs/315
I have noticed that if I try to mount an ssh path which is being served
on the local machine (i.e. the command is "sshfs anotheru...@localhost:
local_mountpoint"), then provided that "anotheruser" exists on your
machine (should be the case), the ownership of the files is assigned to
'anotheruser',
