aboutsummaryrefslogtreecommitdiff
path: root/sysutils/p5-Schedule-Cron/pkg-descr
diff options
context:
space:
mode:
authorNeil Blakey-Milner <nbm@FreeBSD.org>2001-01-03 09:17:30 +0000
committerNeil Blakey-Milner <nbm@FreeBSD.org>2001-01-03 09:17:30 +0000
commit194d04ec160048fde97cda369ce5a8ec40ca7440 (patch)
tree97646c0a1d5054365720ab40c79c0e574b87f767 /sysutils/p5-Schedule-Cron/pkg-descr
parent397bdc226600f30a935a377deeb212da7bf3556a (diff)
Notes
Diffstat (limited to 'sysutils/p5-Schedule-Cron/pkg-descr')
-rw-r--r--sysutils/p5-Schedule-Cron/pkg-descr21
1 files changed, 21 insertions, 0 deletions
diff --git a/sysutils/p5-Schedule-Cron/pkg-descr b/sysutils/p5-Schedule-Cron/pkg-descr
new file mode 100644
index 000000000000..e34bae54ad73
--- /dev/null
+++ b/sysutils/p5-Schedule-Cron/pkg-descr
@@ -0,0 +1,21 @@
+This module provides a simple but complete cron like scheduler. I.e
+this modules can be used for periodically executing Perl subroutines.
+The dates and parameters for the subroutines to be called are
+specified with a format known as crontab entry (see manpage crontab(5)
+or documentation of Schedule::Cron).
+
+The philosophy behind Schedule::Cron is to call subroutines
+periodically from within one single Perl program instead of letting
+cron trigger several (possibly different) Perl scripts. Everything
+under one roof. Furthermore Schedule::Cron provides mechanism to
+create crontab entries dynamically, which isn't that easy with cron.
+
+Schedule::Cron knows about all extensions (well, at least all
+extensions I'm aware of, i.e those of the so called "Vixie" cron) for
+crontab entries like ranges including 'steps', specification of month
+and days of the week by name or coexistence of lists and ranges in the
+same field. And even a bit more (like lists and ranges with symbolic
+names).
+
+-Anton
+<tobez@tobez.org>