On Thu, Sep 24, 2009 at 01:32:13PM +0100, Colin Watson wrote:
> On Thu, Sep 10, 2009 at 01:25:06PM +0200, Adam Borowski wrote:
> > Sadly, man-db still spams.
> > The line you added is:
> > if ! grep -q 'envID:.*[1-9]' /proc/self/status; then
> >
> > but /proc/self/status doesn't include that envID line you're looking for,
> > neither on 2.6.18 nor 2.6.26.
>
> Can you provide an authoritative way to detect that we're in a vserver
> container, preferably with a reference?
An authoritative way, not really.
A non-authoritative way:
/proc/self/status will have a line:
VxID: 0 in the host
VxID: x where x is a number!=0 in containers
So this looks exactly like that envID thingy in OpenVZ.
> > I also wonder, perhaps it would be better to instead ask for having
> > start-stop-daemon hush nice/ionice messages when -q is given, as that's
> > more of an informative message rather than a real error.
>
> I CCed the dpkg guys on another similar bug today. It's certainly
> annoying to have to work around this in multiple places.
Yeah, that's why I insist on hushing these non-fatal messages instead. This
way you'll have it working when a yet another type of virtualization crops
up -- and changing this in start-stop-daemon means anything which uses it
will be taken care of.
Cheers,
--
1KB // Microsoft corollary to Hanlon's razor:
// Never attribute to stupidity what can be
// adequately explained by malice.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
