This one time, at band camp, Paolo said:
> On Fri, Jan 12, 2007 at 06:05:47PM +0000, Stephen Gran wrote:
> > > tmpfs on /var/lock type tmpfs (rw,size=4m)
> > > tmpfs on /var/run type tmpfs (rw,size=4m)
> > >
> > > so everything under /var/run vanishes on reboot.
> >
> > Look for RAMRUN and RAMLOCK - probably in /etc/default somewhere.
> > Comment or set the variable to something other than yes. I agree this
> > is a bad default.
>
> eh, no RAMRUN/RAMLOCK anywhere but in /etc/init.d/{boot,mount}*. Totally
> undoc'd, tried to zgrep the whole /doc* and /man*.
> I guess the tmpfs entries in fstab are done on system install, once for all.Hmm. Me either, but I don't have a tmpfs mounted on /var/run. Reading the init scripts, it looks like it won't do it unless RAMRUN is defined somewhere. Odd that you can't find it. Take a look at a couple of init scripts - `grep -rl RAMRUN` /etc/init.d will give you an idea where it's referenced, and then you can build a list of files that are sourced, and grep them. > don't know whether other pkgs are doing mkdir to address same issue, but > note that clamav-freshclam already checks/makes /var/lib/ucf/cache, so doing > same for /var/run/clamav doesn't look too exotic, after all. This is an artifact of my common-functions implementation - if I write reusable code that is needed in several of the packages, they all get all the reusable functions. Those mkdir calls are actually only ever run from postinstall scripts - the init scripts carry them as cruft that saves me hours of repetetive copy and paste. > Clearly the issue needs proper (policy?) addressing, and involves initscripts, > as it is unacceptable that eg setting RAMRUN breaks many pkgs. Agreed. -- ----------------------------------------------------------------- | ,''`. Stephen Gran | | : :' : [EMAIL PROTECTED] | | `. `' Debian user, admin, and developer | | `- http://www.debian.org | -----------------------------------------------------------------
signature.asc
Description: Digital signature
