John Helmuth wrote:
I think it's called bb-fetch...
Having used bb-fetch for some time I can't really recommend
it anymore. This is NOT due to bb-fetch itself, which is a
really good idea, but due to the asynchronous way bb gets
its messages. I always ran into "purple" problems after some
hours/days, because some tests had already written their out-
put to bb, bb-fetch retrieved the output file and after that
the remaining tests wrote their output to bb. But this might
have been just me messing up the config ... ;-)
I found the usage of ssh-tunnels much more reliable in terms
of "purple". For starters there is a good introduction at:
http://www.blubrick.com/bb/index.php/CreateAtunnel
Admittedly there is some fiddling, if you have one "master"
BBDISPLAY and some "slave" BBDISPLAYs relaying to the master
plus clients at the master AND the slave(s). This is since
you can't have the ssh-tunnel and the bb-process both listen
to the same port at the slave BBDISPLAY. So i did a quick &
dirty hack to the bb sources to have bb send the relying
information to another port, at which the ssh-tunnel-end is
listening.
For the sake of keeping up my reputation of being totally
paranoid, the remote sites are connected via a IPsec VPN,
which in turn tunnels the ssh-tunnel ;-)
Regards,
Frank