[pve-devel] [PATCH common 1/2] fork_worker: use correct handle type for POSIX::write

Wolfgang Bumiller w.bumiller at proxmox.com
Wed Dec 27 11:15:57 CET 2017


$resfh can be a pipe from POSIX::pipe() or the upid output
handle, which is an IO::File, so we need to take its
fileno().

Signed-off-by: Wolfgang Bumiller <w.bumiller at proxmox.com>
Fixes: ed52a8435a6d ("fork_worker: use separate pipe for status messages")
---
Fixes 'Error: unable to read tail' messages produced by starting async
tasks from the UI.

 src/PVE/RESTEnvironment.pm | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/PVE/RESTEnvironment.pm b/src/PVE/RESTEnvironment.pm
index 91de875..871f12b 100644
--- a/src/PVE/RESTEnvironment.pm
+++ b/src/PVE/RESTEnvironment.pm
@@ -525,7 +525,7 @@ sub fork_worker {
 		    if !open(STDIN, "</dev/null");
 
 		$outfh = PVE::Tools::upid_open($upid);
-		$resfh = $outfh;
+		$resfh = fileno($outfh);
 	    }
 
 
-- 
2.11.0





More information about the pve-devel mailing list