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.
> > I'm pretty fine with doing away with the tmpfs.
>
> As am I. I will raise it again on the mailing lists and see what is
> going on.
currently I see
/etc/init.d/alsa: if ! mkdir --mode=755 /var/run/alsa ; then
/etc/init.d/clamav-daemon: mkdir -p /var/run/clamav
/etc/init.d/clamav-freshclam:mkdir -p /var/run/clamav
/etc/init.d/clamav-freshclam: [ -d /var/lib/ucf/cache ] || mkdir -p
/var/lib/ucf/cache
/etc/init.d/dirmngr: mkdir -p /var/run/dirmngr || return 1
/etc/init.d/ipsec:mkdir -p /var/run/pluto
/etc/init.d/vsftpd: [ -d /var/run/vsftpd ] || mkdir -p /var/run/vsftpd
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.
Clearly the issue needs proper (policy?) addressing, and involves initscripts,
as it is unacceptable that eg setting RAMRUN breaks many pkgs.
thanks
--
paolo
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
