Yes it's /var/backups. The symlink is specific to this machine though other hosts in the company had been set up with the backups actually under /var/backups. Those may have been ubuntu, debian or CentOS (I'm not in charge of those). Should we avoid /var/backups?
Colin Watson wrote: > We were actually relatively careful to touch only directories the > packaging system knew about, I thought. Here's the relevant code. I > can't see where this could recurse into /var/volumes; could you look > over the following and see if any of the mentioned directories might > contain symlinks into /var/volumes? I suspect that this is specific to > your system somehow but I don't yet see how. Thanks in advance. > > NINER_NINER_PATHS=" \ > /boot \ > /etc \ > /usr/lib/locale \ > /var/backups \ > /var/cache/apt \ > /var/cache/debconf \ > /var/cache/fontconfig \ > /var/cache/fonts \ > /var/cache/ldconfig \ > /var/cache/anthy \ > /var/lib/apt \ > /var/lib/dpkg \ > /var/lib/belocs \ > /var/lib/gconf \ > /var/lib/defoma \ > /var/lib/locales \ > /var/log/installer " > > NINER_NINER_SYMLINKS=" \ > /initrd.img \ > /vmlinuz \ > /cdrom \ > /media/cdrom \ > /etc/alternatives \ > /usr/share/fonts \ > /var/lib/anthy \ > /var/lib/defoma " > > find -L $NINER_NINER_PATHS -gid 999 -print0 | > xargs -0rt chgrp 0 > find $NINER_NINER_SYMLINKS -gid 999 -print0 | > xargs -0rt chgrp -h 0 > find /media -maxdepth 1 -name "cdrom[0-9]*" -gid 999 -print0 | > xargs -0rt chgrp 0 > > find /lib/modules -maxdepth 2 -name "modules.*" -gid 999 -print0 | > xargs -0rt chgrp 0 > > > ** Changed in: base-files (Ubuntu) > Status: New => Incomplete > > ** Changed in: base-files (Ubuntu) > Assignee: (unassigned) => Colin Watson (cjwatson) > > -- base-files postinstall recurses into /var https://bugs.launchpad.net/bugs/319477 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
