tnchkdb(1m) [opensolaris man page]
tnchkdb(1M) System Administration Commands tnchkdb(1M) NAME
tnchkdb - check file syntax of trusted network databases SYNOPSIS
/usr/sbin/tnchkdb [-h path] [-t path] [-z path] DESCRIPTION
tnchkdb checks the syntax of the tnrhtp, tnrhdb, and tnzonecfg databases. By default, the path for each file is: o /etc/security/tsol/tnrhtp o /etc/security/tsol/tnrhdb o /etc/security/tsol/tnzonecfg You can specify an alternate path for any or all of the files by specifying that path on the command line by using the -h (tnrhdb), -t (tnrhtp) and -z (tnzonecfg) options. The options are useful when testing a set of modified files before installing the files as new system databases. All three database files are checked for integrity. tnchkdb returns an exit status of 0 if all of the files are syntactically and, to the extent possible, semantically correct. If one or more files have errors, then an exit status of 1 is returned. If there are command line problems, such as an unreadable file, an exit status of 2 is returned. Errors are written to standard error. To avoid cascading errors, when there are errors in tnrhtp, the template names in tnrhdb are not validated. tnchkdb can be run at any label, but the standard /etc/security/tsol files are visible only in the global zone. OPTIONS
-h [ path ] Check path for proper tnrhdb syntax. If path is not specified, then check /etc/security/tsol/tnrhdb. -t [ path ] Check path for proper tnrhtp syntax. If path is not specified, then check /etc/security/tsol/tnrhtp. -z [ path ] Check path for proper tnzonecfg syntax. If path is not specified, then check /etc/security/tsol/tnzonecfg. EXAMPLES
Example 1 Sample Error Message The tnchkdb command checks for CIPSO errors. In this example, the admin_low template has an incorrect value of ADMIN_HIGH for its default label. # tnchkdb checking /etc/security/tsol/tnrhtp ... tnchkdb: def_label classification 7fff is invalid for cipso labels: line 14 entry admin_low tnchkdb: def_label compartments 241-256 must be zero for cipso labels: line 14 entry admin_low checking /etc/security/tsol/tnrhdb ... checking /etc/security/tsol/tnzonecfg ... FILES
/etc/security/tsol/tnrhdb Trusted network remote-host database /etc/security/tsol/tnrhtp Trusted network remote-host templates /etc/security/tsol/tnzonecfg Trusted zone configuration database ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWtsu | +-----------------------------+-----------------------------+ |Interface Stability |See below. | +-----------------------------+-----------------------------+ The command line is Committed. The output is Uncommitted. SEE ALSO
tnd(1M), tnctl(1M), attributes(5) How to Check the Syntax of Trusted Network Databases in Solaris Trusted Extensions Administrator's Procedures NOTES
The functionality described on this manual page is available only if the system is configured with Trusted Extensions. It is possible to have inconsistent but valid configurations of tnrhtp and tnrhdb when LDAP is used to supply missing templates. SunOS 5.11 20 Jul 2007 tnchkdb(1M)
Check Out this Related Man Page
tnd(1M) System Administration Commands tnd(1M) NAME
tnd - trusted network daemon SYNOPSIS
/usr/sbin/tnd [-p poll-interval] DESCRIPTION
The tnd (trusted network daemon) initializes the kernel with trusted network databases and also reloads the databases on demand from an LDAP server and local files. tnd follows the order specified in the nsswitch.conf file when loading configuration databases. tnd is started at the beginning of the boot process. tnd loads two databases into the kernel: the remote host database, tnrhdb and the remote-host template database, tnrhtp. These databases and their effect on the trusted network are described in their respective man pages. When the associated LDAP database or local databases are changed, tnd also updates the local kernel cache at the predetermined interval. If a local trusted networking database file is modified, the administrator should run tnchkdb(1M) to check the syntax, and should also run svcadm refresh svc:/network/tnd to initiate an immediate database scan by tnd. tnd is intended to be started from an smf(5) script and to run in the global zone. The following signals cause specific svcadm actions: SIGHUP Causes svcadm refresh svc:/network/tnd to be run. Initiates a rescan of the local and LDAP tnrhdb and tnrhtp databases. tnd updates the kernel database with any changes found. SIGTERM Causes svcadm disable svc:/network/tnd to be run. Terminates the tnd daemon. No changes are made to the kernel database. Running tnd in debug mode is determined by the value of the following service management facility (SMF) property: tnd/debug_level = 0 A value of 0, as above, prevents debug information from being collected; 1 turns on debugging. The default value is 0. Debug output is sent to the /var/tsol/tndlog log file. OPTIONS
-p poll-interval Set poll interval to poll-interval seconds. The default poll-interval is 1800 seconds (30 minutes). EXAMPLES
Example 1 Changing the Poll Interval The following command changes the polling interval to one hour, and puts this interval in the SMF repository. At the next boot, the tnd poll interval will be one hour. # svccfg -s network/tnd setprop tnd/poll_interval=3600 The following command changes the polling interval, but does not update the repository. At the next boot, the tnd poll interval remains the default, 30 minutes. # tnd -p 3600 FILES
/etc/security/tsol/tnrhdb Trusted network remote-host database /etc/security/tsol/tnrhtp Trusted network remote-host templates /etc/security/tsol/tnzonecfg Trusted zone configuration database /etc/nsswitch.conf Configuration file for the name service switch ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWtsu | +-----------------------------+-----------------------------+ |Interface Stability |See below. | +-----------------------------+-----------------------------+ The command invocation is Committed. The service is Private. SEE ALSO
svcs(1), svcadm(1M), tninfo(1M), tnctl(1M), tnchkdb(1M), nsswitch.conf(4), attributes(5), smf(5) How to Synchronize Kernel Cache With Network Databases in Solaris Trusted Extensions Administrator's Procedures NOTES
The functionality described on this manual page is available only if the system is configured with Trusted Extensions. The tnd service is managed by the service management facility, smf(5), under the service identifier: svc:/network/tnd The service's status can be queried by using svcs(1). Administrative actions on this service, such as requests to restart the daemon, can be performed using svcadm(1M), as in: svcadm restart svc:/network/tnd SunOS 5.11 15 May 2008 tnd(1M)