ctld(8) [freebsd man page]
CTLD(8) BSD System Manager's Manual CTLD(8) NAME
ctld -- CAM Target Layer / iSCSI target daemon SYNOPSIS
ctld [-d] [-f config-file] DESCRIPTION
The ctld daemon is responsible for managing the CAM Target Layer configuration, accepting incoming iSCSI connections, performing authentica- tion and passing connections to the kernel part of the native iSCSI target. Upon startup, the ctld daemon parses the configuration file and exits, if it encounters any errors. Then it compares the configuration with the kernel list of LUNs managed by previously running ctld instances, removes LUNs no longer existing in the configuration file, and creates new LUNs as necessary. After that it listens for the incoming iSCSI connections, performs authentication, and, if successful, passes the connections to the kernel part of CTL iSCSI target, which handles it from that point. When it receives a SIGHUP signal, the ctld reloads its configuration and applies the changes to the kernel. Changes are applied in a way that avoids unnecessary disruptions; for example removing one LUN does not affect other LUNs. When exiting gracefully, the ctld daemon removes LUNs it managed and forcibly disconnects all the clients. Otherwise - for example, when killed with SIGKILL - LUNs stay configured and clients remain connected. To perform administrative actions that apply to already connected sessions, such as forcing termination, use ctladm(8). The following options are available: -f config-file Specifies the name of the configuration file. The default is /etc/ctl.conf. -d Debug mode. The server sends verbose debug output to standard error, and does not put itself in the background. The server will also not fork and will exit after processing one connection. This option is only intended for debugging the target. FILES
/etc/ctl.conf The configuration file for ctld. The file format and configuration options are described in ctl.conf(5). /var/run/ctld.pid The default location of the ctld PID file. EXIT STATUS
The ctld utility exits 0 on success, and >0 if an error occurs. SEE ALSO
ctl(4), ctl.conf(5), ctladm(8) HISTORY
The ctld command appeared in FreeBSD 10.0. AUTHORS
The ctld was developed by Edward Tomasz Napierala <trasz@FreeBSD.org> under sponsorship from the FreeBSD Foundation. BSD
November 9, 2014 BSD
Check Out this Related Man Page
ISCONTROL(8) BSD System Manager's Manual ISCONTROL(8) NAME
iscontrol -- login/negotiator/control for an iSCSI initiator session SYNOPSIS
iscontrol [-dv] [-c file [-n nickname]] [-p pidfile] [-t target] [variable=value] DESCRIPTION
This command, along with its kernel counterpart iscsi_initiator(4), is obsolete. Users are advised to use iscsictl(8) instead. Internet SCSI (iSCSI) is a network protocol standard, that allows the use of the SCSI protocol over TCP/IP networks, the iscontrol program is the userland side of an iSCSI session, see iscsi_initiator(4). It has 2 modes of operation, if -d (discovery session) is specified, it will print out the target names returned by the target and exit. In the second mode, it will, after a successful login/negotiation, run in daemon mode, monitoring the connection, and will try to reconnect in case of a network/target failure. It will terminate/logout the session when a SIGHUP signal is received. The flags are as follows: -c file a file containing configuration key-options, see iscsi.conf(5). -d do a discovery session and exit. -n nickname if -c file is specified, then search for the block named nickname in that file, see iscsi.conf(5). -p pidfile will write the process ID of the session to the specified pidfile -t target the target's IP address or name. -v verbose mode. variable=value see iscsi.conf(5) for the complete list of variables/options and their possible values. EXAMPLES
iscontrol -dt myiscsitarget will start a discovery session with the target and print to stdout the list of available targetnames/targetadresses. Note: this listing does not necessarily mean availability, since depending on the target configuration, a discovery session might not need login/access permission, but a full session certainly does. iscontrol -c /etc/iscsi.conf -n myiscsi will read options from /etc/iscsi.conf, use the targetaddress found in the block nicknamed myiscsi, login and negotiate whatever options are specified, and start an iscsi-session. SEE ALSO
da(4), iscsi_initiator(4), sa(4), iscsi.conf(5), camcontrol(8), iscsictl(8) STANDARDS
RFC 3720 BUGS
iscontrol should probably load the iscsi_initiator module if needed. Not all functions/specifications have been implemented yet, noticeably missing are the Task Management Functions. The error recovery, though not fully compliant does a brave effort to recover from network disconnects. BSD
October 9, 2014 BSD