ctl(4) [freebsd man page]
CTL(4) BSD Kernel Interfaces Manual CTL(4) NAME
ctl -- CAM Target Layer SYNOPSIS
To compile this driver into the kernel, place the following line in your kernel configuration file: device ctl Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): ctl_load="YES" DESCRIPTION
The ctl subsystem provides SCSI disk and processor emulation. It supports features such as: o Disk and processor device emulation o Tagged queueing o SCSI task attribute support (ordered, head of queue, simple tags) o SCSI implicit command ordering support o Full task management support (abort, LUN reset, target reset, etc.) o Support for multiple ports o Support for multiple simultaneous initiators o Support for multiple simultaneous backing stores o Support for VMWare VAAI: COMPARE AND WRITE, XCOPY, WRITE SAME, and UNMAP commands o Support for Microsoft ODX: POPULATE TOKEN/WRITE USING TOKEN, WRITE SAME, and UNMAP commands o Persistent reservation support o Mode sense/select support o Error injection support o All I/O handled in-kernel, no userland context switch overhead It also serves as a kernel component of the native iSCSI target. SEE ALSO
ctladm(8), ctld(8), ctlstat(8) HISTORY
The ctl subsystem first appeared in FreeBSD 9.1. AUTHORS
The ctl subsystem was written by Kenneth Merry <ken@FreeBSD.org>. BSD
October 23, 2014 BSD
Check Out this Related 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