The support settings file cannot be deleted, but is it readable and writable? What do I need to do if I need support?

[1247862674]

[trapexit]

I'm sorry but I don't understand what you're asking.

[1247862674]

Is there any policy that can control files that cannot be deleted but can be read and written?

[1247862674]

I now have a data source and I want to make it readable and writable, but no one else can delete the file

[trapexit]

Policies select files to act on. They don't control what can be read, written, or unlinked.

You need to be more specific about what you want to happen. What about creates?

[1247862674]

For example, I now mergefs A:B C. I want A to be readable and writable, but all files in A cannot be deleted.

[trapexit]

Yes, I understand that but what about create? These concepts are orthogonal. You can read anything readable and has nothing to do with unlinking or creating or writing. Why not just use ACLS?

[1247862674]

it can create

[trapexit]

Why don't you just use ACLs?

[1247862674]

Are there any specific examples or documentation?

[1247862674]

To be honest, I don’t know how to use ACLS.

[trapexit]

You aren't really explaining the full requirement so it is not possible for me to help. I would suggest just reading about unix and posix permissions and acls. It is fundamental to filesystems. If you don't want people to delete a file just don't give them permissions to it.