That's interesting... I
didn't know that systemimager-server-rsyncd is needed by flamethrower - can
this be fixed?
I think flamethrower itself
should be self-contained and do not need rsyncd to be enabled on the
server...
And no, I do not get any
error using rsync.
I was also wondering if you
know anything about netbootmond - I noticed that when I use flamethrower, it
does not automatically change to localboot after successful image whereas it
works fine with rsync. If you know anything about it I'd appreciate a fix,
otherwise I could probably look into it...
BTW, for BT does it matter
which version of BitTorrent I have installed on the image_server? And
should I add a dependency for that in the spec file?
Cheers,
Bernard
From: Andrea Righi [mailto:[EMAIL PROTECTED]
Sent: Sun 16/04/2006 13:56
To: Bernard Li
Cc: sisuite-devel@lists.sourceforge.net
Subject: Re: si_monitor & flamethrower
Bernard,
try again with the last release (3518)... and be
sure to have
systemimager-rsyncd up & running, since it's used to
evaluate the image
size also with flamethrower...
Do you get the same
error also when you use rsync?
Cheers,
-Andrea
Bernard Li
wrote:
> Hey Andrea:
>
> Testing flamethrower/multicast
with SystemImager trunk r3513 revealed
> that si_monitortk reporting is
not working properly. It stays in the
> "initializing" state and I'm
also getting a bunch of errors on the console:
>
>
(standard_in) 1: parse error
> [: 1: unknown operand
>
>
I believe this was fixed previously in 3.6.x...
>
> I'll test
your latest check-in in a bit.
>
>
Thanks,
>
> Bernard
