02-20-2012
How can I stop this???
I have a user ( and actually me too) getting this messages when the screen is idle, I need help on stopping this messages:
2012 Feb 20 13:30:22 servername Audit[11217]: LENGTH: "330" SESSIONID:[6] "339384" ENTRYID:[1] "1" STATEMENT:[1] "1" USERID:[10] "OPS$PT2ADM" USERHOST:[13] "zzzzzzzzzzz" ACTION:[3] "100" RETURNCODE:[1] "0" COMMENT$TEXT:[96] "Authenticated by: OS; Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=161.134.154.206)(PORT=21889))" OS$USERID:[6] "pt2adm" DBID:[10] "1102948819" PRIV$USED:[1] "5"
2012 Feb 20 13:30:22 zzzzzzzzzzz Audit[11217]: LENGTH: "203" SESSIONID:[6] "339384" ENTRYID:[1] "1" ACTION:[3] "101" RETURNCODE:[1] "0" LOGOFF$PREAD:[1] "0" LOGOFF$LREAD:[2] "27" LOGOFF$LWRITE:[1] "0" LOGOFF$DEAD:[1] "0" DBID:[10] "1102948819" SESSIONCPU:[1] "1"
2012 Feb 20 13:30:22 zzzzzzzzz Audit[11217]: LENGTH: "331" SESSIONID:[6] "339385" ENTRYID:[1] "1" STATEMENT:[1] "1" USERID:[5] "SAPR3" USERHOST:[13] "zzzzzzzzzzz" ACTION:[3] "100" RETURNCODE:[1] "0" COMMENT$TEXT:[102] "Authenticated by: DATABASE; Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=161.134.154.206)(PORT=21889))" OS$USERID:[6] "pt2adm" DBID:[10] "1102948819" PRIV$USED:[1] "5"
9 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
Am having trouble trying to stop the process below ...
bash# ps -eaf | grep "tape erase"
root 29715 1 0 05:16:22 ttyp1 00:00:00 tape erase /dev/rStp0
root 22464 20933 1 03:40:12 ttyp6 00:00:00 grep tape eraseI've tried ... `kill -9 29715` ... but still no luck.
Help... (8 Replies)
Discussion started by: Cameron
8 Replies
2. SCO
i hit ping to ping a server, and it keeps going.
how do you stop it? ctrl Z, D, C, nothing works. (2 Replies)
Discussion started by: BG_JrAdmin
2 Replies
3. UNIX for Advanced & Expert Users
Hi ,
I have one question, suppose i am a normal user and when i use 'w' command , it shows who is logged on and what they are doing .
Now i want to stop others users to know what i am doing accept the root ?
can i do this ?
thanks (5 Replies)
Discussion started by: mobile01
5 Replies
4. UNIX for Advanced & Expert Users
Hello,
I am hosting a site that someone is bouncing a huge amount of spam off of and I have not been able to find what file they are using to abuse my server.
Short of terminating the account and telling my customer to take a hike I am hoping someone can help me find the file that is being... (1 Reply)
Discussion started by: dorpan
1 Replies
5. Solaris
Hi,
I have replaced my current Intel PC machine with Solaris 10, it use to have windows XP.
I am sure alot of people already done this and i have seen Solaris running smoothly but having keyboard problem.
What is the equal keys in a QWERTY keyboard for selection <Stop+A> ?
Is there a... (5 Replies)
Discussion started by: tlee
5 Replies
6. AIX
Dears all
i have an AIX box in which i am facing a problem with a process as below:
/usr/dt/bin/dtexec -open 0 -ttprocid
and each time i am killing this process with "kill -9" then it run again after a while.
any ideas or solutions will be appreciated. (13 Replies)
Discussion started by: TheEngineer
13 Replies
7. UNIX for Dummies Questions & Answers
Hi All,
I am running parallel process as they all run the same JOBS and only thing which changes is the argument which ia passed.
I am doing it as follows
script.sh $1 &
script.sh $2 &
script.sh $3 &..
and so on.
Now each process has same set of JOBS which are to be executed. Now say... (1 Reply)
Discussion started by: Prashantckc
1 Replies
8. Solaris
I am using solaris x86 with a pc keyboard. i am trying to get to the ok prompt i have tried ctrl-break but it is not working , alt-break will not as well.
pls any thought? (4 Replies)
Discussion started by: seyiisq
4 Replies
9. UNIX for Dummies Questions & Answers
I have the following log file running since yesterday and its consuming so much of the disk space.
-rw-rw-r-- 1 dev dba 4543237120 Nov 10 09:00 load_run_file1_0.1111091224.lg
How do i kill this process. I don't have any idea of stopping this. Any help would be really appreciated.
... (3 Replies)
Discussion started by: bobby1015
3 Replies
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)