From owner-freebsd-stable@freebsd.org  Wed Dec  6 19:48:13 2017
Return-Path: <owner-freebsd-stable@freebsd.org>
Delivered-To: freebsd-stable@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id F26A5E8A4AC
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Wed,  6 Dec 2017 19:48:13 +0000 (UTC)
 (envelope-from lists@searchy.net)
Received: from mx.searchy.nl (mx.searchy.nl [IPv6:2a00:1280:8000:4::9])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id B80B1801B9
 for <freebsd-stable@freebsd.org>; Wed,  6 Dec 2017 19:48:13 +0000 (UTC)
 (envelope-from lists@searchy.net)
Received: from mx.searchy.nl (mx.searchy.nl [79.143.214.224])
 by mx.searchy.nl (Postfix) with ESMTP id 0E3D813980A
 for <freebsd-stable@freebsd.org>; Wed,  6 Dec 2017 19:48:10 +0000 (UTC)
X-Virus-Scanned: amavisd-new at mx.searchy.nl
X-Spam-Flag: NO
X-Spam-Score: -3
X-Spam-Level: 
X-Spam-Status: No, score=-3 tagged_above=-99 required=5 tests=[ALL_TRUSTED=-1, 
 BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 DKIM_VALID_AU=-0.1] autolearn=ham autolearn_force=no
Authentication-Results: mx.searchy.nl (amavisd-new); dkim=pass (1024-bit key)
 header.d=searchy.net
Received: from mx.searchy.nl ([79.143.214.224])
 by mx.searchy.nl (mx.searchy.nl [79.143.214.224]) (amavisd-new, port 10026)
 with ESMTP id eGJntJ_2x9rq for <freebsd-stable@freebsd.org>;
 Wed,  6 Dec 2017 19:48:08 +0000 (UTC)
Received: from [IPv6:2001:470:79dd:3:e032:57f7:1137:b6fe] (unknown
 [IPv6:2001:470:79dd:3:e032:57f7:1137:b6fe])
 by mx.searchy.nl (Postfix) with ESMTPSA id DD78A139808
 for <freebsd-stable@freebsd.org>; Wed,  6 Dec 2017 19:48:07 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=searchy.net;
 s=default; t=1512589688;
 bh=BkuxMPY9QHvFln2Zxvf9zAt2yMTeIrTrbhEbU79WPfI=;
 h=To:From:Subject:Date;
 b=u/DX0unicRdjUqez4GS4XyAg7gZ44jZXW+fXun5og9A9cgdrVgbDFRG7D7CSRLJPA
 cCh98hgXhd/uBrIU8D+N6VfBygnTW3iS4hlRZmCe5EErIDnidU0MQUROn8GE7jTu64
 CGnUWz/u5wTW4z1wzRc9ad0cSvlDJ0dVP1y3Hj8s=
To: FreeBSD Stable <freebsd-stable@freebsd.org>
From: "Frank de Bot (lists)" <lists@searchy.net>
Subject: Only 1 initiator per target
Message-ID: <75cbef26-1705-2d9f-585e-52b67c7231fb@searchy.net>
Date: Wed, 6 Dec 2017 20:48:07 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Firefox/52.0 SeaMonkey/2.49.1
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, 
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Dec 2017 19:48:14 -0000

Hi,

Is it possible to limit the number of initiators connected to a target
to 1 besides the 'initiator-name' config on the target? All servers
should be able to connect, but for safety I want to prevent a second
initiator from connecting to that target. A single iniator should be
able to connect several times if they use multi-path.


Regards,

Frank de Bot