Hi Johan, Thanks for reporting this bug. Comments below:
It assumes that you use an ip-address for the n4u.server.interfaces parameter.
Yes, with hindsight, that was an unfortunate assumption...
It only supports one single interface
You're correct here, I need to cater for that as well, nothing wrong with having more than one IP address in there. Not sure if I will check them all, as it would be "a priori" a rather unlikely case that would leave ndsd listening on only one of multiple configured IPs.
my configuration looked like this: n4u.server.interfaces=eth0:[EMAIL PROTECTED],[EMAIL PROTECTED]
Seems unsafe to me to rely on the ethX:X syntax. This is rather platform-specific, so I really don't want to use this in the RA. I even think that not all means of aliasing IPs will result in a such interface on Linux. So supporting this is probably a "Bad Idea".
The lo@ syntax is kind of the same (portability wise - IIRC, AIX uses lo0 for ex), and I can't see any significant problem with using the IP directly there. I'm yet to find a system where loopback <> 127.0.0.1 ;)
As it is today, eDir88 can't handle that. I haven't supplied a patch but it's an easy fix now that you know what the problem is I hope.
Yes, not a big problem to code. Just painful string matching with Bash (or rather sh...)
Thanks for debugging and reporting :) Yan _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
