Applies to: All versions of Zorp

Issue

Most configuration changes take effect after reloading Zorp, except the ones concerning virus filtering.

Answer

Most parameters of the proxies, listeners, and other Zorp objects are implemented in Python. Zorp reads all these parameters when it is reloaded, so any changes related to Zorp take effect immediately after a reload. The followings are exceptions to this rule:

• Virus filtering modules (e.g., vbuster): These modules do not re-initialize their parameters automatically, therefore Zorp or ZCV must be restarted for such changes to take effect. Parameters that require restarts include the Archive max size (archive_max_size) and Archive max ratio (archive_max_ratio) parameters of the vbuster module and the vbuster proxy.

• Instance parameters of Zorp: These parameters (available by clicking the Parameters button on the Instances tab of the Zorp ZMC component) are loaded only at Zorp startup, so a restart is needed when they are modified.

Additional information / References

For further information on the parameters of the virus filtering modules, see section ZCV modules in the Zorp Administrator's Guide available at
http://www.balabit.com/dl/html/zorp-admin-guide.html/bk01-toc.html#zcv_module_instances
For further information on instance parameters, see section Creating and configuring instances in the Zorp Administrator's Guide available at
http://www.balabit.com/dl/html/zorp-admin-guide.html/bk01-toc.html#zorp_configuring_instances