On Wed, 2014-12-17 at 20:25 +0000, Chris Moore wrote: > I've started running into this too - I think it happened when I switched to testing with RHEL 7.1. > The auto create of a portal at 0.0.0.0 is really killing me. > > I create Target1 and it auto creates the 0.0.0.0:3260 portal. I want my portal at 192.168.1.1:3260 > but I can't create it because the auto portal is already using that port. > > I can delete the portal at 0.0.0.0:3260, then create mine at 192.168.1.1:3260. But then when > I try to create Target2 it fails because it's trying to create a portal at 0.0.0.0:3260 for that one > and it's getting EADDRINUSE. > > Is there a way to turn off this automatic creation of portals in targetcli? > > Chris > Btw, upstream targetcli doesn't do this. IIRC this is hardcoded assumption into targetcli-fb code, and can't be disabled via a 'set global' parameter. Here's the offending line: https://github.com/agrover/targetcli-fb/blob/master/targetcli/ui_target.py#L328 However, you should be able to just comment that bit out. --nab -- 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
