Re: EADDRINUSE setting up iSCSI portal on aarch64

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 12/17/2014 12:52 PM, Nicholas A. Bellinger wrote:
On Wed, 2014-12-17 at 20:25 +0000, Chris Moore wrote:
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.
Is there a way to turn off this automatic creation of portals in targetcli?

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.

I've opened https://github.com/agrover/targetcli-fb/issues/46 .

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.

beta feedback received loud and clear :-)

Thanks -- Regards -- Andy
--
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




[Index of Archives]     [Linux SCSI]     [Kernel Newbies]     [Linux SCSI Target Infrastructure]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Device Mapper]

  Powered by Linux