Hello followers,
at first I have to thanks to all of you which have joined the guardian 2.0 testing team. I've got a lot of positive feedback but also has been noticed about several tiny issues.
I've uploaded an updated test version to http://people.ipfire.org/~stevee/guardian-2.0/.
The installation / update works in the same way as described in the planet post: http://planet.ipfire.org/post/introducing-guardian-2-0-for-ipfire
IMPORTANT: Please create a backup of your files stored in "/var/ipfire/guardian/", otherwise the will be overwritten by the update!
Changelog:
* Matthias Fischer detected some small problems in the "guardian.cgi" and provided some patches for them. http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=19d6abcce57... http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=0a6c3cb8964... http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=82208c83c70...
* Blago Culjak informed me about problems on starting guardian and displaying it's status in the web interface. This behaviour only happens when the legacy version of guardian has been un-installed and not just replaced by the guardian. In the updated version contains the required file which is used by various IPFire scripts to detect if an addon is installed or not.
* The CLI switch "-d" called "debug mode" has been replaced by "-f" to launch guardian and run it in the foreground. http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=a58bd674863...
* Some new code has been added to prevent from starting multiple instances of guardian. http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=9d44c0d9952...
Best regards,
-Stefan