This is the mail archive of the cygwin-apps mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Please review and upload cron-4.1-1


[I sent this last night but it seems to have vanished, despite being queued on sourceware.org
 2007-04-09 21:13:33 JG9CQG-0002DO-4R => cygwin-apps@cygwin.com R=dnslookup T=remote_smtp 
H=sourceware.org [209.132.176.174] C="250 Queued! 1176167611 qp 8330 
<3.0.1.32.20070409211328.00b9dc90@incoming.verizon.net>" ]
********************************************************

With Corinna's encouragement I am taking over as cron maintainer.
Fortunately the latest cron requires a lot fewer Cygwin specific changes
that what she had to implement.

A mistake in packaging or porting is always possible, and cron tends
to generate annoying traffic to the list. Thus reviews of the package will
be appreciated. I am also including below some details that will be in the
announcement.

The files can be found in

http://mysite.verizon.net/phumblet/cron-4.1-1/setup.hint
http://mysite.verizon.net/phumblet/cron-4.1-1/cron-4.1-1.tar.bz2
http://mysite.verizon.net/phumblet/cron-4.1-1/cron-4.1-1-src.tar.bz2

Please upload if no issues are reported within a day.

Pierre

*************************************************************
This is a change of maintainer and of cron version.

News:

Cron
****
This port is based on Paul Vixie's cron packaged as 4.1 but reporting itself
as 5.0.

The changes (listed in /usr/share/doc/cron/CHANGES) don't appear to break
compatibility with 3.0.

There is a new algorithm to handle time jumps.

Logging of a command can now be suppressed by using the -q switch, such as
in the following example:
* * * * * -q /usr/bin/date

Package
*******
/usr/bin/cron-config is still recommended to install the cron service.

The base environment is now set as under sshd (in the previous package the
environment on NT was the same as that of cygrunsrv, with some variables
deleted, and it was empty on 9x). Variables defined in the crontab are added
to the base, as previously done.

Cron normally uses a mailer such as exim or ssmtp to communicate stdout
and stderr output to the user. Cron uses the symbolic link /usr/sbin/sendmail
to find the mailer. This feature is still supported.

If /usr/sbin/sendmail does not point to a mailer, the cron postinstall script
links it to the (new) script /usr/bin/cronlog.

/usr/bin/cronlog is a "poor man's" mailer that writes cron output (if any)
to HOME/cron.log.  HOME can be superseded in the crontab file.
The temporary output of /usr/bin/cronlog is written to /tmp/cron.XXX.log and
/tmp/cron.XXX.log.err. These files are deleted if all goes well but can
provide useful debugging information if HOME/cron.log cannot be written
(e.g. on some network drives).
/usr/bin/cronlog can be edited to suit particular needs.

A mailer can be installed as well. The mailer configuration script,
exim-config or ssmtp-config, will then offer to point /usr/sbin/sendmail
appropriately.

More information can be found in /usr/share/doc/Cygwin/cron-4.1-1.README




Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]