Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

ses(4) [debian man page]

SES(4)							   BSD Kernel Interfaces Manual 						    SES(4)

NAME

     ses -- SCSI Environmental Services driver

SYNOPSIS

     device ses

DESCRIPTION

     The ses driver provides support for all SCSI devices of the environmental services class that are attached to the system through a supported
     SCSI Host Adapter, as well as emulated support for SAF-TE (SCSI Accessible Fault Tolerant Enclosures).  The environmental services class gen-
     erally are enclosure devices that provide environmental information such as number of power supplies (and state), temperature, device slots,
     and so on.

     A SCSI Host adapter must also be separately configured into the system before a SCSI Environmental Services device can be configured.

KERNEL CONFIGURATION

     It is only necessary to explicitly configure one ses device; data structures are dynamically allocated as devices are found on the SCSI bus.

     A separate option, SES_ENABLE_PASSTHROUGH, may be specified to allow the ses driver to perform functions on devices of other classes that
     claim to also support ses functionality.

IOCTLS

     The following ioctl(2) calls apply to ses devices.  They are defined in the header file <cam/scsi/scsi_ses.h> (q.v.).

     SESIOC_GETNOBJ	Used to find out how many ses objects are driven by this particular device instance.

     SESIOC_GETOBJMAP	Read, from the kernel, an array of SES objects which contains the object identifier, which subenclosure it is in, and the
			ses type of the object.

     SESIOC_GETENCSTAT	Get the overall enclosure status.

     SESIOC_SETENCSTAT	Set the overall enclosure status.

     SESIOC_GETOBJSTAT	Get the status of a particular object.

     SESIOC_SETOBJSTAT	Set the status of a particular object.

     SESIOC_GETTEXT	Get the associated help text for an object (not yet implemented).  ses devices often have descriptive text for an object
			which can tell you things like location (e.g, "left power supply").

     SESIOC_INIT	Initialize the enclosure.

EXAMPLE USAGE

     The files contained in <usr/share/examples/ses> show simple mechanisms for how to use these interfaces, as well as a very stupid simple moni-
     toring daemon.

FILES

     /dev/sesN	    The Nth SES device.

DIAGNOSTICS

     When the kernel is configured with DEBUG enabled, the first open to an SES device will spit out overall enclosure parameters to the console.

HISTORY

     The ses driver was written for the CAM SCSI subsystem by Matthew Jacob.  This is a functional equivalent of a similar driver available in
     Solaris, Release 7.

BSD
								 January 29, 2000							       BSD

Check Out this Related Man Page

PASS(4) 						   BSD Kernel Interfaces Manual 						   PASS(4)

NAME

     pass -- CAM application passthrough driver

SYNOPSIS

     device pass

DESCRIPTION

     The pass driver provides a way for userland applications to issue CAM CCBs to the kernel.

     Since the pass driver allows direct access to the CAM subsystem, system administrators should exercise caution when granting access to this
     driver.  If used improperly, this driver can allow userland applications to crash a machine or cause data loss.

     The pass driver attaches to every SCSI device found in the system.  Since it attaches to every device, it provides a generic means of access-
     ing SCSI devices, and allows the user to access devices which have no "standard" peripheral driver associated with them.

KERNEL CONFIGURATION

     It is only necessary to configure one pass device in the kernel; pass devices are automatically allocated as SCSI devices are found.

IOCTLS

     CAMIOCOMMAND     This ioctl takes most kinds of CAM CCBs and passes them through to the CAM transport layer for action.  Note that some CCB
		      types are not allowed through the passthrough device, and must be sent through the xpt(4) device instead.  Some examples of
		      xpt-only CCBs are XPT_SCAN_BUS, XPT_DEV_MATCH, XPT_RESET_BUS, XPT_SCAN_LUN, XPT_ENG_INQ, and XPT_ENG_EXEC.  These CCB types
		      have various attributes that make it illogical or impossible to service them through the passthrough interface.

     CAMGETPASSTHRU   This ioctl takes an XPT_GDEVLIST CCB, and returns the passthrough device corresponding to the device in question.  Although
		      this ioctl is available through the pass driver, it is of limited use, since the caller must already know that the device in
		      question is a passthrough device if they are issuing this ioctl.	It is probably more useful to issue this ioctl through the
		      xpt(4) device.

FILES

     /dev/passn  Character device nodes for the pass driver.  There should be one of these for each device accessed through the CAM subsystem.

DIAGNOSTICS

     None.

SEE ALSO

     cam(3), cam(4), cam_cdbparse(3), xpt(4), camcontrol(8)

HISTORY

     The CAM passthrough driver first appeared in FreeBSD 3.0.

AUTHORS

     Kenneth Merry <ken@FreeBSD.org>

BUGS

     It might be nice to have a way to asynchronously send CCBs through the passthrough driver.  This would probably require some sort of
     read/write interface or an asynchronous ioctl interface.

BSD
								 October 10, 1998							       BSD
Man Page