61
TCB Bugs / Re: CorePure64 v17 networking issues
« Last post by Juanito on March 04, 2026, 04:25:30 PM »It would help if you could show the steps you took and the errors you got
... also wondering which version was fetched? given: ...
tc@box:~/BuildTCZs/FAtrace/fatrace$ git describe --tags --long | cut -d '-' -f 1,2 | tr - .
0.19.1.5
tc@box:~/BuildTCZs/FAtrace/fatrace$someone@somewhere:~$ apt info fatrace
Package: fatrace
Version: 0.17.0-1
Priority: optional
Section: utils
Maintainer: Martin Pitt <mpitt@debian.org>
Installed-Size: 44.0 kB
Depends: libc6 (>= 2.34)
Recommends: python3, powertop
Homepage: https://github.com/martinpitt/fatrace
Download-Size: 12.5 kB
APT-Sources: http://deb.devuan.org/merged daedalus/main amd64 Packages
Description: report system wide file access events
fatrace reports file access events from all running processes.
Its main purpose is to find processes which keep waking up the disk
unnecessarily and thus prevent some power saving.
.
This package also contains a "power-usage-report" tool, which uses
fatrace and powertop to build a textual report from one minute of
measuring power usage and file accesses. This does not take any
arguments or requires any interactivity, so is very simple to use and
serves as a starting point for bug reports or optimizing a particular
installation.# Install toolchain and a couple of support packages.
tce-load -wi compiletc git sstrip
# Create a build directory.
mkdir FAtrace
cd FAtrace
# Fetch the source package.
git clone https://github.com/martinpitt/fatrace.git
# Build and strip fatrace.
cd fatrace
make
sstrip fatrace# From the man page:
# "It does not report file access by fatrace itself, to avoid logging events
# caused by writing the output into a file. It also ignores events on virtual
# and kernel file systems such as sysfs, proc, and devtmpfs."
#
# It also seems to ignore the RAM based rootfs, including /etc. It seems to
# want "real mount points", so we create one:
mkdir etc
sudo mount --bind /etc etccd etc
# Useful options:
# -c means "Only record events on partition/mount of current directory".
# That's why we cd into etc.
# -f W Means "We only want to capture file writes".
# -p means "Ignore events for this process ID. Can be specified multiple times."
# That's useful for filtering out noisy processes.
# -o ../file.txt means "Write events to given file instead of standard output."
# No point in writing a file to etc.
tc@box:~/BuildTCZs/FAtrace/fatrace/etc$ sudo .././fatrace -c -f W -o ../file.txttc@box:~/BuildTCZs/FAtrace/fatrace/etc$ rm -f ../file.txt
tc@box:~/BuildTCZs/FAtrace/fatrace/etc$ sudo .././fatrace -c -f W -p 397 -o ../file.txttc@box:~$ sudo ifconfig eth0 down
tc@box:~$ sudo /opt/eth0.shtc@box:~/BuildTCZs/FAtrace/fatrace/etc$ cat ../file.txt
eth0.sh(8208): W /home/tc/BuildTCZs/FAtrace/fatrace/etc/resolv.conf
eth0.sh(8208): CWO /home/tc/BuildTCZs/FAtrace/fatrace/etc/resolv.conf
tc@box:~/BuildTCZs/FAtrace/fatrace/etc$tc@box:~/BuildTCZs/FAtrace/fatrace/etc$ sudo .././fatrace -c -f W 2>&1 grep -E "resolv|hosts"
eth0.sh(13001): W /home/tc/BuildTCZs/FAtrace/fatrace/etc/resolv.conf
eth0.sh(13001): W /home/tc/BuildTCZs/FAtrace/fatrace/etc/resolv.conf
eth0.sh(13001): CW /home/tc/BuildTCZs/FAtrace/fatrace/etc/resolv.conf
eth0.sh(13001): W /home/tc/BuildTCZs/FAtrace/fatrace/etc/resolv.conf
eth0.sh(13001): CW /home/tc/BuildTCZs/FAtrace/fatrace/etc/resolv.confEven though eth0.sh performs 2 echo commands into /etc/resolv.conf, we get 5 results (quirk?).tc@box:~/BuildTCZs/FAtrace/fatrace/etc$ sudo .././fatrace -c -f W 2>&1 grep -E "resolv|hosts" > ../file.txtAnother quirk, or is something wrong with my redirection?