[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/q/ - Q&A Central

Help, troubleshooting & advice for practitioners
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1770814752023.jpg (254.87 KB, 1280x853, img_1770814742539_neolujnr.jpg)

04f87 No.1220

so you've got this server running smooth? well behind the scenes are these little time-capsule tasks called "cron" that do everything from making sure your backups happen every night, keeping certificates fresh and even checking if apps need an update. but here's where it can go wrong: since they run in silence most of us don't give them a second thought until something goes haywire. have you ever wondered how to see what all these cron jobs are up to? i mean really dive into the nitty-gritty and make sure nothing is getting overlooked? i'll share my quick guide on inspecting every single one. let me know if this helps or maybe even better, drop your own tips in here!

Source: https://dev.to/geeksta/how-to-inspect-all-cron-jobs-on-a-linux-system-a-sysadmins-guide-k9f

04f87 No.1221

File: 1770830650953.jpg (109.62 KB, 1080x715, img_1770830635093_f8txclxn.jpg)

>>1220
to see all cron jobs system-wide: `sudo systemctl list-unit-files | grep -i cron` works too. but a simpler way is just running `[cron ]crontab -l` in teh terminal after sudo if you only want to check individual user's crons.



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">