All of lore.kernel.org
 help / color / mirror / Atom feed
* command missing
@ 2007-04-23 14:46 xi-chen-0
  2007-04-23 15:05 ` Steve Grubb
  0 siblings, 1 reply; 3+ messages in thread
From: xi-chen-0 @ 2007-04-23 14:46 UTC (permalink / raw)
  To: linux-audit


Hi,

I've just started using auditing utilities to monitor filesystem events. I'm using audit-1.5.2
version. The problem is as follows:

If I do "auditctl -a entry,always -w /etc/passwd", then "grep man /etc/passwd", then "ausearch -f
passwd", the "grep" command is logged in the log file.

However, if I do "auditctl -a entry,always -w /etc", then "grep man /etc/passwd", then "ausearch -f 
passwd", the "grep" command is not logged in the log file. However, the "vim" command is recorded
if I use vim to open that "/etc/passwd" file.

Is this the preassumed behavior for the auditing system or have I misconfigured something? Any
clues on that?

ps: Is there a better way to monitor the whole filesystem behaviors, such as open, create, delete
syscalls, instead of just monitoring a single directory?

Thanks for your help,

Xi

^ permalink raw reply	[flat|nested] 3+ messages in thread
* command missing
@ 2007-04-20 22:28 xi-chen-0
  0 siblings, 0 replies; 3+ messages in thread
From: xi-chen-0 @ 2007-04-20 22:28 UTC (permalink / raw)
  To: linux-audit


Hi,

I've just started using auditing utilities to monitor filesystem events. I'm using audit-1.5.2
version. The problem is as follows:

If I do "auditctl -a entry,always -w /etc/passwd", then "grep man /etc/passwd", then "ausearch -f
passwd", the "grep" command is logged in the log file.

However, if I do "auditctl -a entry,always -w /etc", then "grep man /etc/passwd", then "ausearch -f 
passwd", the "grep" command is not logged in the log file. However, the "vim" command is recorded
if I use vim to open that "/etc/passwd" file.

Is this the preassumed behavior for the auditing system or have I misconfigured something? Any
clues on that?

ps: Is there a better way to monitor the whole filesystem behaviors, such as open, create, delete
syscalls, instead of just monitoring a single directory?

Thanks for your help,

Xi

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2007-04-23 15:05 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-04-23 14:46 command missing xi-chen-0
2007-04-23 15:05 ` Steve Grubb
  -- strict thread matches above, loose matches on Subject: below --
2007-04-20 22:28 xi-chen-0

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.