iscsid(8) [netbsd man page]

ISCSID(8)						    BSD System Manager's Manual 						 ISCSID(8)

NAME

     iscsid -- interface to kernel iSCSI driver

SYNOPSIS

     iscsid [-n] [-d lvl]

DESCRIPTION

     The iSCSI initiator runs as a kernel driver, and provides access to iSCSI targets running across a network using the iSCSI protocol, RFC
     3720.  The iscsid utility itself interfaces to the kernel iSCSI driver, and also communicates, using isns(3), with the iSCSI name service
     running on other hosts to locate services and iSCSI instances.  In normal operation, iscsid is a standard daemon, and will detach from the
     controlling terminal using daemon(3) and then loops, reading requests, processing them, and sending responses.  Communication takes place
     over a Unix domain socket.  iscsid exits on receiving a terminate message, (no response to one that is sent to the kernel), or when an error
     occurs reading from or writing to the socket.

     The -d flag increases the debug level to lvl.  Any level above 0 causes iscsid to remain in the foreground, and increases the amount of debug
     output.  The -n flag makes the daemon single-threaded.

     It is envisaged that user-level communication take place with iscsid using the iscsictl(8) utility, rather than directly over its communica-
     tion socket.  An example of setting up the in-kernel iSCSI initiator is shown in iscsictl(8).

SEE ALSO

     daemon(3), isns(3), iscsictl(8)

HISTORY

     The iscsid utility appeared in NetBSD 6.0.

AUTHORS

     Alistair Crooks <agc@NetBSD.org> wrote this manual page.  The iscsid utility was contributed by Wasabi Systems, Inc.

BSD
								   May 27, 2012 							       BSD

ISCSI(4)						   BSD Kernel Interfaces Manual 						  ISCSI(4)

NAME

     iscsi -- iSCSI initiator

SYNOPSIS

     To compile this driver into the kernel, place the following line in the kernel configuration file:

	   device iscsi

     Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):

	   iscsi_load="YES"

DESCRIPTION

     The iscsi subsystem provides the kernel component of an iSCSI initiator.  The initiator is the iSCSI client, which connects to an iSCSI tar-
     get, providing local access to a remote block device.  The userland component is provided by iscsid(8) and both the kernel and userland are
     configured using iscsictl(8).  The iscsi subsystem is responsible for implementing the "Full Feature Phase" of the iSCSI protocol.

SYSCTL VARIABLES

     The following variables are available as both sysctl(8) variables and loader(8) tunables:

     kern.iscsi.ping_timeout
	     The number of seconds to wait for the target to respond to a NOP-Out PDU.	In the event that there is no response within that time
	     the session gets forcibly restarted.

     kern.iscsi.iscsid_timeout
	     The number of seconds to wait for ctld(8) to establish a session.	After that time iscsi will abort and retry.

     kern.iscsi.login_timeout
	     The number of seconds to wait for a login attempt to succeed.  After that time iscsi will abort and retry.

     kern.iscsi.maxtags
	     The maximum number of outstanding IO requests.

     kern.iscsi.fail_on_disconnection
	     Controls the behavior after an iSCSI connection has been dropped due to network problems.	When set to 1, a dropped connection causes
	     the iSCSI device nodes to be destroyed.  After reconnecting, they will be created again.  By default, the device nodes are left
	     intact.  While the connection is down all input/output operations are suspended, to be retried after the connection is reestablished.

SEE ALSO

     iscsi.conf(5), iscsictl(8), iscsid(8)

HISTORY

     The iscsi subsystem first appeared in FreeBSD 10.0.

AUTHORS

     The iscsi subsystem was developed by Edward Tomasz Napierala <trasz@FreeBSD.org> under sponsorship from the FreeBSD Foundation.

BSD
								September 11, 2014							       BSD