Your message dated Thu, 16 Oct 2008 12:32:06 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#501454: fixed in varnish 2.0-1
has caused the Debian Bug report #501454,
regarding Please add varnishncsa init script
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 [EMAIL PROTECTED]
immediately.)


-- 
501454: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=501454
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: varnish
Version: 1.1.2
Severity: minor

Copying from
https://bugs.launchpad.net/ubuntu/+source/varnish/+bug/277558
:

There already is a init script for varnishlog (
http://linux.die.net/man/1/varnishlog ) to save the varnish log to a file.

But there is no init script for varnishncsa (
http://linux.die.net/man/1/varnishncsa ).
varnishncsa produces apache-style logs, these are much more useful
because one can use standard logfile analysis tools (awstats f.x.).

The command line arguments for both are very similar: Varnishlog accepts
a superset of varnishncsa's arguments - but the varnishlog init script
only uses the common ones.
The varnishlog init script can be used for varnishncsa with slight
modifications.

I attach a diff of the neccessary changes.
The only non-obvious change is the addition of the -c switch.
Without this switch, varnishncsa also logs varnish accessing the backend
webserver. For an apache-style log, you obviously want to see only
clients accessing the proxy.


diff_varnishlog_varnishncsa.txt  (684 bytes, text/plain)
http://launchpadlibrarian.net/18160068/diff_varnishlog_varnishncsa.txt



--- End Message ---
--- Begin Message ---
Source: varnish
Source-Version: 2.0-1

We believe that the bug you reported is fixed in the latest version of
varnish, which is due to be installed in the Debian FTP archive:

libvarnish-dev_2.0-1_amd64.deb
  to pool/main/v/varnish/libvarnish-dev_2.0-1_amd64.deb
libvarnish1_2.0-1_amd64.deb
  to pool/main/v/varnish/libvarnish1_2.0-1_amd64.deb
varnish_2.0-1.diff.gz
  to pool/main/v/varnish/varnish_2.0-1.diff.gz
varnish_2.0-1.dsc
  to pool/main/v/varnish/varnish_2.0-1.dsc
varnish_2.0-1_amd64.deb
  to pool/main/v/varnish/varnish_2.0-1_amd64.deb
varnish_2.0.orig.tar.gz
  to pool/main/v/varnish/varnish_2.0.orig.tar.gz



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Stig Sandbeck Mathisen <[EMAIL PROTECTED]> (supplier of updated varnish package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Thu, 16 Oct 2008 14:04:42 +0200
Source: varnish
Binary: varnish libvarnish1 libvarnish-dev
Architecture: source amd64
Version: 2.0-1
Distribution: unstable
Urgency: low
Maintainer: Stig Sandbeck Mathisen <[EMAIL PROTECTED]>
Changed-By: Stig Sandbeck Mathisen <[EMAIL PROTECTED]>
Description: 
 libvarnish-dev - Development files for Varnish
 libvarnish1 - Shared libraries for Varnish
 varnish    - A state-of-the-art, high-performance HTTP accelerator
Closes: 481067 501454
Changes: 
 varnish (2.0-1) unstable; urgency=low
 .
   * New upstream version
   * Add varnishncsa init script, defaults and log rotation (Closes: #501454)
   * Add dependency on libc6.1-dev (Closes: #481067)
Checksums-Sha1: 
 e6955d7e9e72a1780ede8919667b692474d6ef66 1317 varnish_2.0-1.dsc
 92c75ba40136d12e059ee0bf6187ff35ce05dd6a 374924 varnish_2.0.orig.tar.gz
 4b209de91bd49e96f4cee497e5f9c7bd181b16fc 8127 varnish_2.0-1.diff.gz
 326eb8d6b70cc28a4fa7e215cd55023a31f1378d 259234 varnish_2.0-1_amd64.deb
 542a932f8190960540fc722286cdd757d0810b9d 75652 libvarnish1_2.0-1_amd64.deb
 37bff272a525f8f6442ad8930c26936eff24e21d 92536 libvarnish-dev_2.0-1_amd64.deb
Checksums-Sha256: 
 c90d845b487c370a33074ff815c16e1b935a389e299ef63ca449f46d22b12249 1317 
varnish_2.0-1.dsc
 ecd33803849a5850af692b6fa09bc2e34d5944a10a5895b3f78910b952a88f38 374924 
varnish_2.0.orig.tar.gz
 64daf9db47e76d8e6f1c6151f0ec13d6f6c9435712d8d84274d043d701fe7ee3 8127 
varnish_2.0-1.diff.gz
 612bd270440b9d317e5ac57ea179cfab4f8bcfde32ea35b3ac37850cd3948fbf 259234 
varnish_2.0-1_amd64.deb
 a449fb047f0a727c28a8e5926ea354b3066d9420627e83fe39453c4ff36ddb53 75652 
libvarnish1_2.0-1_amd64.deb
 df1ba4568afe8c795b5eabe82c4b6d0fb9455bf08ccd76009fcecdfe61035bb2 92536 
libvarnish-dev_2.0-1_amd64.deb
Files: 
 b25aef20577ffe33e5220e36056602db 1317 web optional varnish_2.0-1.dsc
 9d4263fe283530d5e2a693c9bfa77cc9 374924 web optional varnish_2.0.orig.tar.gz
 c6b72542abe3f280284292d856a9c689 8127 web optional varnish_2.0-1.diff.gz
 2600087dc510de299b469412aef63f1b 259234 web optional varnish_2.0-1_amd64.deb
 69a0c7a9e7cbbb2dc01fc4ecdbf133c7 75652 libs optional 
libvarnish1_2.0-1_amd64.deb
 e6009f13ddb0a5f5d5dc4c9fe3ac1f13 92536 libdevel optional 
libvarnish-dev_2.0-1_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkj3L3UACgkQQONU2fom4u4/XQCfbmhlwF9T2DLasR6BPLs/QoeR
joEAn2e8nMlho0lwg8YPcdNsYjje4Eqj
=hkny
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to