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
I have this issue:
I use a pipeline local filesystem to link the storage with the dashboard. In the dashboard, the services are run with the archivematica user.
For some reasons, when the storage sends files to the dashboard, it uses another user to ssh in the dashboard, called archivematica-storage.
Both archivematica and archivematica-storage are in the group archivematica, so the folders created by the storage on the dashboard look like this:
drwxrw-rw-. 1 archivematica-storage archivematica 0 Aug 9 15:26 archive
As you can see, groups can't execute the folder (so they can't see what's in). So, when the dashboard wants to use it, via the archivematica user, it doesn't work.
For me, it makes sense that the created folders have the execute permission as long as they already have read and write, thus I suggest the following PR: #227
The text was updated successfully, but these errors were encountered:
I have this issue:
I use a pipeline local filesystem to link the storage with the dashboard. In the dashboard, the services are run with the
archivematica
user.For some reasons, when the storage sends files to the dashboard, it uses another user to ssh in the dashboard, called
archivematica-storage
.Both
archivematica
andarchivematica-storage
are in the grouparchivematica
, so the folders created by the storage on the dashboard look like this:As you can see, groups can't execute the folder (so they can't see what's in). So, when the dashboard wants to use it, via the
archivematica
user, it doesn't work.For me, it makes sense that the created folders have the execute permission as long as they already have read and write, thus I suggest the following PR: #227
The text was updated successfully, but these errors were encountered: