On Fri, Feb 3, 2012 at 11:47 PM, Roland Dreier <roland@xxxxxxxxxxxxxxx> wrote: > It seems it might be better to just deal with systemd and only bind network > addresses after the network is up. The issue is if specific IP address(es) are defined for iSCSI portals. Currently, sys admins will have to do non-obvious special configuration to make this work. With my patch, no special configuration changes are required. It just works. > How does the NFS server handle things? Presumably the same issue exists > there, and I would hope NFS serving works with systemd. If a server binds to 0.0.0.0 or loopback, like the NFS server, the issue doesn't exist The issue comes into play for any server that wishes to bind to a /specific/ IP address. The recommended solution for all servers (userland or kernel based) is to use the IP_FREEBIND socket option. The IP_FREEBIND feature was added to Linux in 2001 specifically to address this situation -- we should use it. Dax Kelson -- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
