Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

dminfo(1m) [opensolaris man page]

dminfo(1M)						  System Administration Commands						dminfo(1M)

NAME
dminfo - report information about a device entry in a device maps file SYNOPSIS
dminfo [-v] [-a] [-f pathname] dminfo [-v] [-a] [-f pathname] -n dev -name... dminfo [-v] [-a] [-f pathname] -d dev -path... dminfo [-v] [-a] [-f pathname] -t dev -type... dminfo [-v] [-f pathname] -u dm -entry DESCRIPTION
dminfo reports and updates information about the device_maps(4) file. OPTIONS
The following options are supported -a Succeed if any of the requested entries are found. If used with -v, all entries that match the requested case(s) are printed. -d dev-path Search by dev-path. Search device_maps(4) for a device special pathname in the device_list field matching the dev-path argument. This option cannot be used with -n, -t or -u. -f pathname Use a device_maps file with pathname instead of /etc/security/device_maps. -n dev-name Search by dev-name. Search device_maps(4) for a device_name field matching dev-name. This option cannot be used with -d, -t or -u. -t dev-type Search by dev-type. Search device_maps(4) for a device_type field matching the given dev-type. This option cannot be used with -d, -n or -u. -u dm-entry Update the device_maps(4) file. This option is provided to add entries to the device_maps(4) file. The dm-entry must be a complete device_maps(4) file entry. The dm-entry has fields, as in the device_maps file. It uses the colon (:) as a field separator, and white space as the device_list subfield separators. The dm-entry is not made if any fields are missing, or if the dm-entry would be a duplicate. The default device maps file can be updated only by the super user. -v Verbose. Print the requested entry or entries, one line per entry, on the standard output. If no entries are specified, all are printed. EXIT STATUS
0 Successful completion. 1 Request failed. 2 Incorrect syntax. FILES
/etc/security/device_maps ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
bsmconv(1M), device_maps(4), attributes(5) NOTES
The functionality described in this man page is available only if the Solaris Auditing feature has been enabled. See bsmconv(1M) for more information. SunOS 5.11 16 Apr 2008 dminfo(1M)

Check Out this Related Man Page

device_maps(4)                                                     File Formats                                                     device_maps(4)

NAME
device_maps - device_maps file SYNOPSIS
/etc/security/device_maps DESCRIPTION
The device_maps file contains access control information about each physical device. Each device is represented by a one line entry of the form: device-name : device-type : device-list : where device-name This is an arbitrary ASCII string naming the physical device. This field contains no embedded white space or non- printable characters. device-type This is an arbitrary ASCII string naming the generic device type. This field identifies and groups together devices of like type. This field contains no embedded white space or non-printable characters. device-list This is a list of the device special files associated with the physical device. This field contains valid device special file path names separated by white space. The device_maps file is an ASCII file that resides in the /etc/security directory. Lines in device_maps can end with a `' to continue an entry on the next line. Comments may also be included. A `#' makes a comment of all further text until the next NEWLINE not immediately preceded by a `'. Leading and trailing blanks are allowed in any of the fields. The device_maps file must be created by the system administrator before device allocation is enabled. This file is owned by root, with a group of sys, and a mode of 0644. EXAMPLES
Example 1: A sample device_maps file # scsi tape st1: rmt: /dev/rst21 /dev/nrst21 /dev/rst5 /dev/nrst5 /dev/rst13 /dev/nrst13 /dev/rst29 /dev/nrst29 /dev/rmt/1l /dev/rmt/1m /dev/rmt/1 /dev/rmt/1h /dev/rmt/1u /dev/rmt/1ln /dev/rmt/1mn /dev/rmt/1n /dev/rmt/1hn /dev/rmt/1un /dev/rmt/1b /dev/rmt/1bn: FILES
/etc/security/device_maps SEE ALSO
allocate(1), bsmconv(1M), deallocate(1), dminfo(1M), list_devices(1) NOTES
The functionality described in this man page is available only if the Basic Security Module (BSM) has been enabled. See bsmconv(1M) for more information. SunOS 5.10 16 Jan 2001 device_maps(4)
Man Page