![]() |
|
|
|
|
|||||||
| Forums | Portal | Register | Forum Rules | FAQ | Contribute | Members List | Arcade | Search | Today's Posts | Mark Forums Read |
| UNIX for Advanced & Expert Users Advanced UNIX and Linux questions go here. Expert-to-Expert. |
|
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| how to write modifications in to two tables | naveeng.81 | Shell Programming and Scripting | 0 | 04-09-2008 10:26 AM |
| question about testing in shell programming(modifications were made) | thungmail | Shell Programming and Scripting | 2 | 04-08-2008 12:51 PM |
| my shell script (file modifications) | whizkidash | Shell Programming and Scripting | 2 | 03-24-2008 12:50 PM |
| list files with modifications <15 minutes | tom_k_mishra | UNIX for Dummies Questions & Answers | 2 | 11-10-2005 11:10 PM |
| In Line File Modifications: Search and Replace | Shakey21 | Shell Programming and Scripting | 2 | 11-20-2001 01:21 PM |
|
|
Submit Tools | LinkBack | Thread Tools | Search this Thread | Display Modes |
|
#1
|
|||
|
|||
|
Tracing file modifications
Hello all!
Is there a way or a utility to trace any kind of file changes in a particular directory on any UNIX machine? The purpose is that in Unix, there are multiple ways of opening and making changes to a file. But internally, there must be something common (a single pipe, etc.) that is being refered by every application or command that performs file modifications. How can I get to that? |
| Forum Sponsor | ||
|
|
|
#2
|
||||
|
||||
|
Some versions of unix have c2 security features which can trace any system call made by any process. I don't know of any other way to to do what you want. The kernel knows whenever a file is changed, but there are no interfaces to provide the info except for c2 auditing. Beyond that you would need to rewrite the kernel.
|
|
#3
|
||||
|
||||
|
There is a product called ETrust that is available from Computer Associates, maybe you could look that up.
|
|
#4
|
|||
|
|||
|
Tripwire is a possibility for tracking file system intergrity. Worth looking at anyway.
|
|||
| Google The UNIX and Linux Forums |