![]() ![]() ![]() Either that, or use a totally separate hierarchy rooted in, e.g., /opt or /sw or somesuch place (not used by base system or package managers). If you're the only user of the system, then just install under $HOME, for example in a $HOME/local hierarchy. Installing scripts in /usr/local/bin would only make it more awkward to back up and to maintain your personal files.Īlso, the /usr/local hierarchy may be used when installing external software from locally compiled source code, which means that software installed in that way have a potential risk of overwriting your personal scripts and/or accidentally pick them up as system-provided tools (depending on how you name your scripts).Īlso note that package managers on some BSD systems install packages under /usr/local (OpenBSD and macOS, for example), which is another reason to leave that particular file hierarchy alone for personal scripts. The DomainAdministrator is the owner of the root shared folder. at 22:43 On the File Server every time that I need to assign a new user to one of the department folders, if new files or folders have been created under the ownership of a regular user, the administrator would not able to assign new security to these files or folders. As the user root I create a new file into this folder, and the default ownership will be root:root, but I need that this new file inherit automatically (without chown or other) the john:john. Since you are the only user on the system, and therefore the only user of the scripts that you write, I don't really see much point in installing personal scripts in /usr/local/bin. How I can make sure that all new files created in a folder (by any user) inherit the folder ownership, for example: /var/www/john -> owned by john:john. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |