But the problems aren't really problems, IMO. They could at some point be considered feature requests.
The module has to make some assumptions to put some structure around the relatively amorphous squidguard.conf file. It really makes only one - that you are using the module as your primary management tool. If 5 minutes had been taken to make some changes and see the results in the .conf file the light would have come on. It still may not be a fit, but so what? Log a feature request/suggestion, but don't imply it is broken. I agree that it is not a 100% be-all solution, but it certainly isn't broken, especially within the bounds of the issues raised. Just my thoughts, Jerry ----- Original Message ----- From: "Joe Cooper" <[EMAIL PROTECTED]> To: "Rick Matthews" <[EMAIL PROTECTED]> Cc: "Squidguard Mailing List" <[EMAIL PROTECTED]> Sent: Wednesday, November 07, 2001 12:18 AM Subject: Re: squidGuard Module for Webmin > Hi Rick, > > Have you mentioned any of this to Tim? (The fellow who wrote it for us, > and has been working on enhancements and bugfixes for another company > recently. It will see quite a bit more work from Swell pretty soon as > well, as we will be integrating SquidGuard into our systems soon.) > > The module isn't perfect yet, but Tim really does try hard to make it > work well by the time he calls it 'stable'. It is still in beta right > now, so the point is to find these problems and get them fixed--not > expect it to 'just work' out of the box. Nonetheless it is the only GUI > I know of that will address all of the various aspects of SquidGuard > administration (adding|removing|viewing the db, setting up the access > groups and rules, etc.). > > Just a thought... > > Rick Matthews wrote: > > > Well, I answered my own question by looking through his cgi scripts in > > </usr/libexec/webmin/squidguard>. > > > > The author has made the assumption that your blacklists are in: > > > > <$dbhome/blacklists/porn> > > <$dbhome/blacklists/ads> > > etc. > > > > This assumption is contrary to the documentation, which says: > > domainlist filename > > where: filename is either a path relative to dbhome or an absolute path > > (i.e. /full/path) to a database file. > > > > So, the following combination works with squidGuard and conforms to the > > documentation: > > dbhome /usr/local/squidGuard/db > > domainlist block/blacklist/porn/domains > > full path /usr/local/squidGuard/db/block/blacklist/porn/domains > > > > The above combination does not work with the Webmin squidGuard module, > > however, due to the author's incorrect assumption concerning the path. > > > > Since I've been very interested in seeing what the squidGuard module > > does for you, I made a few changes so that my path declarations would > > conform to the author's assumptions. After bouncing squid I tried the > > squidGuard module again. > > > > This time the blacklists option opened to show an icon for each of my > > blacklist categories (porn, ads, etc.) Clicking on the icon apparently > > causes the module to completely read the blacklist before opening a page > > that allows you to search or add to the files. Clicking on <porn> caused > > a delay of 20 - 25 seconds before presenting the next screen; clicking > > on <ads> brought up the next screen in less than a second. > > > > I guess the last straw was that in each of the categories, the search > > page had a red notice at the top that said "This blacklist is disabled". > > There is also a link labeled "Enable this blacklist". I have no idea > > why the module thinks my blacklists are disabled, but at this point I > > don't really care. > > > > I've uninstalled the squidGuard module for Webmin. > > -- > Joe Cooper <[EMAIL PROTECTED]> > http://www.swelltech.com > Web Caching Appliances and Support > >
