In an effort to reduce FS writes on a system with a solid-state disk,
I mount /var/run as a tmpfs, i.e. ramdisk. Other packages do not mind
and create their /var/run/xxx directories as required, e.g. "bind".
When /var/run/munin is not present after a reboot, munin-node refuses
to start but does not issue an error message.
You arbitrarily delete contents of the munin-node package, and then
consider it a bug that it doesn't work any longer? Please.
No, I consider it a bug that munin-node fails silently, without so much
as an error message. I was only able to discover the cause via strace. I
know that that is not a package maintainer's bug, but that you might fix
it in the same way as mldonkey was fixed, with an init script tweak:
http://www.mail-archive.com/ubuntu-bugs@lists.ubuntu.com/msg16629.html
There's already code to handle this situation in the upstream
repositories, however. (To support Ubuntu, which does the same thing
as you do, for some strange reason.)
For what it's worth you'll end up with double the amount of writes
with your setup (mkdir+pidfile creation vs. pidfile creation only).
I'm not troubled by more writes on the tmpfs. Thanks for the
consideration, though.
Regards
Cheers,
Paul
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
