On Fri, Jul 17, 2009 at 11:04:20AM +0200, Norman Leutner wrote:
Thanks for the hint, it's been the PATH...
[varnish_*]
env.varnishstat /usr/local/bin/varnishstat
works fine now.
Glad to hear it :)
I found a small mistake in your plugin, when using multiple varnish
installations on a
Norman Leutner n.leut...@all2e.com writes:
[to Kristian Lyngstol]
Your're the one who wrote that plugin...
I was about to say no, that was me - then I found out that my code had
been replaced.
Kristian, what was wrong with the existing plugin? More to the point,
what was so wrong about it
Norman Leutner n.leut...@all2e.com writes:
Kristian has created a more abstract plugin which includes all needed
functions in one plugin.
And how is that different from the one I wrote?
DES
--
Dag-Erling Smørgrav - d...@des.no
___
varnish-misc
On Fri, Jul 17, 2009 at 01:03:07PM +0200, Dag-Erling Smørgrav wrote:
Norman Leutner n.leut...@all2e.com writes:
[to Kristian Lyngstol]
Your're the one who wrote that plugin...
I was about to say no, that was me - then I found out that my code had
been replaced.
Kristian, what was wrong
Hi,
I'm new to this mailing list.
As a German partner of eZ Systems AS we're using varnish in combination with eZ
Publish with great success.
Currently I'm trying to get munin running with the plugin from the trunk
http://varnish.projects.linpro.no/browser/trunk/varnish-tools/munin
Now I
On Thu, Jul 16, 2009 at 03:31:01PM -0400, Norman Leutner wrote:
Trying manually using munin-run I'm getting the expected results.
# munin-run varnish_hit_rate
client_req.value 30714
(...)
Using the munin telnet interface I get no data...
# telnet localhost 4949
Trying 127.0.0.1...
