* Matt Zimmerman
> That isn't accurate. It solves a number of real problems, such as the
> situation where a pid file needs to be written there, but the root
> filesystem is mounted read-only (or even not mounted yet, e.g.
> initramfs).
Good point. Would've been nice if those files were moved
On Mon, Jul 31, 2006 at 05:06:38PM +0200, Tore Anderson wrote:
> * Matt Zimmerman
>
> > It isn't particularly strange; Ubuntu uses a tmpfs for /var/run now.
>
> Which is exactly what I find strange.
>
> I asked Tollef about it the other day, and understood it simplified
> some cleanup scrip
* Paul Radford
> That's what I get for setting log level to 0 in munin-node.conf (/var
> mounted read-only), I guess. *slaps forehead*. I had been looking for
> a stdout message, but again that's upstream's decision. Sorry.
I believe that by the time it bombs out, it has already detached fro
* Matt Zimmerman
> It isn't particularly strange; Ubuntu uses a tmpfs for /var/run now.
Which is exactly what I find strange.
I asked Tollef about it the other day, and understood it simplified
some cleanup script slightly. Hardly something worth breaking heaps of
packages, local applicat
On Mon, Jul 31, 2006 at 12:35:44PM +0200, Tore Anderson wrote:
> 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.)
It isn't particularly strange; Ubuntu uses a tmpfs for /
Tore Anderson wrote:
When you yank out essential data from underneath dpkg, all bets are
off. Anyway, I cannot reproduce the silent failure you're describing:
[EMAIL PROTECTED] :) sudo /etc/init.d/munin-node start
Starting munin-node: FAILED!
The log brings more information:
* Paul Radford
> 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.
When you yank out essential data from underneath dpkg, all bets are
off. Anyway, I cannot reproduce the silent failure you're desc
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
retitle 380434 deal with /var/run/munin gone AWOL
severity 380434 wishlist
tags 380434 fixed-upstream
quit
* Paul Radford
> 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
Package: munin-node
Version: 1.2.3-1
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
10 matches
Mail list logo
