[Click] FromPacket: read: Bad File Descriptor error

[Beyers Cronje]

Hi Hippo,

Just this week I've started looking into using the socket elements of click.
I might be wrong, but as far as I can see you should use the socket element
and not to/fromsocket. From the documentation: "This element exists only for
backward compatibility. See the more general
*Socket*(n)<http://pdos.csail.mit.edu/click/doc/Socket.n.html>implementation
for details, and for supported keyword arguments. A
*FromSocket* is equivalent to a
*Socket*(n)<http://pdos.csail.mit.edu/click/doc/Socket.n.html>with the
CLIENT keyword set to FALSE or a
*Socket*(n) <http://pdos.csail.mit.edu/click/doc/Socket.n.html> with no
inputs."

Cheers

Beyers

On 2/2/06, Hippi Do <hippido at yahoo.com> wrote:
>
> Hi,
>
>   I'm trying to implement interprocess communication between an external
> application and Click.  The external application is executing on the same
> machine as Click.  The Click configuration file is as follows:
>
>   ------ Click configuration --------
>   FromSocket(UDP, 0.0.0.0, 3000) -> MyElement;
>   ------------------------------------------
>
>   The external application periodically sends a UDP message to the
> localhost at port 3000.  When the message is sent, Click continuously prints
> out the error, "FromPacket: read: Bad File Descriptor".  I appreciate
> pointers on how to get fix this problem.  Also, please point me to any
> examples you might have on how to communicate between Click and an external
> application.
>
>   Thanks in advance,
>   Hippi Do
>
>
> ---------------------------------
> Do you Yahoo!?
> With a free 1 GB, there's more in store with Yahoo! Mail.
> _______________________________________________
> click mailing list
> click at amsterdam.lcs.mit.edu
> https://amsterdam.lcs.mit.edu/mailman/listinfo/click
>