The UNIX and Linux Forums  
Hello and Welcome from United States to the UNIX and Linux Forums! Thank You for Visiting and Joining Our Global Community.

Go Back   The UNIX and Linux Forums > Top Forums > UNIX for Dummies Questions & Answers
.
google unix.com



UNIX for Dummies Questions & Answers If you're not sure where to post a UNIX or Linux question, post it here. All UNIX and Linux newbies welcome !!

More UNIX and Linux Forum Topics You Might Find Helpful
Thread Thread Starter Forum Replies Last Post
Symark Software’s PowerBroker 5.0 Selected as ''Hot Pick'' by ... - Business Wire (pr iBot UNIX and Linux RSS News 0 10-16-2007 05:00 AM
Powerbroker policy file advice needed yvs24 UNIX for Dummies Questions & Answers 1 06-13-2005 11:34 AM
Networking sysadmin/blocking/IM kymberm IP Networking 1 07-18-2003 04:51 PM
Sysadmin Day. killerserv News, Links, Events and Announcements 2 06-24-2002 09:17 PM

Closed Thread
English Japanese Spanish French German Portuguese Italian Dutch Swedish Russian Norwegian Hungarian Hebrew Danish Powered by Powered by Google
 
LinkBack Thread Tools Search this Thread Rate Thread Display Modes
  #1 (permalink)  
Old 07-08-2008
bcouchtx bcouchtx is offline
Registered User
  
 

Join Date: Jul 2008
Posts: 1
Question Parsing Powerbroker Logs for SysAdmin Changes (SOX)

I need to identify a list of AIX command strings that can be used to parse Powerbroker logs for changes that are being made by Unix SysAdmins. Need to filter out (as much as possible) inquiry or routine maintenance activity and concentrate on software/security changes.

This is for internal SOX monitoring (control self-assessment) - I am not an auditor.

Can anyone help? Suggestions?
  #2 (permalink)  
Old 07-08-2008
joeyg's Avatar
joeyg joeyg is offline Forum Staff  
modérateur
  
 

Join Date: Dec 2007
Location: Home of 17-time world champion Boston Celtics
Posts: 1,311
Wink Perhaps one thought...

You can grep -v the file to exclude data. For instance --

cat mylogfile | grep -v "routine"
or
cat mylogfile | grep -v "routine" >mylogfile.2

The first example will send the file to stdout (your screen normally) while the second example will direct the output to a new file. In both cases, any lines with the word "routine" would be excluded.
You could try the second approach, and then if you find another keyword to exclude re-do the command but with the next keyword, for example

cat mylogfile.2 | grep -v "ordinary" >mylogfile.3

Be aware of overall filespace, and remember to clean-up when done. Sometimes log files are very large. Perhaps this gives you a start?
Closed Thread

Bookmarks

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On




All times are GMT -4. The time now is 12:35 AM.


Powered by: vBulletin, Copyright ©2000 - 2006, Jelsoft Enterprises Limited. Language Translations Powered by .
vBCredits v1.4 Copyright ©2007 - 2008, PixelFX Studios
The UNIX and Linux Forums Content Copyright ©1993-2009. All Rights Reserved.Ad Management by RedTyger

Content Relevant URLs by vBSEO 3.2.0