I wonder if it would be possible, for future versions of emhttp, to have the shell calls (e.g. for restarting services - samba, nfs, avahi etc) extracted out into separate scripts (maybe held in /usr/local/emhttp/scripts).

 

For a lot of actions emhttp does use the scripts in /etc/rc.d but curiously not in all cases. I have seen in logs that under certain circumstances, when stopping samba, emhttp will call something like "kill smbd" rather than "/etc/rc.d/rc.samba stop"

 

My request is that going forward all emhttp shell calls, for interacting with services, should be replaced with calls to scripts in /usr/local/emhttp/scripts. These scripts should be the only way in which emhttp interacts with other services - instances of killing processes directly should be redirected through a script.

 

The main reason for asking is due to the increased talk lately of the possibility of running an unRAID package on a distro other than Slackware. Whilst any official method of doing so may or may not happen, some users are still happy to experiment on their own. Having the scripts available to be tweaked/replaced to suit the users distro of choice would enable them to tinker away and get emhttp integrated into the distro much more closely.

 

Another reason is that it may well improve consistency and maintainability for the standard unRAID releases. In all cases of interaction with another service scripts would be used (no more kill smbd directly from emhttp), and these scripts would again be tweakable without needing changes made to the emhttp binary.

 

It might mean an additional script being called in the process e.g. instead of emhttp calling "/etc/rc.d/rc.samba start|stop|restart" it would be emhttp calling "/usr/local/emhttp/scripts/samba start|stop|restart" which would in turn call "/etc/rc.d/rc.samba start|stop|restart".

 

Hope that all makes sense!

ooo I'd love this. Yes.

 

Then I could have all sorts of fun with scripting!

Fast loading website as well. Add the convenience of watching them do it.