DansGuardian Documentation Wiki

You are here: Main Index » faq


|

Wiki Information

Differences

This shows you the differences between the selected revision and the current version of the page.

faq 2010/05/25 21:55 faq 2010/10/22 16:50 current
Line 683: Line 683:
then refuse to start up, even if 'clamav' is not being used and so is not configured in dansguardian.conf.  Executables //without// the old 'clamav' build option will not experience this problem.) then refuse to start up, even if 'clamav' is not being used and so is not configured in dansguardian.conf.  Executables //without// the old 'clamav' build option will not experience this problem.)
-**//Installation#22b. On my system the 'clamdscan' option in dansguardian.conf says //!!Not Compiled!!//, but the 'clamav' option is present. Can I use the 'clamav' option instead? If not, what should I do?//** \\ The 'clamav' option is not exactly the same, may not work at all with recent releases of ClamAV, unneccessarily introduces an overly tight version dependency, can be difficult to install and maintain, and for all these reasons is not recommended.+**//Installation#22b. On my system the 'clamdscan' option in dansguardian.conf says //!!Not Compiled!!//, but the 'clamav' option is present. Can I use the 'clamav' option instead? If not, what should I do?//** \\ The 'clamav' option is not exactly the same, probably will not work at all with more recent releases of ClamAV, unneccessarily introduces an overly tight version dependency, can be difficult to install and maintain, and for all these reasons is not recommended.
Instead, do one or more of the following: Instead, do one or more of the following:
Line 934: Line 934:
**//Usage#12b. Should I treat adjustments I have to make to the DansGuardian configuration as "bugs"?//** \\ Not usually. The DansGuardian "default" configuration is __not__ a fixed canned configuration (it's more of a "starting point"). Some tweaking of the DansGuardian "default" configuration to better match your local usage patterns and policies is expected. **//Usage#12b. Should I treat adjustments I have to make to the DansGuardian configuration as "bugs"?//** \\ Not usually. The DansGuardian "default" configuration is __not__ a fixed canned configuration (it's more of a "starting point"). Some tweaking of the DansGuardian "default" configuration to better match your local usage patterns and policies is expected.
-**//Usage#13. DansGuardian doesn't work the way I want it to on my IPCop system.//** \\ Although the Cop+ that runs on the IPCop distribution is derived from DansGuardian+**//Usage#13. DansGuardian doesn't work the way I want it to on my IPCop system.//** \\ The Cop+ Web interface that controls DansGuardian gives you limited ability to edit Dansguardian Configuration files. The configuration files are all in /etc/dansguardian/ and subdirectories. You can edit the configuration files directly with vi from the command line or using WinSCP from a windows workstation. **Care Must be taken to keep the files owned by "nobody" or the Web interface will not be able to edit them anymore.** 
-the configuration tools are specific to Cop+ and are quite different from those used by vanilla DansGuardian.  +For help with Cop+, try [[http://home.earthlink.net/~copplus/dghelp.html]].
-For help with Cop+, try [[http://copfilter.endlich-mail.de/]].+
**//Usage#14. DansGuardian doesn't work the way I want it to on my SmoothWall Express or SmoothWall system.//** \\ For help with the homebrew DansGuardian package for SmoothWall Express, **//Usage#14. DansGuardian doesn't work the way I want it to on my SmoothWall Express or SmoothWall system.//** \\ For help with the homebrew DansGuardian package for SmoothWall Express,