Bug 297521
Summary: | Rebase squid to the latest stable (STABLE20) | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Martin Stransky <stransky> |
Component: | squid | Assignee: | Jiri Skala <jskala> |
Status: | CLOSED ERRATA | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 5.0 | CC: | aglotov, ddomingo, sputhenp, syeghiay, tao |
Target Milestone: | --- | Keywords: | FutureFeature, Rebase, Triaged |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Rebase: Bug Fixes and Enhancements | |
Doc Text: |
Squid has been re-based to the latest stable upstream version (STABLE21). This update addresses several bugs, including:
* The squid init script always incorrectly returned an exit code of 0. This bug is now fixed, making squid now compliant with Linux Standard Base.
* Using the refresh_stale_hit directive causes error message "Clock going backwards" to appear in
the squid log file.
* The squid installation process did not set up correct ownership of /usr/local/squid
directory. With this release, the user squid is now the default owner of /usr/local/squid.
* Whenever squid attempts to use the function hash_lookup(), it could abort with signal 6.
* Using squid_unix_group could cause squid to crash.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2009-01-20 21:16:49 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 454962 |
Description
Martin Stransky
2007-09-20 08:13:38 UTC
This request was evaluated by Red Hat Product Management for inclusion, but this component is not scheduled to be updated in the current Red Hat Enterprise Linux release. This request will be reviewed for a future Red Hat Enterprise Linux release. Latest STABLE is 2.6.STABLE20 rebased to last release STABLE21 This release note is now in the 5.3 Release Notes. The changes should be visible internally (within 12 hours) on: http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.3/html/Release_Notes/ If there are any changes required, please edit the "Release Notes" field above and set the requires_release_notes flag back to ?. Release note added. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Squid has been re-based to the latest stable upstream version (STABLE20). This update addresses several bugs, including: * The squid init script always incorrectly returned an exit code of 0. This bug is now fixed, making squid now compliant with Linux Standard Base. * Using the refresh_stale_hit directive causes error message "Clock going backwards" to appear in the squid log file. * The squid installation process did not set up correct ownership of /usr/local/squid directory. With this release, the user squid is now the default owner of /usr/local/squid. * Whenever squid attempts to use the function hash_lookup(), it could abort with signal 6. * Using squid_unix_group could cause squid to crash. Release note updated. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,4 +1,4 @@ -Squid has been re-based to the latest stable upstream version (STABLE20). This update addresses several bugs, including: +Squid has been re-based to the latest stable upstream version (STABLE21). This update addresses several bugs, including: * The squid init script always incorrectly returned an exit code of 0. This bug is now fixed, making squid now compliant with Linux Standard Base. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2009-0126.html |