Project

General

Profile

Actions

Bug #265

closed

Bugs in Squid LightSquid SquidGuard Packages in PFsense 2.0

Added by Alfredo Frugone over 14 years ago. Updated almost 13 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Squid
Target version:
-
Start date:
12/31/2009
Due date:
% Done:

30%

Estimated time:
Plus Target Version:
Affected Version:
2.0
Affected Plus Version:
Affected Architecture:

Description

Squid is a very useful package, but has many problems in 2.0:
1.- Version problems with libcrypt, libcrypto and libssl.
2.- After renaming these libs,Squid and SquidGuard can be installed, but not showing in Installed packages.
3.- Squid and Squidguard cannot be removed, as they are not in installed packages
4.- LightSquid stops installation in "Loading package configuration..."

Actions #1

Updated by Jim Pingle about 14 years ago

  • % Done changed from 0 to 30
  • Affected Version set to 2.0

I have squid working again on 2.0. Haven't tried to move on to SquidGuard and Lightsquid yet.

Actions #2

Updated by Basel G. over 13 years ago

To effectively remove packages you have to delete the .xml file(s) in "/usr/local/pkg", this seems to be a problem with all packages on embedded too when a package fails to install tested on 2.0-BETA4-4g-20101014-0217-nanobsd.

Another problem with Squidguard is it uses /var/ for storing the blacklists, on embedded it gets lost on a reboot plus it has a limited space, which breaks the whole system in case there's not enough, I think this can be fixed by recompiling Squidguard with some custom dir options.

Actions #3

Updated by Chris Buechler over 13 years ago

The only alternative to using /var is to keep the CF mounted read write all the time, which eliminates the purpose of running embedded. That's just not a good thing to run on an embedded system if you're trying to do all that. In some configurations it's ok, yours doesn't sound like one of them.

Actions #4

Updated by Basel G. over 13 years ago

No need to make the CF mounted read/write all the time just to extract the Squidguard blacklists, why not to mount RW for extraction, then RO again? I think it's better in all embedded configurations to store it on a permanent directory away from /var/, The current shallalist is about 35mb, having a list once is better than none at all.

Actions #5

Updated by Basel G. over 13 years ago

squidGuard.conf contains the option "dbhome" which defines where blacklists are located, the default path is /usr/local/squidGuard/db. Maybe modifying this will solve the issues on embedded.

Actions #6

Updated by Jim Pingle almost 13 years ago

  • Status changed from New to Resolved

Squid, Squidguard, and Lightsquid have been working on 2.0 for quite some time now.

Actions

Also available in: Atom PDF