Source: mono
Version: 3.0.6+dfsg2-10
Severity: important

>From my pbuilder build log:

...
umount: /build/chroot-amd64/run/shm: device is busy.
        (In some cases useful info about processes that use
         the device is found by lsof(8) or fuser(1))

  Could not unmount run/shm, some programs might
  still be using files in /proc (klogd?).
  Please check and kill these processes manually
  so that I can unmount run/shm.  Last umount error was:
umount: /build/chroot-amd64/run/shm: device is busy.
        (In some cases useful info about processes that use
         the device is found by lsof(8) or fuser(1))

  This error only affects chroots; you may want to use
  user-mode-linux to avoid this message.

...

This is because the process below is still running and prevents the chroot's 
/run/shm from being unmounted.  So, I have to manually kill it in order for 
the build to complete.

1234     31167  0.0  0.0   8496   692 pts/7    SN+  12:36   0:00 sh -c 
MONO_PATH=/tmp/buildd/mono-3.0.6+dfsg2/mcs/class/lib/net_4_5 
MONO_SHARED_DIR=/tmp/buildd/mono-3.0.6+dfsg2/runtime 
MONO_CFG_DIR=/tmp/buildd/mono-3.0.6+dfsg2/runtime/etc ../../doltlibtool --
mode=execute  ../../mono/mini/mono --config tests-config --optimize=all --debug 
bug-10127.exe 2>bug-10127.exe.stderr 1>bug-10127.exe.stdout
1234     31168  204  0.7 966728 62284 pts/7    RNl+ 12:36   5:04  \_ 
../../mono/mini/mono-sgen --gc=sgen --config tests-config --optimize=all 
--debug 
bug-10127.exe
-- 
Daniel Schepler


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to