On Mon, 2008-12-29 at 16:03:34 +0100, Frans Pop wrote: > On Monday 29 December 2008, Raphael Hertzog wrote: > > If the same system call is causing this change then: > > strace -f -v -e trace=ioctl
> OK, I can somewhat reproduce this although the behavior appears quite > random. I don't get caps consistently for the same invocations of dpkg, > but things change around. I've no idea yet what could trigger it, > unless it would be console switching. > The full strace file where I got the caps problem is attached, but I > don't think we can tell what process 24401 was from that, correct? > Should I get further details? You could append ',clone,fork,vfork,execve' to 'trace=ioctl'. > On Monday 29 December 2008, Guillem Jover wrote: > > You seem to be running it under virtualbox, did you run that pbuilder > > under some emulator as well, vbox or qemu? Which kind of output are you > > using, serial? > > pbuilder was run on a normal amd64 system running Lenny under KDE's konsole, > possibly (but unlikely) in an i386 chroot. > I'm not using serial console in the D-I case, just regular VTs. My initial gut feeling was that this could be one of kernel, glibc, the terminal emulator or the program invoking dpkg (in this case apt). I guess the terminal emulator we can discard, as it happens with different ones. > > > Also note that in D-I all output is redirected to syslog and not to a > > > terminal, although I guess terminal settings could still influence > > > it. > > > > Who is responsible of redirecting the output to syslog? > > We use a special D-I utility 'log-output' written by Colin for that (part > of debian-installer-utils source package). Ok, skimmed over the source and didn't see anything suspicious and given that it happens outside D-I we can ignore it. regards, guillem -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
