Bare with me, i am not the person to post on forms and i am not exactly sure if this is even the right place to post
Cronie was installed by something in the welcome screens when i first installed my systems (my guess based on logs ) but not enabled or active.
i found this on both of my machines but the info below is from my desktop i use for testing
Garuda (2.6.14-1): System install date: 2022-03-21 Last full system update: 2023-01-19 ↻ Is partially upgraded: No Relevant software: snapper NetworkManager mkinitcpio Windows dual boot: Probably (Run as root to verify) Failed units: shadow.service
# /var/log/pacman.log [2022-03-21T14:58:42-0600] [PACMAN] Running 'pacman -Su --needed appmenu-gtk-module ark bluedevil brave-bin breeze breeze-gtk code colord-kde discord discover dolphin-plugins drkonqi evolution ffmpegthumbs filelight garuda-wallpapers-extra gnome-firmwa re gwenview hypnotix icoutils kaccounts-providers kactivitymanagerd kamera kamoso kate kcalc kcron kde-cli-tools kdeconnect kd ecoration kdegraphics-thumbnailers kde-gtk-config kdenetwork-filesharing kdeplasma-addons kde-service-menu-reimage kde-service menus-encfs kde-servicemenus-komparemenu kde-servicemenus-officeconverter kde-servicemenus-pdf kde-servicemenus-pdf-encrypt-de crypt kde-servicemenus-sendtodesktop kde-servicemenus-setaswallpaper kdf kdialog keditbookmarks kfind kgamma5 khelpcenter khot keys kimageformats kinfocenter kio-extras kio-fuse kio-gdrive kipi-plugins kleopatra kmenuedit kompare konsole krdc krename kr fb kscreen ksshaskpass ksystemlog kwalletmanager kwrited milou obs-studio octopi okular packagekit-qt5 partitionmanager plasma -browser-integration plasma-desktop plasma-disks plasma-firewall plasma-integration plasma-nm plasma-pa plasma-systemmonitor p lasma-thunderbolt plasma-vault plasma-workspace plasma-workspace-wallpapers polkit-kde-agent powerdevil printer-support print- manager python-adblock qt5-imageformats quota-tools qutebrowser resvg rootactions-servicemenu ruby samba-mounter-git samba-sup port scanner-support shortwave signal-desktop skanlite smb4k smplayer smplayer-skins smplayer-themes spectacle streamlink-twit ch-gui systemsettings torbrowser-launcher vim virt-manager-meta yakuake zoom' ... ... ... [2022-03-21T15:01:00-0600] [ALPM] installed cronie (1.5.7-2)
i wanted to create a cron script that runs garuda-update updated everyday and if the kernel was updated reboot. so being a good system admin i went to google and stack overflow and got nowhere =D so custom script FTW i went to /etc saw a bunch of cron folders (cron.hourly cron.daily ect...) made my dumb little script put it in cron.daily next to an existing
/etc/cron.daily/snapper that was there checked make sure it should reboot my system and waited for cron/anacron to do its thing and nothing happened
so after some banging around on the arch wiki i found how it does cron scheduling and did some packages searching saw that cronie was already installed... WIN!!! ..from there i checked
systemctl status cronie and it wasnt active or enabled .. BINGO! a couple of commands later and its enabled and seems to be working ok
so ya my problems fixed moving on with life ...but what about that snapper cron script ...what else was now going to run
# find /etc/cron* -type f /etc/cron.d/0hourly /etc/cron.daily/snapper /etc/cron.daily/z_garuda-update # this one is my lazyness /etc/cron.deny /etc/cron.hourly/0anacron /etc/cron.hourly/snapper
well the snapper stuff seems fine but the rabbit hole i am not sure is there is some systemd-timer set up for snapper
# systemctl list-timers NEXT LEFT LAST PASSED UNIT > Fri 2023-01-20 11:54:09 MST 47min left Thu 2023-01-19 18:53:39 MST 16h ago updatedb.timer > Fri 2023-01-20 16:33:10 MST 5h 26min left Thu 2023-01-19 16:33:10 MST 18h ago snapper-cleanup.timer > Fri 2023-01-20 16:38:26 MST 5h 32min left Thu 2023-01-19 16:38:26 MST 18h ago systemd-tmpfiles-clean.timer > Sat 2023-01-21 00:00:00 MST 12h left Fri 2023-01-20 00:00:04 MST 11h ago logrotate.timer > Sat 2023-01-21 00:00:00 MST 12h left Fri 2023-01-20 00:00:04 MST 11h ago shadow.timer > Sat 2023-01-21 08:28:40 MST 21h left Fri 2023-01-20 02:16:48 MST 8h ago man-db.timer > Sun 2023-01-22 09:43:12 MST 1 day 22h left Tue 2022-12-20 09:41:43 MST 1 month 0 days ago archlinux-keyring-wkd-sync.time> Wed 2023-02-01 00:00:00 MST 1 week 4 days left Sun 2023-01-01 00:00:29 MST 2 weeks 5 days ago btrfs-balance.timer > Wed 2023-02-01 00:00:00 MST 1 week 4 days left Sun 2023-01-01 00:00:29 MST 2 weeks 5 days ago btrfs-defrag.timer > Wed 2023-02-01 00:00:00 MST 1 week 4 days left Sun 2023-01-01 00:00:29 MST 2 weeks 5 days ago btrfs-scrub.timer > Wed 2023-02-01 00:00:00 MST 1 week 4 days left Sun 2023-01-01 00:00:29 MST 2 weeks 5 days ago btrfs-trim.timer >
- Do i need remove the snapper crons or the snapper systemd-timers?
- does the cron do the same thing as the timers? (im not a fan of systemd troubleshooting so im hoping someone knows)
- Am i better off disabling cronie and figure out how to get a systemd-timer to run my script?
- Should cronie have been enabled by default with snapper ?
i am lazy and i forget to update my machine. so far ive used it for the last 3 weeks manually and it seems to work fine. hence my idea about putting it in cron i couldnt find a solid way to do unintended-upgrades or needs-reboot and my trust in the aur is not great so i avoid it when i can.
Again sorry for the post. i know its long but im hoping i given enough info of what i see with both of my garuda machines. not 100% sure its a bug or by design. ive only used Garuda for 18 months or so (25+ year desktop linux user) and ive been really happy. it seems stable and other then needing to use the boot repair utility from the iso a couple of times from bad grub updates that didnt seem to be a Garuda isolated issue... totally off subject that boot repair utility is GREAT!!!! dont know if that is a Garuda only thing. but whoever created that, i owe them a beer/coffee)