webapps automatic updates

[mvulcan]

I have the following in the #cron settings section of my options.conf file, yet Roundcube auto-updated to 0.8.5 today.
I would like to continue to be notified of an available update through the cron job, but I want to update manually, so I can copy over my plugins, etc.
What am I missing? I thought "webapps_updates=no" would be enough to prevent automatic updates of roundcube.

#Cron settings
cron=yes
cron_frequency=daily
[email protected]
notifications=yes
da_autoupdate=no
updates=no
webapps_updates=no

 

[zEitEr]

If you changed cron section of options.conf you need to run

./build cron

once more time to apply changes.

 

[Greenhost]

If your Roundcube updated that's weird. For do off line automatic update "webapps_updates=no" is enough. May be you don't run "service directadmin restart" after your modify your Corn.

 

[Greenhost]

Sorry I had typo mistake.
For turn off automatic updates"webapps_updates=no" is enough.
May be you don't run

service directadmin restart

after your modify your Corn.

 

[zEitEr]

No need to restart directadmin, but ./build cron is required. This is how the file /etc/cron.daily/custombuild looks with enabled web autoupdates:

#!/bin/sh
cd /usr/local/directadmin/custombuild
./build update >/dev/null 2>&1
AVAIL_UPDATES="`./build versions_nobold | grep -c -e 'update is available.'`"
if [ "${AVAIL_UPDATES}" -gt 0 ]; then
./build versions_nobold | grep 'update is available.' | mail -s "${AVAIL_UPDATES} updates available for `hostname`" [email protected] 
./build update_webapps
fi
exit 0;

And this is how it looks without enabled web-updates:

#!/bin/sh
cd /usr/local/directadmin/custombuild
./build update >/dev/null 2>&1
AVAIL_UPDATES="`./build versions_nobold | grep -c -e 'update is available.'`"
if [ "${AVAIL_UPDATES}" -gt 0 ]; then
 ./build versions_nobold | grep 'update is available.' | mail -s "${AVAIL_UPDATES} updates available for `hostname`" [email protected]
fi
exit 0;

To rewrite the file you need to run suggested above command.

 

[mvulcan]

Thanks. I wasn't aware of needing to run the ./build cron for the changes in the options.conf to take effect.