Awesome, thanks! I've got another minor issue... The create command for creating a TPG takes a positive integer. If you inadvertently do something dumb, like I did, and give it something that's not an integer (like "tpg2") you get dumped out with a stack trace. Want me to file an issue for that as well? Chris > -----Original Message----- > From: Andy Grover [mailto:agrover@xxxxxxxxxx] > Sent: Wednesday, December 17, 2014 1:08 PM > To: Nicholas A. Bellinger; Chris Moore > Cc: Noah Watkins; target-devel@xxxxxxxxxxxxxxx > Subject: Re: EADDRINUSE setting up iSCSI portal on aarch64 > > 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 ��.n��������+%������w��{.n����j� ����{ay� ʇڙ���f���h������_�(�階�ݢj"��������G����?���&��
