On Tue, 30 Apr 2013 19:23:44 -0500 "Craig A. Berry" <craig.a.berry@gmail.com> wrote: > I did more or less get to the bottom of the 11sockopts.t failure, > which is that the failing tests requires elevated privileges. Here's > a snippet of a debug session showing where things go south: ... > If you put "setsockopt broadcast privilege" into your favorite > search engine, you'll see that broadcast has been a privileged > operation for various systems at various times. We could put in a > skip for this test, but I don't know how necessary this feature is to > the functioning of IO::Socket::IP. Oh it's totally ancilliary; if this doesn't work on VMS it's quite simple to skip the test. I'm curious to know though - is this a new failure since 0.21, or has it existed for a while? I'm not really aware of anything I changed since 0.21 that would cause this. -- Paul "LeoNerd" Evans leonerd@leonerd.org.uk ICQ# 4135350 | Registered Linux# 179460 http://www.leonerd.org.uk/Thread Previous | Thread Next