Your message dated Sun, 1 Jun 2014 00:04:42 +0200
with message-id <[email protected]>
and subject line as indicated before, long fixed
has caused the Debian Bug report #742203,
regarding munin-cgi-graph stops using an non-default cgitmpdir after a while
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.)
--
742203: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742203
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: munin
Version: 2.0.6-4+deb7u2
Control: forward -1 http://munin-monitoring.org/ticket/1289
Control: fixed -1 2.0.10-1
done
As helmut noted on IRC:
> is there possibly a bug in the handling of the cgitmpdir configuration for
> fastcgi?
> it appears to reset to the default in some fastcgi worker proceses
> occasionally.
> the problem vanishes on "/etc/init.d/apache2 reload"
The bug is already fixed upstream in
6d62e6b0782ecfa0f4e0c2bec14434d675734962, which is in 2.0.10.
--
Steve Schnepp
http://blog.pwkf.org/tag/munin
--- End Message ---
--- Begin Message ---
version: 2.0.10-1
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
