Bug 27777 - Dansguardian und Squid sind nicht performant
Dansguardian und Squid sind nicht performant
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: Dansguardian
UCS 3.0
Other Linux
: P5 normal (vote)
: ---
Assigned To: Squid maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-06-29 14:22 CEST by Kevin Dominik Korte
Modified: 2017-08-08 07:07 CEST (History)
4 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 2: Improvement: Would be a product improvement
Who will be affected by this bug?: 2: Will only affect a few installed domains
How will those affected feel about the bug?: 1: Nuisance – not a big deal but noticeable
User Pain: 0.023
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin Dominik Korte univentionstaff 2012-06-29 14:22:43 CEST
Sowohl mit UCS 3.0 als auch mit UCS 2.4 bricht die Performance um mehr als 60% ein wenn Dansguardian in der UCS Konfiguration verwendet wird.

Beobachtet an Ticket: 2012062821008476
Comment 1 Moritz Muehlenhoff univentionstaff 2012-06-29 14:55:44 CEST
Die zusätzlichen Zugriffsprüfungen / Virenscan-Prozesse verursachen natürlich Overhead gegenüber normalem Caching.

Wie ist denn die Last auf dem System bei aktiviertem Dansguardian?
Comment 2 Felix Botner univentionstaff 2012-09-14 12:59:06 CEST
Vielleicht sollte man sich mal http://squidclamav.darold.net/config.html anschauen. 

dansguardian wird ja für content und virenscan verwendet. Möglicherweise kann man den virenscan über squidclamav und den "content" Scan über squiguard machen (wobei der glaube ich nur blacklists etc .macht.)
Comment 3 Stefan Gohmann univentionstaff 2017-06-16 20:36:27 CEST
This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.
Comment 4 Stefan Gohmann univentionstaff 2017-08-08 07:07:34 CEST
This issue has been filed against UCS 3.0.

UCS 3.0 is out of maintenance and many UCS components have vastly changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen this issue. In this case please provide detailed information on how this issue is affecting you.