From: thib <thib>
Date: Fri, 30 Aug 2002 20:06:07 +0000 (+0000)
Subject: *** empty log message ***
X-Git-Tag: ver1564~40
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=41c0d6abf1b8d0349c21dfee5239ee370c2e0b2b;p=fcron

*** empty log message ***
---

diff --git a/doc/en/changes.sgml b/doc/en/changes.sgml
index c9c8377..f36d5b7 100644
--- a/doc/en/changes.sgml
+++ b/doc/en/changes.sgml
@@ -8,7 +8,7 @@ Foundation.
 A copy of the license is included in gfdl.sgml.
 -->
 
-<!-- $Id: changes.sgml,v 1.15 2002-08-29 17:35:29 thib Exp $ -->
+<!-- $Id: changes.sgml,v 1.16 2002-08-30 20:06:10 thib Exp $ -->
 
 <sect1 id="changes">
     <title>Changes</title>
@@ -21,6 +21,10 @@ A copy of the license is included in gfdl.sgml.
 	<listitem>
 	    <para>mailto can now be set to a non-real user (for ex., an alias).</para>
 	</listitem>
+	<listitem>
+	    <para>Added a system fcrontab. Root can access it with fcrontab by using
+"-u systab".</para>
+	</listitem>
 	<listitem>
 	    <para>fcron now calls shutdown() when a connection from fcrondyn is closed.
 Another change in the code should prevent fcrondyn from not returning to the prompt after
diff --git a/doc/en/todo.sgml b/doc/en/todo.sgml
index 86d81b0..30f82d9 100644
--- a/doc/en/todo.sgml
+++ b/doc/en/todo.sgml
@@ -8,7 +8,7 @@ Foundation.
 A copy of the license is included in gfdl.sgml.
 -->
 
-<!-- $Id: todo.sgml,v 1.12 2002-08-29 17:34:57 thib Exp $ -->
+<!-- $Id: todo.sgml,v 1.13 2002-08-30 20:06:07 thib Exp $ -->
 
 <sect1 id="todo">
     <title>Todo</title>
@@ -30,6 +30,9 @@ well.</para>
 	    <para>find a way to get user's job pid (not the fcron process
 	    controling it) (use pipe() ?)</para>
 	</listitem>
+	<listitem>
+	    <para>Use (or remove from config.h.in) MAX_USER_CON & MAX_IDLE_TIME.</para>
+	</listitem>
 	<listitem>
 	    <para>PAM support (included in fcron, but need more tests by people 
 using PAM - not implemented in fcrondyn)</para>
@@ -49,6 +52,11 @@ not be run again (in case of an error, etc...).</para>
 (.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 ?).</para>
+	</listitem>
+	<listitem>
+	    <para>(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.</para>
 	</listitem>
 	<listitem>
 	    <para>add a system of data flow</para>