Il giorno 26/set/2012, alle ore 13:41, C Anthony Risinger <[email protected]> ha scritto:
> On Wed, Sep 26, 2012 at 12:15 AM, Roberto De Ioris <[email protected]> wrote: >> On Tue, Sep 25, 2012 at 11:58 PM, C Anthony Risinger <[email protected]> wrote: >>> >>> i've just started using the UDP multicast socket logging: >>> >>> [..] >>> >>> would it be possible to detect (first 3 chars?) if multicast address, >>> and set accordingly? [...] >> >> In 1.3 that feature already exists. You may want to try -rc4 > > bah! i thought that's what i did, but it seems i was in fact running > 1.2.6 ... thanks! > > anyways, while it does work as advertised, there are a couple things i > noticed ... both of which may simply be non-issues (i'm noob at the C > level): > > - binding to socket before setting IP_ADD_MEMBERSHIP and IP_MULTICAST_LOOP? I am not quite sure about that, does it changes something ? > > - not setting SO_REUSEADDR (like TCP sockets)? when i was using socat > i could bind as many as i liked, not so with uwsgi :-( seems (extremely) reasonable, i will apply it > > ... the latter one is all i care about, but on a related note, > wouldn't it also be useful to set IP_MULTICAST_TTL to something > greater than the default of 1? else we can't get out of the subnet ... > eg. my use case is listening to server logs across VPN, so at least 1 > hop for sure; maybe TTL could be configurable or something ... > > ... or perhaps some other way/syntax to set arbitrary socket options, > eg. copy socat interface? one could use the `=<N>` construct used > elsewhere in configs, say: > i will check it , but i suppose a --multicast-ttl option will be the easiest choice for now -- Roberto De Ioris http://unbit.it JID: [email protected] _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
