If I understand your explanation correctly, you have to restart apache with a one minute cronjob. So your changes get applied after about one minute. Thats the same time that the normal ispconfig system takes to apply the changes, so I dont see the real benefit in the time to get changes applied.
If you want to get changes applied faster, then the approach that was used in ispconfig 2 might be a good choice.
1) Comment out the server.sh root cronjob.
2) create a bash script, e.g. /usr/local/bin/ispconfig_server.sh with the following content:
echo "ERROR: $1"
if [ ! -z "$MYUID" ];
if [ $MYUID != 0 ];
error "You need root privileges to run this script! / Vous devez avoir les privileges root pour executer ce script!";
while (true) do
if [ -f /usr/local/ispconfig/interface/web/temp/.run ]; then
rm -f /usr/local/ispconfig/interface/web/temp/.run
/usr/bin/php -q /usr/local/ispconfig/server/server.php
rm -f /usr/local/ispconfig/server/temp/.run2
Start this shell script in the background, it will run forever until you kill it or you reboot the server. It has a very low resource usage. The script checks every 10 seconds if a file /usr/local/ispconfig/interface/web/temp/.run exists and if that file exists it will start the ispconfig update process. You can even reduce the time to less then 10 seconds if nescessary.
So if you want to start an update from the ispconfig interface then, you just execute this php command:
This variant is only usable on single server systems, thats why we dont use it in ispconfig 3.