Hello community, here is the log from the commit of package fatrace for openSUSE:Factory checked in at 2019-05-06 13:25:46 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/fatrace (Old) and /work/SRC/openSUSE:Factory/.fatrace.new.5148 (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "fatrace" Mon May 6 13:25:46 2019 rev:6 rq:698636 version:0.13 Changes: -------- --- /work/SRC/openSUSE:Factory/fatrace/fatrace.changes 2019-04-17 10:08:05.418760722 +0200 +++ /work/SRC/openSUSE:Factory/.fatrace.new.5148/fatrace.changes 2019-05-06 13:25:48.597100209 +0200 @@ -1,0 +2,5 @@ +Mon Apr 15 18:49:11 UTC 2019 - Jan Engelhardt <jeng...@inai.de> + +- Trim storytelling from description. + +------------------------------------------------------------------- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ fatrace.spec ++++++ --- /var/tmp/diff_new_pack.W3Qp8O/_old 2019-05-06 13:25:49.197101447 +0200 +++ /var/tmp/diff_new_pack.W3Qp8O/_new 2019-05-06 13:25:49.201101455 +0200 @@ -20,7 +20,7 @@ Name: fatrace Version: 0.13 Release: 0 -Summary: Report system wide file access events +Summary: System wide file access event reporting utility License: GPL-3.0-or-later Group: System/Monitoring URL: https://launchpad.net/fatrace @@ -28,26 +28,16 @@ BuildRequires: glibc-devel %description -Part of the efforts to reduce power consumption is to identify processes -which keep waking up the disk even when the computer is idle. - -Unfortunately there is no really good tool to trace file access events -system-wide. powertop claims to, but its output is both very incomplete, -and also wrong (e. g. it claims that read accesses are writes). strace -gives you everything you do and don’t want to know about what’s going on, -but is per-process, and attaching strace to all running and new processes -is cumbersome. blktrace is system-wide, but operates at a way too low -level for this task: its output has nothing to do any more with files or -even inodes, just raw block numbers which are impossible to convert back -to an inode and file path. - -So I created a little tool called fatrace (“file access trace”, not “fat -race” :-) ) which uses fanotify, a couple of /proc lookups and some glue -to provide this. By default it monitors the whole system, i. e. all mounts -(except the virtual ones like /proc, tmpfs, etc.), but you can also tell -it to just consider the mount of the current directory. You can write the -log into a file (stdout by default), and run it for a specified number of -seconds. Optional time stamps and PID filters are also provided. +The fatrace trace uses fanotify, a couple of /proc lookups and some +glue to trace file access events system-wide, in an effort to +identify processes which keep waking up the disk even when the +computer is idle. + +By default, it monitors the whole system, i.e. all mounts except +virtual ones like /proc, tmpfs, etc. It can be told to monitor just +the mount of the current directory. The log can be written to a file +and runtime be capped. Optional time stamps and PID filters are also +provided. %prep %setup -q @@ -56,7 +46,7 @@ make %{?_smp_mflags} CFLAGS="%{optflags}" PREFIX="%{_prefix}" %install -make install DESTDIR=%{buildroot} CFLAGS="%{optflags}" PREFIX="%{_prefix}" +%make_install CFLAGS="%{optflags}" PREFIX="%{_prefix}" %files %license COPYING
