On Wednesday 16 July 2008 11:17:04 am J Sloan wrote:
abin is for automatic binaries that will be ran via cron (just separation for me to keep the bin dir less cluttered).
maybe i'll just put all the admin task stuff into sbin and the stuff from abin into bin .. What are your thoughts on that?
Why invent new paths? /usr/local/bin is the customary unix path for local scripts and binaries, and /usr/local/sbin specifically for system level scripts and binaries. Definitely go with the established standards, it makes life more sane.
Joe
Hi Joe, I am going to go with bin / sbin (bin for the ones my cron jobs use and sbin for the system admin scripts that I previously had in bin).. I am just having a hard time trying to decide to put some other things that I need to push out to all these boxes. Here's an example of some stuff that would be there: bin sbin crontab.dist (a crontab that I will have append to all machines with stuff I want) distlist (the list of what should be distributed) sahead (system admin header (has a ton of commonly used variables) saenv.setup (setting up the sys admin environment) sudoers (common sudoers across all servers) I know to use: /usr/local/bin and /usr/local/sbin But I can't put the others on the root of /usr/local .. where in /usr/local should I then put them? Thanks -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org