Ah!
It just hit me. The reason we don't ping the IMAGESERVER if
FLAMETHROWER_DIRECTORY_PORTBASE is set, is that the client may never be
given, know, or need to know, the ip address of the imageserver because
the client is receiving _all_ of it's data via multicast, which is more
like listening to a channel, as compared with connecting directly to
a server.
I've put this as a comment in there for a future release.
Cheers, -Brian
Thus spake Bas van der Vlies ([EMAIL PROTECTED]):
Brian Elliott Finley wrote:
Thus spake Bas van der Vlies ([EMAIL PROTECTED]):
We at SARA are currently switching to flamethrower setup. If we
enable flamethrower the conenctivity test is different then
with rsync, from /etc/init.d/rcS
# Ping test
ping_test() {
echo
echo ping_test
if [ ! -z "$FLAMETHROWER_DIRECTORY_PORTBASE" ]; then
PING_DESTINATION=$GATEWAY
HOST_TYPE="default gateway"
else
PING_DESTINATION=$IMAGESERVER
fi
echo
echo "Pinging your $HOST_TYPE to ensure we have network
connectivity."
echo
My question is why?
I honestly don't remember why, but it definitely looks like it was on
purpose.
It is fine for me ;-). Still strange that the check is different. Maybe
we have to do 2 ping tests if flamethrower is enabled. One to the
gateway and if this fails to the imageserver. Just a thought
Regards
--
--
* *
* Bas van der Vlies e-mail: [EMAIL PROTECTED] *
* SARA - Academic Computing Servicesphone: +31 20 592 8012 *
* Kruislaan 415 fax:+31 20 6683167*
* 1098 SJ Amsterdam *
* *
--
--
Brian Elliott Finley Argonne, MCS Division
Mobile: 630.631.6621 Office: 630.252.4742
gpg --keyserver wwwkeys.pgp.net --recv-keys 10F8EE52
--
---
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
___
Sisuite-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/sisuite-users
