From: Gabriel K. M. <isc...@sa...> - 2008-08-27 21:56:33
|
Team, The man (5) page on ietd.conf states: [MaxConnections <value>] Optional. Has to be set to "1" (in words: one). which is also the default. In my ietd.conf, I have no MaxConnections line, but I have half a dozen ESX hosts connected to it. I also want to create a couple of targets that are essentially temp space for data migrations, and I want to NOT limit which machines have access in initiators.{allow, deny}, but DO limit the # of connections to the given target to a single initiator, as the volumes will be NTFS & will be accessed primarily by Windows servers and workstations. Apparently the default of MaxConnections 1 is not enforced; if I put it in and specify MaxConnections 1 will it it fact work? Thanks, Gabriel |
From: Arne R. <ag...@po...> - 2008-08-29 15:38:09
|
Am Mittwoch, den 27.08.2008, 16:56 -0500 schrieb Gabriel K. McAtee: > Team, > The man (5) page on ietd.conf states: > > [MaxConnections <value>] > Optional. Has to be set to "1" (in words: one). which is also the > default. > > > In my ietd.conf, I have no MaxConnections line, but I have half a dozen > ESX hosts connected to it. I also want to create a couple of targets > that are essentially temp space for data migrations, and I want to NOT > limit which machines have access in initiators.{allow, deny}, but DO > limit the # of connections to the given target to a single initiator, > as the volumes will be NTFS & will be accessed primarily by Windows > servers and workstations. > > Apparently the default of MaxConnections 1 is not enforced; if I put it > in and specify MaxConnections 1 will it it fact work? MaxConnections specifies the # of connections that can be part of a session, i.e. MC/S (multiple conns per session). Since we don't support MC/S its always one. See the RFC for details. What you have in mind is to limit the number of sessions, which is not supported. HTH, Arne |
From: Gabriel K. M. <isc...@sa...> - 2008-08-29 16:10:15
|
Arne Redlich wrote: > Am Mittwoch, den 27.08.2008, 16:56 -0500 schrieb Gabriel K. McAtee: > >> Team, >> The man (5) page on ietd.conf states: >> >> [MaxConnections <value>] >> Optional. Has to be set to "1" (in words: one). which is also the >> default. >> >> >> In my ietd.conf, I have no MaxConnections line, but I have half a dozen >> ESX hosts connected to it. I also want to create a couple of targets >> that are essentially temp space for data migrations, and I want to NOT >> limit which machines have access in initiators.{allow, deny}, but DO >> limit the # of connections to the given target to a single initiator, >> as the volumes will be NTFS & will be accessed primarily by Windows >> servers and workstations. >> >> Apparently the default of MaxConnections 1 is not enforced; if I put it >> in and specify MaxConnections 1 will it it fact work? >> > > MaxConnections specifies the # of connections that can be part of a > session, i.e. MC/S (multiple conns per session). Since we don't support > MC/S its always one. See the RFC for details. > > What you have in mind is to limit the number of sessions, which is not > supported. > > HTH, > Arne > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Iscsitarget-devel mailing list > Isc...@li... > https://lists.sourceforge.net/lists/listinfo/iscsitarget-devel > > > OK, thanks! --Gabriel |