Hello,
by the way, I added a conn_error_callback, as in your code. Interestingly:
after sending the empty tipc_send2name the conn_error_cb gets invoked with
reason=2. The tipc_send fails and returns something like -22 or -28, so
I let the module loading fail.
If instead I send directly the subscription message with tipc_send2name
(without sending an empty message first), the conn_error_cb gets called
when the first publish event should be comming.
Regards,
Erich
On Samstag 23 Februar 2008, Erich Focht wrote:
> Dear Elmer,
>
> thanks for the example. I actually added your callback to my init code,
> and changed the subscription "type" to 18888, such that the example should
> work fine with the tipc_demo-1.16/topology_subscr_demo/ example.
>
> But it doesn't (2.6.24, on x86_64). Loading the module shows the messages are
> sent fine, and a new connection is in the "tipc-config -p" output:
> 2818850801: connected to <1.1.178:2818850799>
>
> But when I start the user-space subscriptions monitor from the
> topology_subscr_demo the ports output shows something like:
> 2818850753: connected to <1.1.178:2818850751> via {1,1}
> 2818850751: connected to <1.1.178:2818850753>
>
> So I'm missing one of the connections.
>
> The user-space subscription monitor is reporting correctly publish/withdraw
> events, e.g. when starting server_tipc from the demo. This tells me that
> either I'm doing something really wrong, or something is broken with the
> native interface in 2.6.24. If you want to try reproducing, the source is
> attached.
>
> Best regards,
> Erich
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
tipc-discussion mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tipc-discussion
