Its clear to me that the
command will make any file, theoretically, accessible/readable/writeable/executable/ by any user.
But are there instances where, even with a world writable/readable file, we still need to implement CHOWN in order for the file to be used by system processes?
Or can we assume that, as long as permissions are wide open, the chown command has no impact on the access pattern behaviour of a file.
I ask this in relevance to some multithreaded/cluster processes which seem to fail when running as the wrong user due to ENOENT errors which appear to occur on a file which has wide open (777) permissions.