That depends. At least two alternatives exist depending on the number of
user accounts on the system and who is to have access. If access is to be
system-wide, /usr/local/bin is the place for these scripts. If a single
user or group of users is to have access, then /home/user/bin/ is proper.
Those two statements do not take into account version control. If you
were using rcs I know very very old, you might have co put the checked out
scripts into /usr/local/bin/ by default. Version control is really smart.
On Tue, 6 Mar 2007, José Pablo Fernández wrote:
Hello,
we are creating lot's of little scripts on our servers, some in bash, some in
python and other languages may be picked as well. Currently we have a mess,
scripts all
over... /bin, /usr/bin, /usr/sbin, /usr/local/bin, /usr/local/sbin, /root/bin
and even other weird locations (/usr/src/...) depending on who wrote the
script.
I want to standardize on one and only one location for these scripts. It'll be
versioned and it'll be backed up. Any recommendation on where to put these
scripts? Any best or common practice?
Thank you.
--
José Pablo Fernández
[EMAIL PROTECTED]
