From: "Frank Ch. Eigler" <fche@redhat.com>
To: Anthony Green <green@redhat.com>
Cc: systemtap@sources.redhat.com
Subject: Re: systemtap question
Date: Wed, 06 Sep 2006 13:36:00 -0000 [thread overview]
Message-ID: <20060906133557.GD22715@redhat.com> (raw)
In-Reply-To: <1157546598.2847.28.camel@localhost.localdomain>
Hi -
green@redhat.com wrote:
> I have a customer who wants certain system files to have
> non-standard file permissions, but some cron job keeps changing them
> back every night. He'd like to figure out who is doing this.
OK.
> Is this the kind of thing systemtap could help with? Do you have
> any examples that are similar to this?
The closest one would be one of the demos from the tutorial, which I'm
plopping onto the wiki as we speak.
http://sourceware.org/systemtap/wiki/WSFileMonitor
- FChE
next parent reply other threads:[~2006-09-06 13:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1157546598.2847.28.camel@localhost.localdomain>
2006-09-06 13:36 ` Frank Ch. Eigler [this message]
2006-09-06 18:41 Stone, Joshua I
[not found] <48ACFC02.3080002@gmail.com>
2008-08-23 4:28 ` Peter Teoh
2008-08-23 12:51 ` Mark Wielaard
2008-08-23 14:09 ` Frank Ch. Eigler
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=20060906133557.GD22715@redhat.com \
--to=fche@redhat.com \
--cc=green@redhat.com \
--cc=systemtap@sources.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).