Re: [Sawfish] Re: High IO while config is open.

["Robert 'Bobby' Zenz" <Robert.Zenz@xxxxxxxxxxxxxx>]

Thanks for the hints so far.

I'm at the moment trying to narrow this down with inotifywatch...there
is definitely something fishy going...but can't tell if is Sawfish or
GTK, see (attached) inotifywatch_local. That does not explain the disk
IO, but accessing that directory for 1k times during only a few seconds
of running?

I also tried with a new user, there was still disk-IO, but only a 10th
of it, around 50kb/sec. If I execute "inotifywatch -rv ." in the new
users home (which I can still do there, as I have too much in my own)
it shows still heavy access to (the empty) .local/share (around 400
times). I'm not sure if that tells you anything, though.

Does anyone else see this, by the way? Because if not, I assume that it
is my setup in some way.

Thanks for sticking with me so far.

P.S.: "gzip it"...dude, now I feel dumb...

On Wed, 29 Aug 2012 10:06:53 +0200
Michal Maruska <mmaruska@xxxxxxxxx> wrote:

> On Wed, Aug 29, 2012 at 12:33 AM, GSR - FR
> <famrom@xxxxxxxxxxxxxxxxxxxx> wrote: .....
> > There are thousands of 'read'. The one that appears a lot uses fd
> > 10, 'grep "read(10" strace_output | wc -l' gives 116465, the file
> > has 261125 lines.
> >
> > Looking up what has generated a 10 gives some 'open's (that are
> > closed quickly) and 'inotify_init1'. Those read calls have
> > '\x73\x74\x72\x61\x63\x65\x5f\x6f\x75\x74\x70\x75\x74' which is the
> > string 'strace_output'.
> >
> > My take is something is looking for changed files (check the
> > 'inotify_add_watch' calls), and you are changing a file just where
> > that thing is looking at.
> >
> > Could you try making redirections to /tmp/strace_output and check
> > again? Maybe something (gtk inner guts?) is causing part of the IO
> > noise.
> 
> So for some reason  this  sawfish-config opens an inotify on your home
> directory (and/home/robert/.local/share) .
> Maybe it should not, or is it some Gtk internal thing?
> 
> So, similar to
>     inoticoming --foreground  .  echo {} \;
> 
> When you do as GSR suggested (diverting the strace output out of those
> 2 directories),
> you might see what is touching files in those directories.
>

Attachment: strace_output.tar.bz2
Description: application/bzip

Attachment: inotifywatch_local
Description: Binary data