Dave freecycle_berkeley@niwas.net [unison-users]
2018-11-25 06:39:39 UTC
Sat Nov 24, 2018 3:12 am (PST) . Posted by: worley397
successfully run things in two ways: One way is as a non-root user,
where the user can read/write everything it needs to read/write, and the
program does not pay attention to file ownership. The second way is as
root, in which case the program can do all sorts of manipulation.
In regard to Unison, if you want to run it as a non-root user, then you
have to avoid the -user and -group options, so Unison won't try to
change the ownership of things it creates. Then, everything it creates
will be owned by the user it is running under, rather than the owner of
the file/directory it copies.
One useful thing is to run the program "id". It tells the user and
group your shell is running under, as well as the "additional groups" of
the process. That's not complicated, but it's useful to remind yourself
of how you are running things.
Dale
Thanks, Dale. It turns out that the filesystem that I am trying to sync with, a FUSE-fs - keybase's kbfs - that doesn't allow root access. It is mounted without the "allow_root" option. So I've got unison working now, by using the -group and -perms options. My next step is to run unison via inconrd, but systemctl runs that as root, so now I have to figure out if there's a way to run that under my own username. I know it's OT for this list, but if anyone has input, I'd certainly appreciate it!
Dave.
Well, part of my question is I don't understand linux
permissions/ownership very well. I would presume my user:group is
me:me, though I am also a member of various other groups, like
debian-tor for example.
The general rule in Unix (and I think Unison follows it) is that you canpermissions/ownership very well. I would presume my user:group is
me:me, though I am also a member of various other groups, like
debian-tor for example.
successfully run things in two ways: One way is as a non-root user,
where the user can read/write everything it needs to read/write, and the
program does not pay attention to file ownership. The second way is as
root, in which case the program can do all sorts of manipulation.
In regard to Unison, if you want to run it as a non-root user, then you
have to avoid the -user and -group options, so Unison won't try to
change the ownership of things it creates. Then, everything it creates
will be owned by the user it is running under, rather than the owner of
the file/directory it copies.
One useful thing is to run the program "id". It tells the user and
group your shell is running under, as well as the "additional groups" of
the process. That's not complicated, but it's useful to remind yourself
of how you are running things.
Dale
Dave.