On Fri, Jul 15, 2011 at 08:05:25AM -0000, Eduard Hasenleithner wrote:
> > No, it's set up in an upstart job, so you need to reboot after
> > the upgrade.
> Now that is strange, I rebooted already several times, but the situation
> did not change. Maybe there is a chicken-and-egg problem of upstart not
> triggering the symlink creation because there are still old (pid, ...)
> files in the directory?
No, /etc/init.d/umountroot should unconditionally nuke /var/run on reboot.
Is your /etc/init.d/umountroot the unmodified version from the package?
Do you have any mount points *under* /var/run, that would prevent the rm -rf
/var/run in this shutdown script from succeeding?
Did /var/lock get turned successfully into a symlink, or is it still a
directory like /var/run?
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
<email address hidden> <email address hidden>
On Fri, Jul 15, 2011 at 08:05:25AM -0000, Eduard Hasenleithner wrote:
> > No, it's set up in an upstart job, so you need to reboot after
> > the upgrade.
> Now that is strange, I rebooted already several times, but the situation
> did not change. Maybe there is a chicken-and-egg problem of upstart not
> triggering the symlink creation because there are still old (pid, ...)
> files in the directory?
No, /etc/init. d/umountroot should unconditionally nuke /var/run on reboot.
Is your /etc/init. d/umountroot the unmodified version from the package?
Do you have any mount points *under* /var/run, that would prevent the rm -rf
/var/run in this shutdown script from succeeding?
Did /var/lock get turned successfully into a symlink, or is it still a
directory like /var/run?
-- www.debian. org/
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://
<email address hidden> <email address hidden>