squid's apport hook should include /var/log/squid/cache.log in crash reports
Bug #676141 reported by
Clint Byrum
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
squid (Ubuntu) |
Fix Released
|
Wishlist
|
Bryce Harrington |
Bug Description
Binary package hint: squid
When debugging squid crashes it would be extremely helpful to have the cache.log in addition to the other logs that are included. It may also be helpful to include the other logs as well, but cache.log will have any error messages.
Related branches
~bryce/ubuntu/+source/squid:fix-lp676141-noble
Merged
into
ubuntu/+source/squid:ubuntu/noble-devel
at
revision fecdce8b53d7d071786cef2fae8143a96d85a0ce
- git-ubuntu bot: Approve
- Utkarsh Gupta (community): Approve
- Canonical Server Reporter: Pending requested
- Canonical Server Core Reviewers: Pending requested
-
Diff: 90 lines (+65/-0)3 files modifieddebian/changelog (+7/-0)
debian/rules (+4/-0)
debian/source_squid.py (+54/-0)
Changed in squid (Ubuntu): | |
importance: | Undecided → Wishlist |
Changed in squid (Ubuntu): | |
status: | New → Confirmed |
Changed in squid (Ubuntu): | |
assignee: | nobody → Bryce Harrington (bryce) |
To post a comment you must log in.
Looking at (fixed and unfixed) bug reports for Squid over the past few years, I don't spot any where log, config, or other files were needed to diagnose problems. There also seem to be relatively few auto-collected crash reports (at least, few that triggered apport).
Squid doesn't currently have an apport hook, and given the above I'm not sure having one is terribly necessary. But on the off chance I'm wrong, attached is a quick draft of one that could be considered here.