Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

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

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

NAME
iscsid - establish iSCSI connections SYNOPSIS
iscsid [ -b bindingfile ] [ -d ] [ -f configfile ] [ -l basedir ] [ -m mode ] [ -n ] DESCRIPTION
iscsid establishes connections with iSCSI targets defined in /etc/iscsi.conf. Once the Linux iSCSI driver is activated, a discovery process for iSCSI storage devices will proceed as follows: - The iSCSI daemon requests available iSCSI targets from the iSCSI target, and passes the information discovered to the iSCSI kernel module. - The iSCSI kernel module establishes connections to the targets. - Linux queries targets for device information. - Linux creates a mapping from SCSI device nodes to iSCSI targets. iscsid should be started after networking is configured and stopped after all iSCSI devices have been unmounted. Warning: Data corruption can occur if you do not unmount iSCSI devices before disabling network interfaces! DEVICE NAMES
Because Linux assigns SCSI device nodes dynamically whenever a SCSI logical unit is detected, the mapping from device nodes (e.g /dev/sda, /dev/sdb) to iSCSI targets and logical units may vary. Variations in process scheduling and network delay may result in iSCSI targets being mapped to different SCSI device nodes every time the driver is started. Because of this variability, configuring applications or operating system utilities to use the standard SCSI device nodes to access iSCSI devices may result in SCSI commands being sent to the wrong target or logical unit. To provide a more reliable namespace, the iSCSI driver will scan the system to determine the mapping from SCSI device nodes to iSCSI tar- gets, and then create a tree of directories and symbolic links under /dev/iscsi to make it easier to use a particular iSCSI target's logi- cal units. TARGET BINDINGS
The iSCSI driver automatically maintains a bindings file /var/iscsi/bindings. This file contains persistent bindings to ensure that the same iSCSI bus and target id number are used for every iSCSI session to a particular iSCSI TargetName, no matter how many times the driver is restarted. This feature ensures that the SCSI numbers in the device symlinks described above will always map to the same iSCSI target. Note that because of the way Linux dynamically allocates SCSI device nodes as SCSI devices are found, the driver does not and can not ensure that any particular SCSI device node (e.g. /dev/sda) will always map to the same iSCSI TargetName. The symlinks described in the section on Device Names are intended to provide a persistent device mapping for use by applications and fstab files, and should be used instead of direct references to particular SCSI device nodes. If the bindings file grows too large, lines for targets that no longer exist may be manually removed by editing the file. Manual editing should not normally be needed, since the driver can maintain up to 65535 different bindings. OPTIONS
-b bindingfile Specify an alternative bindings file instead of /var/iscsi/bindings, which is the default. -d Turns on debug mode. Each occurence of -d will increment the debug level by one. The default is zero (off). -f configfile Specify an alternative configuration file instead of /etc/iscsi.conf, which is the default. -l basedir Specify the base directory under which to build a tree of directories containing symlinks to SCSI device nodes, in a manner similar to the devfs Linux kernel option. Using these symlinks hides variations in the mapping from SCSI device nodes to SCSI device id numbers. -m mode Specify the directory permission mode (in octal) to use when creating directories. -n Avoid auto-backgrounding. -v Print version and exit. SIGNALS
iscsid reacts to a set of signals. You may easily send a signal to iscsid using the following: kill -SIGNAL `cat /var/run/iscsid.pid` SIGTERM The daemon and all of it's children will die. SIGHUP sent to the main daemon process will restart all discovery processes and reprobe LUNs on all targets. iscsid and all of it's chil- dren will die after shutting down all of the kernel's iSCSI sessions. SIGCHLD Wait for children. NOTES
The iSCSI Driver for Linux provides IP access to a maximum of sixteen remote SCSI targets. Each target will be probed for up to 256 LUNs, until the Linux kernel's limit of SCSI devices has been reached. The iSCSI drivers, README files, and example configuration files are available on the Linux-iSCSI homepage at: http://linux-iscsi.sourceforge.com/ <http://linux-iscsi.sourceforge.com/> FILES
/etc/iscsi.conf target address and LUN configuration /var/run/iscsi.pid the process id of the running daemon /var/iscsi/bindings persistent bus and target id bindings for iSCSI TargetNames /proc/scsi/iscsi information about iSCSI devices /dev/iscsi a directory tree containing symlinks to iSCSI device nodes. SEE ALSO
iscsi.conf(5) $Revision: 1.8 $ $Date: 2002/09/20 19:27:32 $ ISCSID(8)
Man Page