All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loulwa Salem <loulwas@us.ibm.com>
To: linux-audit@redhat.com
Subject: another issue with Audit
Date: Mon, 24 Apr 2006 10:21:55 -0500	[thread overview]
Message-ID: <444CED13.1070900@us.ibm.com> (raw)

This is a really strange problem .. seems like I have a knack to finding those.

I am running lspp.18 kernel (SELinux in permissive mode), audit-1.2.1 on an 
x86_64 system.

Here is what is happening .. someone else please try this and let me know if you 
see the same problem...

# auditctl -w /tmp/file1	>> works fine
# auditctl -w /tmp/file6
Error sending add rule request (File exists)
# auditctl -w /tmp/afile
Error sending add rule request (File exists)
# auditctl -w /tmp/newfile	>> works fine
# auditctl -w /tmp/thefile
Error sending add rule request (File exists)

Here is what I noticed from this pattern ... as long as the length of the file 
name I am adding watch on is the same, it says the watch already exists... So I 
tried something else to see if only the file name matters or the whole path 
length ...

# mkdir /foo
# auditctl -w /foo/file3	>> notice .. same length as /tmp/file1
Error sending add rule request (File exists)
# auditctl -w /foo/foofile >> notice .. same length as /tmp/newfile
Error sending add rule request (File exists)
# auditctl -w /foo/anotherfile	>> works fine

So you see ... even using a different directory still says the watch exists.

If this is happening with others .. this definitely seems like a bug to me.

Thanks,
-Loulwa

             reply	other threads:[~2006-04-24 15:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-24 15:21 Loulwa Salem [this message]
2006-04-24 15:51 ` another issue with Audit Linda Knippers
2006-04-24 15:59   ` Steve Grubb
2006-04-24 16:04     ` Loulwa Salem
2006-04-24 18:07     ` Amy Griffis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=444CED13.1070900@us.ibm.com \
    --to=loulwas@us.ibm.com \
    --cc=linux-audit@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.