Best practices

Dear all,
Kinda lame question but i'd like to hear your experiences and advice.

Question in short
-----------------
What permission should a mount point "ideally" have - i think it's root.

Ex:- /usr/app/ i'd set the app to be owned by root and within /usr/app i would create another directory for the specific purpose and give it permissions accordingly.

I think i can use the same analogy for BD2 and Oracle mount points.

cheers folks
Tim

That's actually a few questions.

The mountpoint itself, before its mounted, what permissions should it have? Probably root, and read-only to everything else. You don't want the mountpoint to be used when not mounted by accident, that could fill up your root filesystem.

When it's mounted, what permissions should it have? Well, a mountpoint is in effect just a folder like any other. It may have to have certain permissions; if you put a mountpoint on /var/cache/squid, it ought to belong to user squid, group squid, and be writable by squid, or it won't be a whole lot of use.

Given that in some ways it's easier to rearrange filesystems than files -- you can plant them literally wherever you want -- it may be best to mould filesystems to the layout you want rather than vice versa.

1 Like