Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

bsmconv(1m) [opensolaris man page]

bsmconv(1M)						  System Administration Commands					       bsmconv(1M)

NAME
bsmconv, bsmunconv - enable or disable Solaris Auditing SYNOPSIS
/etc/security/bsmconv [rootdir]... /etc/security/bsmunconv [rootdir]... DESCRIPTION
The bsmconv and bsmunconv scripts are used to enable or disable the BSM features on a Solaris system. The optional argument rootdir is a list of one or more root directories of diskless clients that have already been configured. See smdiskless(1M). To enable or disable BSM on a diskless client, a server, or a stand-alone system, logon as super-user to the system being converted and use the bsmconv or bsmunconv commands without any options. To enable or disable BSM on a diskless client from that client's server, logon to the server as super-user and use bsmconv, specifying the root directory of each diskless client you wish to affect. For example, the command: myhost# bsmconv /export/root/client1 /export/root/client2 enables BSM on the two machines named client1 and client2. While the command: myhost# bsmconv enables BSM only on the machine called myhost. It is no longer necessary to enable BSM on both the server and its diskless clients. After running bsmconv the system can be configured by editing the files in /etc/security. Each diskless client has its own copy of configu- ration files in its root directory. You might want to edit these files before rebooting each client. Following the completion of either script, the affected system(s) should be rebooted to allow the auditing subsystem to come up properly initialized. FILES
The following files are created by bsmconv: /etc/security/device_maps Administrative file defining the mapping of device special files to allocatable device names. /etc/security/device_allocate Administrative file defining parameters for device allocation. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsr | +-----------------------------+-----------------------------+ |Interface Stability |Obsolete Committed | +-----------------------------+-----------------------------+ SEE ALSO
auditconfig(1M), auditd(1M), audit_startup(1M), audit.log(4), audit_control(4), attributes(5) See the section on Solaris Auditing in System Administration Guide: Security Services. NOTES
bsmconv and bsmunconv are not valid in a non-global zone. These commands are Obsolete and may be removed and replaced with equivalent functionality in a future release of Solaris. SunOS 5.11 20 Jan 2009 bsmconv(1M)

Check Out this Related Man Page

bsmconv(1M)                                               System Administration Commands                                               bsmconv(1M)

NAME
bsmconv, bsmunconv - enable or disable the Basic Security Module (BSM) on Solaris SYNOPSIS
/etc/security/bsmconv [rootdir...] /etc/security/bsmunconv [rootdir...] DESCRIPTION
The bsmconv and bsmunconv scripts are used to enable or disable the BSM features on a Solaris system. The optional argument rootdir is a list of one or more root directories of diskless clients that have already been configured. See smdiskless(1M). To enable or disable BSM on a diskless client, a server, or a stand-alone system, logon as super-user to the system being converted and use the bsmconv or bsmunconv commands without any options. To enable or disable BSM on a diskless client from that client's server, logon to the server as super-user and use bsmconv, specifying the root directory of each diskless client you wish to affect. For example, the command: myhost# bsmconv /export/root/client1 /export/root/client2 enables BSM on the two machines named client1 and client2. While the command: myhost# bsmconv enables BSM only on the machine called myhost. It is no longer necessary to enable BSM on both the server and its diskless clients. After running bsmconv the system can be configured by editing the files in /etc/security. Each diskless client has its own copy of configu- ration files in its root directory. You might want to edit these files before rebooting each client. Following the completion of either script, the affected system(s) should be rebooted to allow the auditing subsystem to come up properly initialized. FILES
The following files are created by bsmconv: /etc/security/device_maps Administrative file defining the mapping of device special files to allocatable device names. /etc/security/device_allocate Administrative file defining parameters for device allocation. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsr | +-----------------------------+-----------------------------+ SEE ALSO
auditconfig(1M), auditd(1M), audit_startup(1M), audit.log(4), audit_control(4), attributes(5) NOTES
bsmconv and bsmunconv are not valid in a non-global zone. SunOS 5.10 26 May 2004 bsmconv(1M)
Man Page