Hi Mike,

Thanks for the clarification about the user_allow_other flag!

As far as I can see, the problem was actually that I was using syncthing to
synchronize the directories that were a problem.  This didn't cause trouble
on my laptop, but perhaps interacts poorly with NFS.

David

On Sat, Nov 1, 2014 at 8:07 AM, Mike Shal <[email protected]> wrote:

> The user_allow_other flag is only needed if you want to use full
> file-system wide dependencies, or run processes with the ^c flag to force
> running in a chroot. Otherwise you don't need to set it. If that is the
> problem, you should see something like this:
>
>  --- Run t2000-basic-tupfile.sh ---
> .tup repository initialized.
> [ tup ] [0.000s] Scanning filesystem...
> [ tup ] [0.001s] Reading in new environment variables...
> [ tup ] [0.001s] Parsing Tupfiles...
> fusermount: option allow_other only allowed if 'user_allow_other' is set
> in /etc/fuse.conf
>
> Since yours is failing with a different permission error, I'd guess
> something else is the problem. Is there a non-NFS mountpoint that you can
> try to use instead? Does that fail as well?
>
> -Mike
>
> On Fri, Oct 31, 2014 at 1:47 PM, David Roundy <
> [email protected]> wrote:
>
>> Hmmm.  That sounds like it's undermining a pretty important security
>> setting, and I'm hesitant to do that on a multiuser machine.
>>
>> David
>>
>> On Fri, Oct 31, 2014 at 10:19 AM, Freddie Chopin <
>> [email protected]> wrote:
>>
>>>  Hmm... I won't help you much with the NFS issue, but for a "normal"
>>> workflow I had to enable option "user_allow_other" in /etc/fuse.conf - it
>>> was enough to uncomment it. Tup worked without that too, but using ^c^ flag
>>> caused an error.
>>>
>>>
>>> Regards,
>>> FCh
>>>
>>> --
>>> --
>>> tup-users mailing list
>>> email: [email protected]
>>> unsubscribe: [email protected]
>>> options: http://groups.google.com/group/tup-users?hl=en
>>> --- You received this message because you are subscribed to a topic in
>>> the Google Groups "tup-users" group.
>>> To unsubscribe from this topic, visit https://groups.google.com/d/
>>> topic/tup-users/ApM3nxONDkg/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> [email protected].
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> David Roundy
>>
>> --
>> --
>> tup-users mailing list
>> email: [email protected]
>> unsubscribe: [email protected]
>> options: http://groups.google.com/group/tup-users?hl=en
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "tup-users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>  --
> --
> tup-users mailing list
> email: [email protected]
> unsubscribe: [email protected]
> options: http://groups.google.com/group/tup-users?hl=en
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "tup-users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/tup-users/ApM3nxONDkg/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
> For more options, visit https://groups.google.com/d/optout.
>



-- 
David Roundy

-- 
-- 
tup-users mailing list
email: [email protected]
unsubscribe: [email protected]
options: http://groups.google.com/group/tup-users?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"tup-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to