John Zdunczyk wrote:
Hi Alan,

That's just it - I've been using IPaddr2 this whole time, in the
following format: IPaddr2::192.168.5.5/24/eth1:1
As you said, it normally does not assign a virtual interface, unless I
explicitly specify it, as above. This is why I was surprised by the
recurring error message.

Oh... that's now how you specify that it provide a virtual interface name (at least not that I recall). But, maybe I'm wrong :-)

eth1 normally has only one IP Address bound to it, and there are no
other virtual interfaces associated with eth1. If a virtual interface
number was specified, the proper virtual interface seems to get grabbed
every time, but it keeps printing the error message.

I see the bug :-(.

I'll file a bugzilla...

http://www.osdl.org/developer_bugzilla/show_bug.cgi?id=1259
[Of course, I could be wrong ;-)]

Doubt that, I've got megabytes upon megabytes of logs with that error
message  :)

No what I meant was "is my bug description correct"? Does IPaddr* require ipaddr for monitor, or not? (I don't think it does - the original code doesn't seem to have).


Regardless of the resolution to the virtual interface support issue,
we've decided to stop depending on the presence of a virtual interface.
Instead, we'll be parsing the results of 'ip addr show', which is the
approach that we should've taken in the first place, in my opinion.

I missed that you were already using ipaddr2.


--
    Alan Robertson <[EMAIL PROTECTED]>

"Openness is the foundation and preservative of friendship... Let me claim from you at all times your undisguised opinions." - William Wilberforce
_______________________________________________________
Linux-HA-Dev: [email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/

Reply via email to