I'm only now beginning to dabble with running scripts, such as for fan control, and I'm curious as to whether there is a "standard" of where to place these custom scripts on the unRAID flash drive.

 

Is there a "best practice" for placing these scripts?

 

TIA!

These days I duplicate the standard linux tree in boot as

 

/boot/local/bin

/boot/local/lib

/boot/local/lib/packages

/boot/local/var

/boot/local/var/log

/boot/local/var/log/preclear

/boot/local/var/tmp

/boot/local/etc

/boot/local/etc/profile.d

/boot/local/etc/rc.d

/boot/local/etc/rc.d/init.d

/boot/local/etc/ssh

/boot/local/etc/squid

 

I had a suggestion early on when using unraid to use /boot/custom

I switched to /boot/local since I work on many systems and many facilities.

 

I got into the habit of building the local tree on every facility that required storage for that facility.

It made it easy to manage.

 

I also throw stuff in

/boot/bin when I need to do things that require a full path and I feel too lazy to type.

 

Here's something we started working with years ago. I just use local instead of custom.

http://lime-technology.com/wiki/index.php/Third_Party_Boot_Flash_Plugin_Architecture

 

At work it made it easier when I had to compile a special version of an application for a facility.

i.E. if a facilty required it's own local version of an app I could do

 

make PREFIX=/facility/local install

and it would build the tree as I needed.

Perfect!

 

Just what I was looking for.

Let me add, When I had a cache drive.

 

I put the local tree there as /mnt/cache/.local

then made a symlink on /mnt to

 

cd /mnt && ln -s cache/.local local

 

I started migrating stuff off /boot because the flash started to get errors.

 

I no longer have a cache drive, so I'm back to using /boot or some other filesystem on /mnt if it gets to be too much.

 

Using the symlink approach it could be anywhere you want.

i.e. disk1, some other filesystem, etc, etc.

 

I did not use /usr/local because it's on the ram drive.

I had thought about rsyncing /usr/local to some static area upon boot up.. then using a mount -o bind to remount that tree on /usr/local but it just wasn't needed at that time.

 

so currently my additional facility scripts live on /boot/local.