With a little bit simplification, the filepermissions look like this:
There are 3 possible relations you can have to a file:
- you are the owning user (u)
- you are in the group (g)
- else, other. (o)
For all of these categories, there is a boolean permission-triple: rwx
so for those files:
the user oracle has rw (read, write)-permissions. Should you use the oracle account? Surely not.
The group oinstall has only read permissions. Well - you might become a member of that group, which would give you read permissions to those files.
For completeness: x means execute-permissions. Here nobody may execute the files, a common
pattern for logfiles.
Everybody else doesn't have any permitssion on that files.
Whatever you mean by weblogic-file - created by weblogic, for weblogic, in some relation to weblogic - that's not a category that is usefull to discuss permission questions. Those files all have permissions set for ugo, and if you are the user, in the group or someone other, you have the permissions which are bound to the file.
The admin could of course change the permissions of the file in the section 'other', and give other people than oracle or those in the oinstall-group read permissions - for example. But that wouldn't apply to everybody else too.
And maybe the file is changed by some process, then the admin repeatedly had to change the permissions.