[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: /run support for wheezy: final (I hope) call for testing



On Fri, Apr 15, 2011 at 02:28:35PM +0200, Adam Borowski wrote:
> On Fri, Apr 15, 2011 at 12:07:37PM +0100, Roger Leigh wrote:
> > http://people.debian.org/~rleigh/run/sysvinit_2.88dsf-13.3.dsc
> > 
> > Changes since last time:
> > - vserver environments should now upgrade correctly (autodetect and
> >   treat like chroots)
> 
> Sadly, it still seems to fail for me:
> 
> /var/run -> /run is properly created in postinst, exists after shutdown,
> disappears during an attempt to start it.
> 
> 
> Not sure what kills it, lemme try to find it out.  The host is squeeze but
> had been repeatedly upgraded, so something might be different from fresh
> installs.

Got it:

/usr/lib/util-vserver/vserver.start includes the following function:

## Usage: prepareInit <vserver-directory>
function prepareInit
{
    pushd "$1/vdir" >/dev/null
    case "$INITSTYLE" in
        sysv)
            { find var/run  ! -type d -print0; \
              find var/lock ! -type d -print0; } | xargs -0r $_CHROOT_SH rm
            ;;
        plain)
            $_CHROOT_SH rm .autofsck forcefsck 2>/dev/null || :
            : | $_CHROOT_SH truncate fastboot  2>/dev/null || :
            ;;
        minit)
            ;;
    esac
    "${INITCMD_PREPARE[@]}"
    popd >/dev/null
}

A symlink to a directory is not a directory...

Not sure how to fix it, especially considering that typically the host is
stable or oldstable even if specific guests run unstable.

-- 
1KB		// Microsoft corollary to Hanlon's razor:
		//	Never attribute to stupidity what can be
		//	adequately explained by malice.

Attachment: signature.asc
Description: Digital signature


Reply to: