- Release candidate 0.10.0 - It's Froxlor, but with API :)
-
Release candidate 0.10.0 - It's Froxlor, but with API :)
With the following file: /etc/cron.d/froxlor # automatically generated cron-configuration by froxlor # do not manually edit this file as it will be re-generated periodically. PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin # */5 * * * * root /usr/bin/nice -n 5 /usr/bin/php7.2 -q /var/www/froxlor//scripts/froxlor_master_cronjob.php --tasks 1> /dev/null 0 0 * * * root /usr/bin/nice -n 5 /usr/bin/php7.2 -q /var/www/froxlor//scripts/froxlor_master_cronjob.php --traffic 1> /dev/null 5 0 * * * root /usr/bin/nice -n 5 /usr/bin/php7.2 -q /var/www/froxlor//scripts/froxlor_master_cronjob.php --usage_report 1> /dev/null 0 */6 * * * root /usr/bin/nice -n 5 /usr/bin/php7.2 -q /var/www/froxlor//scripts/froxlor_master_cronjob.php --mailboxsize 1> /dev/null */5 * * * * root /usr/bin/nice -n 5 /usr/bin/php7.2 -q /var/www/froxlor//scripts/froxlor_master_cronjob.php --letsencrypt 1> /dev/null 10 0 * * * root /usr/bin/nice -n 5 /usr/bin/php7.2 -q /var/www/froxlor//scripts/froxlor_master_cronjob.php --backup 1> /dev/null
-
Release candidate 0.10.0 - It's Froxlor, but with API :)
I raised froxlor to 0.10 before the Debian update. Renamed the old folder and restored the config file. Since then I haven't changed anything in the settings. After the Debian Update I have removed old cipher and noticed that the cron doesn't work anymore. When I make the file "froxlor_master_cronjob.php" executable it runs as usual again. I had installed Froxlor before as a package, that was uninstalled during the update of Debian.
- Release candidate 0.10.0 - It's Froxlor, but with API :)
- Release candidate 0.10.0 - It's Froxlor, but with API :)
- Release candidate 0.10.0 - It's Froxlor, but with API :)
- Release candidate 0.10.0 - It's Froxlor, but with API :)
- Release candidate 0.10.0 - It's Froxlor, but with API :)
- Release candidate 0.10.0 - It's Froxlor, but with API :)
- Release candidate 0.10.0 - It's Froxlor, but with API :)
-
Release candidate 0.10.0 - It's Froxlor, but with API :)
I just upgraded my main system to buster and an error occurred with "bind". In the "named.conf.local" the include of Froxlor was included twice. // // Do any local configuration here // // Consider adding the 1918 zones here, if they are not used in your // organization //include "/etc/bind/zones.rfc1918"; include "/etc/bind/froxlor_bind.conf"; include "/etc/bind/froxlor_bind.conf";
- Release candidate 0.10.0 - It's Froxlor, but with API :)
- Release candidate 0.10.0 - It's Froxlor, but with API :)
Tealk
Members
-
Joined
-
Last visited