Re: [Systemimager] Re: [Sisuite-users] Flamethrower connectivity test problem]

2004-07-20 Thread Bas van der Vlies
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

Re: [Systemimager] Re: [Sisuite-users] Flamethrower connectivity test problem

2004-07-20 Thread Brian Elliott Finley
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

Re: [Sisuite-users] Flamethrower connectivity test problem

2004-07-18 Thread Brian Elliott Finley
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

[Sisuite-users] Flamethrower connectivity test problem

2004-06-09 Thread Bas van der Vlies
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