diff options
| author | Richard Jones <rjones@redhat.com> | 2009-04-26 11:15:57 +0100 |
|---|---|---|
| committer | Richard Jones <rjones@redhat.com> | 2009-04-26 11:15:57 +0100 |
| commit | 9501ab7792e50e464dc65e9190a0e1d84b5dd423 (patch) | |
| tree | 043006fafd7a3428c5c7df398a60ba5a46bcee02 | |
| parent | 79633552a42f5d6d60d5204c39acb0bc093199ae (diff) | |
| download | libguestfs-9501ab7792e50e464dc65e9190a0e1d84b5dd423.tar.gz libguestfs-9501ab7792e50e464dc65e9190a0e1d84b5dd423.tar.xz libguestfs-9501ab7792e50e464dc65e9190a0e1d84b5dd423.zip | |
Update BUGS with latest status.1.0.13
| -rw-r--r-- | BUGS | 5 |
1 files changed, 5 insertions, 0 deletions
@@ -22,6 +22,11 @@ http://java.sun.com/j2se/javadoc/writingdoccomments/ [libguestfs] If qemu process is a shell script, then it is not cleaned up correctly, even on "good" exit. This is because we need to set up a new process group (see commented code for doing setpgid). +[fixed? - added documentation in the manual page that you have to +do 'exec qemu' in the wrapper. However I still notice that the +recovery process kills qemu, instead of it being killed by the +parent process, or at least that's what I think is happening] [libguestfs] Some occasional data corruption, certainly on tgz-out. Try using tgz-out on a very large directory. +[we think this is fixed by 64a6a828bd318622420cf3018899392fd80c14e7] |