Copyright © 2000-2002 Thibault Godouet | Fcron 2.9.3 (dev release) | Web page : http://fcron.free.fr |
Fcron documentation | ||
---|---|---|
Prev | Chapter 1. Fcron : how and why ? | Next |
Here are some things that should be done ... Note that some of these entries are just some ideas, which may be done in the long run.
If you plan to help me, please send a mail at <fcron@free.fr> to prevent two people from doing the same thing. You can send me some propositions as well.
bug fix : makewhatis does not work correctly with fcron 2.9.0 and following
Help is welcome to catch this bug !
Use directory notifications (?) (portable ?) (cf. dnotify)
PAM support (included in fcron, but needs more tests by people using PAM - not implemented in fcrondyn)
implement more commands for fcrondyn, and make it more secure and reliable
For environment settings, make a var substitution.
add a return code for jobs which would mean that they should not be run again (in case of an error, etc...).
add a system of modules : at startup, fcron loads some modules (.so files). Then, when fcron should run the job, it calls a function of the module, and let it manage the job (threads ?). (do linux dlopen(), etc exist on other systems ?).
(related to the system of modules ? create a kind of dependencies ?) Add a way to run a job only if a command returns true. It would permit, for instance, to run some jobs on a laptop only if it is on AC power.
add a system of data flow
Add a way to stop a job (SIGSTOP) if the lavg gets to high, and restart it (SIGCONT) when the lavg has decreased.