<!--
Fcron documentation
-Copyright 2000-2002 Thibault Godouet <fcron@free.fr>
+Copyright 2000-2004 Thibault Godouet <fcron@free.fr>
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
Version 1.1 or any later version published by the Free Software
A copy of the license is included in gfdl.sgml.
-->
-<!-- $Id: changes.sgml,v 1.25 2003-09-12 21:35:40 thib Exp $ -->
+<!-- $Id: changes.sgml,v 1.26 2003-12-25 22:59:58 thib Exp $ -->
<sect1 id="changes">
<title>Changes</title>
<para>Changed the subject line of mail reports : it now contains the
subject line, and is very similar to vixie cron's one.</para>
</listitem>
+ <listitem>
+ <para>bug fix : "makewhatis" bug is fixed -- at last !</para>
+ <para>In fact, the problems encountered were due to an abusively ignored
+ signal SIGPIPE.</para>
+ </listitem>
<listitem>
<para>bug fix : possible crash of fcron when trying to save a file
if there was no space left on device.</para>
a username before the command anymore, since many programs have one
of these characters in their name.</para>
</listitem>
+ <listitem>
+ <para>bug fix : option first was broken in fcron 2.9.3.</para>
+ </listitem>
<listitem>
<para>fixed a little typo in an error message
(could->couldn't)</para>
<listitem>
<para>fixed compile on SunOS 5.9 .</para>
</listitem>
+ <listitem>
+ <para>Fcron now compiles on MacOS X.</para>
+ </listitem>
<listitem>
<para>added some $srcdir to be able (again ;) ) to run configure from another directory.</para>
</listitem>
+ <listitem>
+ <para>Perf improvement : use buffer for i/o in run_job().</para>
+ </listitem>
</itemizedlist>
<itemizedlist>
<!--
Fcron documentation
-Copyright 2000-2002 Thibault Godouet <fcron@free.fr>
+Copyright 2000-2004 Thibault Godouet <fcron@free.fr>
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
Version 1.1 or any later version published by the Free Software
A copy of the license is included in gfdl.sgml.
-->
-<!-- $Id: relnotes.sgml,v 1.5 2003-07-14 10:56:26 thib Exp $ -->
+<!-- $Id: relnotes.sgml,v 1.6 2003-12-25 22:58:07 thib Exp $ -->
<sect1 id="relnotes">
<title>Release notes : &fcron; &version;</title>
<itemizedlist>
- <listitem>
+ <listitem>
<para>PAM support has not been tested thoroughly. Help from a PAM
-expert would be appreciated (to audit the PAM code in fcron, and test it). You
-can disable PAM use in configure, using "--with-pam=no".</para>
- </listitem>
- <listitem>
- <para>Some commands of &fcrondyn; are not implemented yet. In
-particular, fcrondyn does not use PAM yet.</para>
- </listitem>
- <listitem>
+ expert would be appreciated (to audit the PAM code in fcron, and
+ test it). You can disable PAM use in configure, using
+ "--with-pam=no".</para>
+ <para>Moreover, fcrondyn does not use PAM at this time (should it
+ anyway ?).</para>
+ </listitem>
+ <listitem>
+ <para>Some commands of &fcrondyn; are not implemented yet.</para>
+ </listitem>
+ <listitem>
<para>Fcrondyn might be not very secure, and might be used to block
-&fcron;.</para>
- </listitem>
+ &fcron;.</para>
+ </listitem>
</itemizedlist>
</sect1>
<!--
Fcron documentation
-Copyright 2000-2002 Thibault Godouet <fcron@free.fr>
+Copyright 2000-2004 Thibault Godouet <fcron@free.fr>
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
Version 1.1 or any later version published by the Free Software
A copy of the license is included in gfdl.sgml.
-->
-<!-- $Id: todo.sgml,v 1.22 2003-09-12 20:55:59 thib Exp $ -->
+<!-- $Id: todo.sgml,v 1.23 2003-12-25 22:59:21 thib Exp $ -->
<sect1 id="todo">
<title>Todo</title>
<para>Here are some things that should be done ... Note that some of these
- entries are just some ideas, which <emphasis>may</emphasis> be done
- in the long run.</para>
- <para>If you plan to help me, please send a mail at &email; to prevent
- two people from doing the same thing. You can send me some propositions as
+ entries are just some ideas, which <emphasis>may</emphasis> be done in
+ the long run.</para>
+ <para>If you plan to help me, please send a mail at &email; to prevent two
+ people from doing the same thing. You can send me some propositions as
well, or ask me to move something to the top of the heap ;) .</para>
<sect2>
<title>High priority</title>
<itemizedlist>
<listitem>
- <para>add psgml-docbook-dtd.cache, psgml-ecat.file to RCS &
- CVS</para>
- </listitem>
- <listitem>
- <para>mails from wohler@newt.com : improve the doc + change (?) the
+ <para>mails from B. Wohler : improve the doc + change (?) the
name of fcrondyn -> fcronc ?? </para>
</listitem>
- <listitem>
- <para>crash when /var is full ???</para>
- </listitem>
<listitem>
<para>problem with daylight savings ? ("already running" ...)
(cf. Nick's mails -- Warning : he has a new address))</para>
system is running on battery (anacron does it ?)</para>
</listitem>
<listitem>
- <para>bug fix : makewhatis does not work correctly with fcron 2.9.0
- and following</para>
- <para>Help is welcome to catch this bug !</para>
+ <para>create a mailing list for help/user support : send a mail
+ on fcronannounce + news on web site to advertise it.</para>
</listitem>
</itemizedlist>
</sect2>
<title>Low priority</title>
<itemizedlist>
<listitem>
- <para>Use directory notifications (?) (portable ?)
- (cf. dnotify)</para>
+ <para>code cleaning : create a .c/.h file for data structures
+ (file/line lists, serial queue, lavg list, exe list),
+ and work with them only through functions/macros.</para>
+ <para>Note : thoroughly check for bugs which can be introduced
+ during the code cleaning (make sure that after the
+ modification, the code executed is still the same as before
+ !).</para>
</listitem>
<listitem>
- <para>PAM support (included in fcron, but needs more tests by people
- using PAM - not implemented in fcrondyn : is it needed in
- fcrondyn anyway ?)</para>
+ <para>Mem footprint reduction : for fcron processes which are aimed
+ at running sendmail, free() some memory (file/line lists, queues, ...)
+ (but does it worth it ? takes too much exe time for few memory ?)</para>
+ <para>Also use an/some union(s) in CL struct.</para>
</listitem>
<listitem>
- <para>implement more commands for fcrondyn, and make it more secure
- and reliable</para>
+ <para>implement more commands for fcrondyn, and make it more
+ secure and reliable</para>
</listitem>
<listitem>
- <para>add a timezone option instead of the tzdiff (so it would look
- like !timezone(europe/paris)) (?)</para>
+ <para>add a timezone option instead of the tzdiff (so it would
+ look like !timezone(europe/paris)) (?)</para>
</listitem>
<listitem>
<para>For environment settings, make a var substitution.</para>
</listitem>
<listitem>
- <para>add a return code for jobs which would mean that they should
- not be run again (in case of an error, etc...).</para>
+ <para>add a return code for jobs which would mean that they
+ should not be run again (in case of an error, etc...).</para>
+ </listitem>
+ <listitem>
+ <para>Use directory notifications (?) (portable ?) (cf.
+ dnotify)</para>
+ </listitem>
+ <listitem>
+ <para>PAM support (included in fcron, but needs more tests by
+ people using PAM - not implemented in fcrondyn : is it needed
+ in fcrondyn anyway ?)</para>
</listitem>
</itemizedlist>
</sect2>
<title>Ideas</title>
<itemizedlist>
<listitem>
- <para>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 ? - yes :
- thanks Harring ;) dlopen exists on all POSIX system - even
- windoze - abait it does not use the same insterface of function
- calls. But it can be easily implemented to port to another
- system.).</para>
+ <para>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 ?
+ - yes : thanks Harring ;) dlopen exists on all POSIX system -
+ even windoze - abait it does not use the same insterface of
+ function calls. But it can be easily implemented to port to
+ another system.).</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>
+ 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>
and restart it (SIGCONT) when the lavg has decreased.</para>
</listitem>
<listitem>
- <para>Add a timeout for task completion : if a task takes more than
- a specified timeout, then start another script with the initial
- task PID as argument. That would allow a kill with different
- signals (-HUP, -TERM -STOP, .... or any other action like sending
- a mail to sysadmin to alert him/her that a task is taking too
- much time and that he has to have a look at it.) </para>
+ <para>Add a timeout for task completion : if a task takes more
+ than a specified timeout, then start another script with the
+ initial task PID as argument. That would allow a kill with
+ different signals (-HUP, -TERM -STOP, .... or any other action
+ like sending a mail to sysadmin to alert him/her that a task
+ is taking too much time and that he has to have a look at it.)
+ </para>
</listitem>
<listitem>
- <para>Add a directory similar to xinet.d or logrotate.d to add job
- entries (?).</para>
+ <para>Add a directory similar to xinet.d or logrotate.d to add
+ job entries (?).</para>
</listitem>
</itemizedlist>
</sect2>
sgml-parent-document:("fcron-doc.sgml" "book" "chapter" "sect1" "")
End:
-->
+
\ No newline at end of file
projects / fcron / commitdiff