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'm writing to an external exfat formatted drive on linux. This is a root mounted drive with no permissions system, so everyfile is owned by root, with full rw access to all users. So I have read, write access to the file.
write-file-atomic is trying to set the ownership of the file.
chown: changing ownership of '/media/sandisk/config.json': Operation not permitted
I know that you advice to pass false to the permission option, however this is a 2nd level dependancy, so I'm not actually using this library directly. I'm using
json-future, which has a dependancy for write-json-file, which is using write-file-atomic.
I think if write-file-atomic is just going to set the uid to the existing user, it could catch this error and squash it, as chown failing has no impact.
The text was updated successfully, but these errors were encountered:
paulhayes
changed the title
[BUG] <title>
Writing to exfat drive on linux
Feb 3, 2020
paulhayes
changed the title
Writing to exfat drive on linux
[Bug] Writing to exfat drive on linux
Feb 3, 2020
paulhayes
added a commit
to paulhayes/write-json-file
that referenced
this issue
Feb 3, 2020
Due to a bug in write-file-atomic saving to a permissionless filesystem ( eg fat32, exfat ) in linux without explicitly setting chown to false, causes the write to fail. As noted here: npm/write-file-atomic#58
By simply setting chown argument explicitly, this error will not occur.
What / Why
I'm writing to an external exfat formatted drive on linux. This is a root mounted drive with no permissions system, so everyfile is owned by root, with full rw access to all users. So I have read, write access to the file.
write-file-atomic is trying to set the ownership of the file.
chown: changing ownership of '/media/sandisk/config.json': Operation not permitted
I know that you advice to pass false to the permission option, however this is a 2nd level dependancy, so I'm not actually using this library directly. I'm using
json-future, which has a dependancy for write-json-file, which is using write-file-atomic.
I think if write-file-atomic is just going to set the uid to the existing user, it could catch this error and squash it, as chown failing has no impact.
The text was updated successfully, but these errors were encountered: