SourceForge: qemudo/qemudo: changeset 264:89314d6bf495
improve description of a known bug
authorMarc Bevand <marc_bevand@rapid7.com>
Sun Sep 13 19:03:03 2009 -0700 (2 months ago)
changeset 26489314d6bf495
parent 263e13028b23c37
child 265cfd0619e71f1
improve description of a known bug
TODO
     1.1 --- a/TODO	Tue Mar 03 20:21:12 2009 -0800
     1.2 +++ b/TODO	Sun Sep 13 19:03:03 2009 -0700
     1.3 @@ -13,11 +13,16 @@
     1.4  - Web UI: arbitrary monitor command
     1.5  - Web UI: ability to disconnect someone who is connected via VNC
     1.6  
     1.7 -- seen in qwrapper.log:
     1.8 -  (qemu) info vnc
     1.9 -  VNC server active on: mrsq.tor.rapid7.com:14
    1.10 -  No client connected
    1.11 -  (qemu) Can't use an undefined value as a symbol reference at /usr/local/bin/qwrapper line 38.
    1.12 +- I once saw in qwrapper.log:
    1.13 +    (qemu) info vnc
    1.14 +    info vnc
    1.15 +    VNC server active on: mrsq.tor.rapid7.com:6
    1.16 +    No client connected
    1.17 +    (qemu) Can't use an undefined value as a symbol reference at /usr/local/bin/qwrapper line 38.
    1.18 +  This is appears to be caused by $wbuf_to_client being undef:
    1.19 +    37:while (length($wbuf_to_client)) {
    1.20 +    38: $bytes = syswrite($client, $wbuf_to_client, 4096);
    1.21 +    39: last if !defined($bytes);
    1.22  
    1.23  - Fix that potential race condition: when starting Qemudo, there is a period
    1.24    of time during which it re-attaches itself to the guests already running