[pve-devel] [PATCH] RBD print error to STDERR instead of hiding it

Stefan Priebe - Profihost AG s.priebe at profihost.ag
Fri May 31 10:01:09 CEST 2013


Am 31.05.2013 09:54, schrieb Dietmar Maurer:
>> +	run_command($cmd, errmsg => "rbd error", errfunc => sub { print
>> STDERR
> 
> So why do you specify errfunc (print to STDERR is default behavior)?
> 
If i do it this way:
run_command($cmd, errmsg => "rbd error");

it takes a lot longer until i see output. It seems the output is heavily
buffered.

Instead of seeing line by line i get suddenly big hunks like this:
Rolling back to snapshot: 1% complete...
Rolling back to snapshot: 2% complete...
Rolling back to snapshot: 3% complete...
Rolling back to snapshot: 4% complete...
Rolling back to snapshot: 5% complete...
Rolling back to snapshot: 6% complete...
Rolling back to snapshot: 7% complete...
Rolling back to snapshot: 8% complete...
Rolling back to snapshot: 9% complete...
Rolling back to snapshot: 10% complete...
Rolling back to snapshot: 11% complete...
Rolling back to snapshot: 12% complete...
Rolling back to snapshot: 13% complete...
Rolling back to snapshot: 14% complete...
Rolling back to snapshot: 15% complete...
Rolling back to snapshot: 16% complete...
Rolling back to snapshot: 17% complete...
Rolling back to snapshot: 18% complete...
Rolling back to snapshot: 19% complete...
Rolling back to snapshot: 20% complete...
Rolling back to snapshot: 21% complete...
Rolling back to snapshot: 22% complete...
Rolling back to snapshot: 23% complete...
Rolling back to snapshot: 24% complete...
Rolling back to snapshot: 25% complete...
Rolling back to snapshot: 26% complete...

Stefan



More information about the pve-devel mailing list