On Tue, Jan 31, 2017 at 19:13:29 +0100, Axel Beckert wrote: > > > 2) So "--enable-ipv6" implies "--disable-ipv4"? If so, that option > > > should probably be renamed to "--only-ipv6" or similar to be > > > unambiguous. > > > > No, I probably should reformulate that text... When you call the > > fping binary 'fping6' (with a sym-link, for example), it is going to > > implicitely set the '-6' option at runtime. Bad idea? > > No, that's fine as it is what users would expect. But my comment was > about the compile time (configure) options. (Maybe adding the same for > "fping4" if IPv6 is set as default might be a nice addition.)
--enable-ipv6 does not imply --disable-ipv4. You can't disable IPv4 at compile time. The idea with 'fping6' is to maintain compatibility for systems that already use fping6. New systems should use preferably 'fping -4' or 'fping -6' if forcing IPv4/IPv6 is needed. Cheers David -- You received this message because you are subscribed to the Google Groups "fping-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to fping-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
