While you're here, please consider supporting GamingOnLinux on:
Reward Tiers: Patreon. Plain Donations: PayPal.
This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Reward Tiers: Patreon. Plain Donations: PayPal.
This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Login / Register
-
Ubuntu 24.04 LTS (Noble Numbat) is now available
- Eike -
Proton 9.0 Beta updated and nearing release for Linux /…
- sudoer -
Factorio devs detail their 'Linux adventures' in a new …
- Samsai -
Proton Hotfix update fixes Fallout 4 frame pacing issue…
- F.Ultra -
Ubuntu 24.04 LTS (Noble Numbat) is now available
- F.Ultra - > See more comments
Latest Forum Posts
- Nintendo-style gaming, without Nintendo!
- Pengling - Free Steam Keys!
- robvv - Company of Heroes 2 Benchmark
- Vortex_Acherontic - New Desktop Screenshot Thread
- Owltech - Hello to all
- JordanBurton - See more posts
View PC info
Anyway, I’d like to figure out what this is and turn it off but I have no idea where to look, so any help would be welcome. Running crontab as either my user or root returns nothing. I’m on Mint 19 Cinnamon.
View PC info
cat /etc/cron.d/*
systemctl list-timers
systemctl --user list-timers
View PC info
I personally find locate a very useful tool when you need it, just shift it to a time when you're less active, or maybe weekly or even monthly instead of daily...
View PC info
/etc/cron.d/* looks innocent:
30 7 * * * root [ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start >/dev/null; fi
SHELL=/bin/bash
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
MAILTO=""
0 * * * * root timeshift --check --scripted
systemctl list-timers:
NEXT LEFT LAST PASSED
Fri 2020-02-21 18:03:54 EST 8min left Fri 2020-02-21 17:00:11 EST 55min ago
Fri 2020-02-21 18:34:22 EST 38min left Fri 2020-02-21 09:53:17 EST 8h ago
Sat 2020-02-22 03:33:17 EST 9h left Fri 2020-02-21 14:43:13 EST 3h 12min a
Sat 2020-02-22 06:53:35 EST 12h left Fri 2020-02-21 09:53:17 EST 8h ago
Sat 2020-02-22 13:22:29 EST 19h left Fri 2020-02-21 13:22:29 EST 4h 33min a
Mon 2020-02-24 00:00:00 EST 2 days left Mon 2020-02-17 00:00:11 EST 4 days ago
n/a n/a Thu 2020-02-20 00:18:53 EST 1 day 17h
The last one might correspond to the approximate time it finished two days ago, but the rest don’t seem related.
systemctl --user list-timers shows 0 timer.
I also tried grep run-parts /etc/crontab to check mlocate and other dailies but the timing doesn’t correspond either.
17 * * * * root cd / && run-parts --report /etc/cron.hourly
25 6 * * * root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
View PC info
Can't help you with systemd specifics though.
View PC info
I ran locate / as suggested on Launchpad to see where it was spending so much time, and as it happens Timeshift’s snapshots are occupying an incredible proportion of the output. I’ve added its directory to PRUNEPATHS in /etc/updatedb.conf as suggested, we’ll see how it goes the next time.
Last edited by Salvatos on 22 February 2020 at 5:25 am UTC
View PC info
View PC info