Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am working on building a scheduler which runs tasks at specified times. In this regard, I felt it would be good to know how the cron daemon works. I Googled, but didnt really get much insight into what actually happens. Can I get some directions as to where I can get information on the same?
When cron is started or made to reread it's config, it examines all the config files, parses them and
stores this info in memory.
In a loop that runs every minute (==the finest time granule allowed), it checks if any jobs need to run
and if there are, it runs them (using a special environment setting and running as the user who submitted the job).
But, I agree with baldy that you should stick with cron/at if you can. There is no need to make your own.
If you do have a system without a scheduler/cron, you may consider building it from it source.
If I understand correctly, cron is one of many "daemons" that run in background to keep the system functioning. All of these have the common feature that they continuously check **something** to see if an action is required. An obvious example is the daemon that watches for keyboard input in a terminal.
cron simply watches the clock and checks against the instructions in crontab to see what needs to be run for any given time.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.