[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#655852: marked as done (polipo: Polipo should log queries/fetches.)



Your message dated Thu, 05 Dec 2019 06:25:54 +0000
with message-id <E1ickaI-000Bsh-SC@fasolo.debian.org>
and subject line Bug#900127: Removed package(s) from unstable
has caused the Debian Bug report #655852,
regarding polipo: Polipo should log queries/fetches.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
655852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655852
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: polipo
Version: 1.0.4.1-1.1
Severity: wishlist

Dear Maintainer,

I'm used to using squid and using its logs to generate stats useful
for analysing traffic and proxy performance. This has been very useful
for tuning cache perfomance and identifying popular and/or problematic
servers.

With polipo, even with logLevel=0xff there doesn't seem to be any sort
of query and/or fetch logging output, making it impossible to do any
sort of analysis.

It would be nice if polipo logged client requests and upstream
fetches. Copying squids logging output would make it easier to use
existing log analyser scripts, but I suspect that squids logging is
actually not that useful for polipo. Even just being able to see
requests/bytes/latency for client requests and upstream fetches would
be useful to determin overall cache hit rates and performance would be
useful.

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages polipo depends on:
ii  dpkg          1.16.1.2
ii  install-info  4.13a.dfsg.1-8
ii  libc6         2.13-24

polipo recommends no packages.

polipo suggests no packages.

-- Configuration Files:
/etc/polipo/config changed:
proxyAddress = "0.0.0.0"    # IPv4 only
allowedClients = 127.0.0.1, 192.168.0.0/24
                                            
proxyName = "proxy.localnet"
proxyPort = 3128
chunkHighMark = 268435456
objectHighMark = 65536
disableIndexing = false
disableServersList = false
dnsQueryIPv6 = no
logSyslog = true
logFacility = "daemon"
logLevel = 0xFF


-- no debconf information



--- End Message ---
--- Begin Message ---
Version: 1.1.1-10+rm

Dear submitter,

as the package polipo has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/900127

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

--- End Message ---

Reply to: