03-04-2014
AIX auditing
In our customer place somebody removed and PV from the server. I want the information like which user removed this PV.
Is there any way to get PV removal information.
When did the PV removed from the server ?
Whether AIX auding will help ?
Where i can get these information ?
Thank you
Last edited by sunnybee; 03-04-2014 at 01:45 PM..
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi all,
Have been asked to learn up on providing Sytem Auditing on two SCO boxes.
Where should I start and what pointers can anyone provide.
Whilst I'm learning to look after these two SCO boxes, I'm also to eventually look after three Compaq DS20E True64 Unix boxes also in the near future. (2 Replies)
Discussion started by: Cameron
2 Replies
2. AIX
Hi,
What's the best way to turn on the auditing in AIX 4.3? I'm in an environment where root password are shared with many users.
Can sudoers member be audited properly?
Thanks (1 Reply)
Discussion started by: itik
1 Replies
3. AIX
can someone help me find out the impact of enabling audting on the entire root filesystem. does it have a major hit on the overall performance of the system
Thanks so much (0 Replies)
Discussion started by: iam
0 Replies
4. UNIX for Advanced & Expert Users
:)I need a little help. I have sent all of our logs to our log server, but I can't send the audit logs that are in /var/log/audit.log. Can someone give me some type of idea to transfer these logs.
Thank You (2 Replies)
Discussion started by: aojmoj
2 Replies
5. AIX
I have a question relating with AIX auditing Question is can we set Auditing on a particular file in AIX for a particular application only?
Let say I have a file name "info.jar" and I have three application named APP1, APP2 & APP3 which are accessing that file so I want to know that which... (0 Replies)
Discussion started by: m_raheelahmed
0 Replies
6. AIX
i have sucessfully enable the auditing on AIX with adding som onjects.
but when i go for
auditpr -v < /audit/trail
vlets say i reset audit at last dat 5 pm
auditpr -v < /audit/trail
will show up to last day 5 pm.
i have to reset audit every time to check latest logs.
please... (3 Replies)
Discussion started by: prashantjain07
3 Replies
7. AIX
Hi All,
i've a problem on a AIX server with audit config...
when i start the audit i receive this error:
root@****:/etc/security/audit > /usr/sbin/audit start
Audit start cleanup: The system call does not exist on this system.
** failed setting kernel audit objects
I don't understand... (0 Replies)
Discussion started by: Zio Bill
0 Replies
8. AIX
can some give some tips, most common security issues or and kind of advice about auditing aix system?
regards (2 Replies)
Discussion started by: bongo
2 Replies
9. AIX
I am trying to find out the information of my local desktop when i use putty to login to an AIX server.
This is what I do:
1. login to my PC
2. take a putty session to an AIX server
Can i get information of my local desktop from the AIX server ? Is there a command available ?
Thanks (8 Replies)
Discussion started by: Nagesh_1985
8 Replies
10. AIX
Hi All
I need your help to configure Aix to send logs to Qradar, I did all the methods that mentioned in IBM website and no use, Plz Help,,
The Logs should I receive from Aix and display in Qradar is (create user delete user changing in privileges....etc )
my skype account
khaled_ly84
... (4 Replies)
Discussion started by: khaled_ly84
4 Replies
LEARN ABOUT SUNOS
nisrmdir
nisrmdir(1) User Commands nisrmdir(1)
NAME
nisrmdir - remove NIS+ directories
SYNOPSIS
nisrmdir [-if] [-s hostname] dirname
DESCRIPTION
nisrmdir deletes existing NIS+ subdirectories. It can remove a directory outright, or simply remove replicas from serving a directory.
This command modifies the object that describes the directory dirname, and then notifies each replica to remove the directory named
dirname. If the notification of any of the affected replicas fails, the directory object is returned to its original state unless the -f
option is present.
This command will fail if the NIS+ master server is not running.
OPTIONS
The following options are supported:
-i Interactive mode. Like the system rm(1) command the nisrmdir command will ask for confirmation prior to removing a direc-
tory. If the name specified by dirname is a non-fully qualified name this option is forced on. This prevents the removal of
unexpected directories.
-f Force the command to succeed even though it may not be able to contact the affected replicas. This option should be used
when a replica is known to be down and will not be able to respond to the removal notification. When the replica is finally
rebooted it will read the updated directory object, note that it is no longer a replica for that directory, and stop
responding to lookups on that directory. Cleanup of the files that held the now removed directory can be accomplished manu-
ally by removing the appropriate files in the /var/nis directory. See nisfiles(4) for more information.
-s hostname Specify that the host hostname should be removed as a replica for the directory named dirname. If this option is not
present all replicas and the master server for a directory are removed and the directory is removed from the namespace.
Special per-server and per-directory access restrictions may apply when this command updates the serving lists of the affected NIS+
servers. For more information, see nisopaccess(1).
OPERANDS
The following operand is supported:
dirname An existing NIS+ directory.
EXAMPLES
Example 1: Using the nisrmdir Command
To remove a directory bar under the foo.com. domain, one would use the command:
example% nisrmdir bar.foo.com.
To remove a replica that is serving directory bar.foo.com. one would use the command:
example% nisrmdir -s replica.foo.com. bar.foo.com.
To force the removal of directory bar.foo.com. from the namespace, one would use the command:
example% nisrmdir -f bar.foo.com.
ENVIRONMENT VARIABLES
NIS_PATH If this variable is set, and the NIS+ directory name is not fully qualified, each directory specified will be searched
until the directory is found. See nisdefaults(1).
EXIT STATUS
The following exit values are returned:
0 Successful operation.
1 Operation failed.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWnisu |
+-----------------------------+-----------------------------+
SEE ALSO
nis+(1), nisdefaults(1), nisopaccess(1),nisrm(1), nisfiles(4), attributes(5)
NOTES
NIS+ might not be supported in future releases of the SolarisTM Operating Environment. Tools to aid the migration from NIS+ to LDAP are
available in the Solaris 9 operating environment. For more information, visit http://www.sun.com/directory/nisplus/transition.html.
SunOS 5.10 10 Dec 2001 nisrmdir(1)