kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: Jeffrey Walton <noloader@gmail.com>
To: kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Monitor filesystem write to a specific directory?
Date: Tue, 31 Mar 2020 03:32:07 -0400	[thread overview]
Message-ID: <CAH8yC8mbRRpGSBprUjFq5pf9m3kVinEmTzeo9f42sc2P6qJH0Q@mail.gmail.com> (raw)

Hi Everyone,

I have some build scripts that allow me to install updated developer
tools on older machines. It builds and installs tools like Git, Curl
and Wget. It also builds dependencies. The scripts can handle about 80
packages.

One of those scripts is building a package that is performing a
wayward write during 'make install'. It is not using my specified
--libdir; instead it appears to hard code ${prefix}/lib. The incorrect
hard coded path breaks on Red Hat systems and Solaris. I need to
determine the offender.

On Windows I would use Process Monitor, run the programs and then
filter the events. I'm trying to find a Linux equivalent but neither
strace nor ltrace looks like an equivalent. For strace and ltrace it
does not look like I can setup a filter and get the process name.

How can I monitor filesystem writes to a specific directory?

Thanks in advance.

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

             reply	other threads:[~2020-03-31  7:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-31  7:32 Jeffrey Walton [this message]
2020-03-31  8:02 ` Monitor filesystem write to a specific directory? Andras Pal

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=CAH8yC8mbRRpGSBprUjFq5pf9m3kVinEmTzeo9f42sc2P6qJH0Q@mail.gmail.com \
    --to=noloader@gmail.com \
    --cc=kernelnewbies@kernelnewbies.org \
    /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 NNTP newsgroup(s).