borgD contaminant

[m4r35n357Member]

As one of the “relics” who actually delivers local email, I have just seen this in my inbox:

From: Anacron <root@bonsai.doitto.me.uk>
To: root@bonsai.doitto.me.uk
Subject: Anacron job 'cron.daily' on bonsai
Date: Sun, 05 Apr 2026 08:01:42 +0100 (BST)

/etc/cron.daily/apt-compat:
/etc/cron.daily/apt-compat: 55: exec: /usr/lib/apt/apt.systemd.daily: not found
run-parts: /etc/cron.daily/apt-compat exited with return code 127

The final command in the cron job is:

# run daily job
exec /usr/lib/apt/apt.systemd.daily

I intend to nuke it from orbit, to be sure 😉

• This topic was modified 5 months, 3 weeks ago by m4r35n357. Reason: literacy

[032_hsnMember]

ha ha …

[wildstar84Member]

The file “/usr/lib/apt/apt.systemd.daily” doesn’t even exist on my system, so nothing to “nuke” here! 😀

[m4r35n357Member]

OK, I didn’t explain properly, but now I have a couple of minutes to do it justice. The cron job is:

/etc/cron.daily/apt-compat

this script belongs to:

$ dpkg -S /etc/cron.daily/apt-compat
apt: /etc/cron.daily/apt-compat

and I assume you have apt 😉

$ grep systemd /etc/cron.daily/apt-compat
# Systemd systems use a systemd timer unit which is preferable to
# same time. The systemd time is better at this than the fixed
if [ -d /run/systemd/system ]; then
exec /usr/lib/apt/apt.systemd.daily

is that better? 😉 Now I could edit /etc/cron.daily/apt-compat myself & delete the appropriate commands, but it will be overwritten at some point.

• This reply was modified 5 months, 1 week ago by m4r35n357. Reason: more detail

[wildstar84Member]

Sorry I didn’t see this reply until now. Yes I have apt and also the file “/etc/cron.daily/apt-compat”, but I do not have a file named “/usr/lib/apt/apt.systemd.daily”, do you?. Technically, it seems the former file should’ve used the code (to avoid potential missing file warnings):

if [ -x /usr/lib/apt/apt.systemd.daily ]; then
/usr/lib/apt/apt.systemd.daily
fi

If you DO have that file, you could either chmod it to NOT be executable, rename it, or comment out the line referencing it in /etc/cron.daily/apt-compat. I do not have any idea what this daily job is supposed to do on a non-systemD system though (need further light on this).

[m4r35n357Member]

The script

/etc/cron.daily/apt-compat

seems to be BorgD only, I zoned out after reading “sleep randomly blah . . .” – IMO that is typical operational BorgD “logic”. This is not a critical issue, I just get a boring email every day.

Since there is no point changing system files I pointed it out here – that is all really.

[Author]

Posts