AboutSummaryRefsLogTreeCommitDiffStats
path: root/TODO
diff options
context:
space:
mode:
authordale_mellor <dale_mellor>2003-08-03 15:14:54 +0000
committerdale_mellor <dale_mellor>2003-08-03 15:14:54 +0000
commiteb50865add48ceccfa38bf4165351dd0418df41f (patch)
treeb6d34a4e806ba0e61ec63f39320c3c636d82b459 /TODO
parent2c6cfc753d5c4a6116bcf24307371c33f49bcfd1 (diff)
downloadmcron-eb50865add48ceccfa38bf4165351dd0418df41f.tar.gz
mcron-eb50865add48ceccfa38bf4165351dd0418df41f.tar.bz2
mcron-eb50865add48ceccfa38bf4165351dd0418df41f.zip
Broken all functionality out into separate modules.
Diffstat (limited to 'TODO')
-rw-r--r--TODO27
1 files changed, 9 insertions, 18 deletions
diff --git a/TODO b/TODO
index a5d5539..e5c0c60 100644
--- a/TODO
+++ b/TODO
@@ -1,4 +1,4 @@
-Copyright (C) 2003 Dale Mellor
+Copyright (C) 2003 Dale Mellor -*-text-*-
See the end for copying conditions.
@@ -9,12 +9,10 @@ Maybe in the near future...
* Check POSIX compliance (should be okay if Vixie cron was okay).
- * Work out how to give each user his own closure (or environment or module)
- for his configuration files so that he can't mess the core or other
- users' files up. Then allow scheme code in the system crontabs.
-
- * Move the code into modules so that it can be incorporated directly into
- other programs.
+ * Work out how to give each user his own closure (or environment or module
+ or continuation) for his configuration files so that he can't mess the
+ core or other users' files up. Then allow scheme code in the system
+ crontabs.
@@ -30,24 +28,17 @@ There are no plans to actually do the following any time soon...
-Quite likely to happen if version 2.0 ever materializes...
-
- * Split program into Vixie and mcron separates (should streamline mcron code
- by a factor of three; removes need for security audit).
+May happen if version 2.0 ever materializes...
* UNIX or TCP socket will allow interrogation and control of a running
- daemon (should be more reliable, efficient and useful than using the
- SIGHUP-/var/cron/update method).
-
-
-
-May happen if version 2.0 ever materializes...
+ daemon (unrelated to, or maybe a major enhancement of, socket used for
+ communication from crontab process).
* Add anacron functionality (run missed jobs if the daemon is stopped, for
example if a personal computer does not run 24 hours a day).
* TCP socket to allow control via HTTP (web browser interface). Or maybe
- just CGI personality.
+ crontab-like CGI personality.
* GTK+/Bononbo/Gnome2 interface.