summaryrefslogtreecommitdiff
path: root/sysutils/runwhen
diff options
context:
space:
mode:
authorDmitry Marakasov <amdmi3@FreeBSD.org>2016-05-19 10:53:05 +0000
committerDmitry Marakasov <amdmi3@FreeBSD.org>2016-05-19 10:53:05 +0000
commit1f8b48b772b2d0ac0ed48a8259d2117ea3236a90 (patch)
tree06f11bc7b351f3abf3bf5507405afdba5374614e /sysutils/runwhen
parent- Fix trailing whitespace in pkg-descrs, categories [g-n]* (diff)
- Fix trailing whitespace in pkg-descrs, categories [p-x]*
Approved by: portmgr blanket
Notes
Notes: svn path=/head/; revision=415500
Diffstat (limited to 'sysutils/runwhen')
-rw-r--r--sysutils/runwhen/pkg-descr32
1 files changed, 16 insertions, 16 deletions
diff --git a/sysutils/runwhen/pkg-descr b/sysutils/runwhen/pkg-descr
index ab7197bfba2f..eb32144b1d39 100644
--- a/sysutils/runwhen/pkg-descr
+++ b/sysutils/runwhen/pkg-descr
@@ -1,23 +1,23 @@
The biggest difference between runwhen and other schedulers is that
-runwhen doesn't have a single daemon overseeing multiple jobs.
-The runwhen tools essentially act as a glorified sleep command.
-Perhaps runwhen does nothing that at(1) doesn't, and there are
+runwhen doesn't have a single daemon overseeing multiple jobs.
+The runwhen tools essentially act as a glorified sleep command.
+Perhaps runwhen does nothing that at(1) doesn't, and there are
lots of things at(1) does that runwhen doesn't:
-- runwhen doesn't change user IDs - thus it will never run
- anything as the wrong user.
-- It doesn't keep a central daemon running at all times -
+- runwhen doesn't change user IDs - thus it will never run
+ anything as the wrong user.
+- It doesn't keep a central daemon running at all times -
thus it won't break if that daemon dies.
-- It doesn't require any modifications to the system boot procedure.
-- It doesn't log through syslog(3) - thus it won't make a mess
- on the console if syslogd(1) isn't running.
-- It doesn't centralize storage of scheduled jobs (or any other
- per-job information) - thus unprivileged users can install and use it
- without cooperation from root, and without the use of a setuid program
- to handle changes.
-- It doesn't send output through mail - thus it doesn't break
- if there is no mail system installed.
-- It doesn't check access control files - thus it doesn't gratuitously
+- It doesn't require any modifications to the system boot procedure.
+- It doesn't log through syslog(3) - thus it won't make a mess
+ on the console if syslogd(1) isn't running.
+- It doesn't centralize storage of scheduled jobs (or any other
+ per-job information) - thus unprivileged users can install and use it
+ without cooperation from root, and without the use of a setuid program
+ to handle changes.
+- It doesn't send output through mail - thus it doesn't break
+ if there is no mail system installed.
+- It doesn't check access control files - thus it doesn't gratuitously
deny users.
WWW: http://code.dogmap.org/runwhen/