It's hard to think about SCO today, but Cahn continues to file. Now he wants Tanner to audit SCO's 401(k) plan. I'd prefer that he audit all the professionals' bills, personally.
If you had purchased $1,000 of AIG stock one year ago, you would have about $40.00 left. With Lehman, you have about $6.00 left. With Fannie or Freddie, you would have less than $5.00 left.
But, if you had purchased $1,000 worth of beer one year ago, and had drunk all of the beer, then turned... (4 Replies)
Hi, everybody
My system will be audit in a few weeks and I need to get a list about users accounts (create date/last login/first login) and I would like to extrat this informations in SCO 5.0.5. Exist a command that makes this?
Thanks for help me,
Tatiana :p (1 Reply)
auditd(1m)auditd(1m)NAME
auditd - Starts the DCE Audit Daemon.
SYNOPSIS
auditd [-t trail_file] [-a] [-s size] [-wrap] [-w svc_route] [-d debug_level]
OPTIONS
Specifies the pathname of the audit trail file used by the Audit daemon. The default path of the audit trail file is dcelo-
cal/var/aud/adm/central_trail. If an audit trail file name (instead of an absolute pathname) is specified, the file will be created in the
dcelocal/var/aud/adm/ directory. Audits the Audit daemon's control interface access. Sets a warning threshold on the size of the audit
trail file. The Audit daemon displays a warning message each time an audit record is appended to the audit trail after the threshold has
been reached. Wraps the recording of audit events to the beginning of the audit trail file when its size limit is reached. The default
action when the size limit has been reached is to stop auditing. Specifies where each level of serviceability messages are routed. The
svc_route argument is divided into three fields, separated by colons - the level, a routing identifier, and a routing parameter:
severity:how:where
See svcroute(5) for possible values for these fields. Specifies debugging level of sub-components. The debug_level argument contains four
fields separated by a colon:
component:flags:how:where
See svcroute(5) for possible values of these fields.
DESCRIPTION
The auditd command starts the Audit daemon. The Audit daemon must be run on the host before the audit clients.
The Audit daemon can only service audit clients that are on the host where it is running. Thus, an Audit daemon must be installed and run
on every host in the cell that has audit clients (audit clients include DCE servers and user-written application servers).
The Audit daemon has two functions. It maintains the filter files which are shared by all audit clients running on the host. It also pro-
vides an audit record logging service to these clients.
The Audit daemon runs under the local host's machine principal identity (host/hostname/self).
A DCE Host daemon (dced) must be running on the local host when auditd is started. Typically, dced and auditd are started at boot time.
The auditd process places itself in the background and sends messages indicating it is ready to service requests for updating or querying
filters and logging audit records.
Privileges Required
You must be logged into a privileged account (cell_admin or a member of the audit-admin group) to be able to run auditd.
EXAMPLES
The following example starts the Audit daemon using the default audit trail file (dcelocal/var/aud/adm/central_trail): $ auditd
The following example starts the Audit daemon and specifies my_trail_file as the audit trail file. $auditd -t my_trail_file
The following example starts the Audit daemon and specifies where each level of serviceability messages is going to be routed. $ auditd -w
FATAL:FILE:/dev/console -w NOTICE:FILE:/opt/dcelocal/var/audit/adm/svc_log
The following example starts the Audit daemon and specifies the debugging level. $ auditd -d 1,esl.9
RELATED INFORMATION aud(1m), audevents(1m), audfilter(1m), audtrail(1m), dcecp(1m).
auditd(1m)
