You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sorry if it's out of arx usage you defined ... in this case trash it
I have try to access files in arx archive wit another user (same secondary group as creator)
... after a mount another user (even sharing same group) don't see the mount point, in other similar case, in Linux, we solve it for ex by adding optional allow_other to fuse mount ... BUT I don't know if it's possible to change fuse options ??? (ex mount using option file to add some specific mount option ... or any other solutions
In same target, I try to access using another user (just add r READ to archive)
arx list work as well
arx extract work as w ell but change the original owner/group if different ... I have not yet evaluate the impact for current usage ...
ARX version used is just before adding recursive option and mount daemon ... I will check with last github commit ...
Philippe.
The text was updated successfully, but these errors were encountered:
Hi,
Sorry if it's out of arx usage you defined ... in this case trash it
I have try to access files in arx archive wit another user (same secondary group as creator)
... after a mount another user (even sharing same group) don't see the mount point, in other similar case, in Linux, we solve it for ex by adding optional allow_other to fuse mount ... BUT I don't know if it's possible to change fuse options ??? (ex mount using option file to add some specific mount option ... or any other solutions
In same target, I try to access using another user (just add r READ to archive)
arx list work as well
arx extract work as w ell but change the original owner/group if different ... I have not yet evaluate the impact for current usage ...
ARX version used is just before adding recursive option and mount daemon ... I will check with last github commit ...
Philippe.
The text was updated successfully, but these errors were encountered: