i did use this reference a lot while working on the code, it is a good reference.
http://felipeferreira.net/?p=240in this reference, you will notice the squidGuard program was compiled first before BerkeleyDB.
also, the notations of somebody mentioning to change the redirect_program and redirect_children wording inside the
the squid.conf to url_rewrite_program and url_rewrite_children.
see squid.org for details on the wording
also notice that i do not let squidGuard install the program with (make install) into my system directories.
but i do let the BerkeleyDB install to my system directories.
also pay attention when installing BerkeleyDB and install it only once, if you try to install it a second time
you will have run some programs to clear out some stuff that was created during the first compile.
the info on that is listed in the referenced linked website in this post above
some other notes:
as far as i can tell, if you have db files created in the /var/lib/squidguard/db folders and you do not have BerkeleyDB support,
then your squidguard program is likely not to work. that has been what i have seen and i again am only a beginer with using squidGuard.
How i got my squidguard program to running was by removing the db files or possibly just renaming them, which i have not tried.
More that likely though you are going to want to start making use of the blacklists db files that can be downloaded from the internet as so will i.
i did see on this form where some people where running a command "config show squidGuard" to get some feed back.
i think running the command "squidGuard -d" may possibly be your best form to check to see if the squidGuard program is running.
a very likely better form of a test, could actually be a routine to run from a cron that creates a report from trying to access either one or mulitple
webpages and the webpage is redirected to a file and that file is read in an automated way, then analyzed on the results that some get your
in a way that the squidguard routine seem broken.
Many people on this forum also suggest that you uninstall the gcc compiler after your done using it.
that can be done with a "yum -y remove gcc" then "signal-event post-upgrade;signal-event reboot" giving a immediate reboot of the sme server.
you may want to remove the directory /temp or rename it, but for me, i am going to leave those files on my server for a while