Re: Where should rrd files generated by a program be stored ?
Oliver Kurth <firstname.lastname@example.org> writes:
> On Mon, 2004-02-16 at 16:38, Goswin von Brederlow wrote:
> > Oliver Kurth <email@example.com> writes:
> > > On Mon, 2004-02-16 at 16:12, Goswin von Brederlow wrote:
> > > > Oliver Kurth <firstname.lastname@example.org> writes:
> > >
> > > > > Although I think this is dependending on the exact purpose of the rrd
> > > > > files, I would say, yes. I would like to mount /var/cache to a ram disk,
> > > > > but this is not possible, because debconf stores its data there - there
> > > > > is/was a bug filed about that in debconf, but I cannot find that
> > > > > anymore.
> > > >
> > > > If you keep the directory structure that should work. And regarding
> > > > debconf, it would just ask the questions again on the next update. Its
> > > > operation is not compromised by loosing the DB, just its comfort. Or
> > > > not?
> > >
> > > True. But I do not want to loose the comfort ;-), ie. I do not want to
> > > answer all these questions again and again on each upgrade.
> > Then don't delete the cache. :)
> Sigh. I want to mount /var/cache to a ram disk. Then /var/cache/debconf
> is also on ram disk. So it's gone when I reboot. To save it, I would
> have to tweak it, eg. with bind mounting, so that /var/cache/debconf is
> on disk again. This trouble would not be necessary if the debconf DB was
> in /var/lib in the first place.
You have to store and restore the directory structure and permissions
on every reboot too. Its not ment to be lost completly on a regular
> > I suggest using tmpfs instead of a ramdisk too.
> Agreed. It is not relevant for the problem though.