On 2006-05-31 17:00, Nicola Mauri wrote:

 >> use the interface (aka bind) option in xinetd to run multiple
 >> instances of the amanda client each responding on a different address

TESTED. Configuring multiple amanda client seems to solve this issue!

My new /etc/xinet.d/amanda file has three entries:
 - The first entry binds to node physical interface.

- The remaining entries bind to every virtual interface defined in the cluster.

I noticed only one problem: when xinetd starts, some virtual interfaces may not be defined on machine, as they are assigned to other cluster members; xinetd won't be listening on non-existent interfaces. When a service is relocated to the node, along with its interface, xinetd must be somehow restarted to get it listening also on the new acquired interface.

Should I schedule a daily '/etc/init.d/xinetd restart'?

(that's not very smart, is it?)

Can you add that command to the program that relocates the service:

  kill -HUP `cat /var/run/xinetd.pid`


--
Paul Bijnens, xplanation Technology Services        Tel  +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM    Fax  +32 16 397.512
http://www.xplanation.com/          email:  Paul.Bijnens AT xplanation DOT com
***********************************************************************
* I think I've got the hang of it now:  exit, ^D, ^C, ^\, ^Z, ^Q, ^^, *
* F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt,  abort,  hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e,  kill -1 $$,  shutdown, *
* init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
* ...  "Are you sure?"  ...   YES   ...   Phew ...   I'm out          *
***********************************************************************