diff options
author | amdmi3 <amdmi3@FreeBSD.org> | 2016-05-19 18:53:05 +0800 |
---|---|---|
committer | amdmi3 <amdmi3@FreeBSD.org> | 2016-05-19 18:53:05 +0800 |
commit | 22084e17f721ebb9a063f5603491229fcfc70d9b (patch) | |
tree | 06f11bc7b351f3abf3bf5507405afdba5374614e /sysutils/runwhen | |
parent | 3f42e716135bc048b90cb6cca188f324e65c69dc (diff) | |
download | freebsd-ports-gnome-22084e17f721ebb9a063f5603491229fcfc70d9b.tar.gz freebsd-ports-gnome-22084e17f721ebb9a063f5603491229fcfc70d9b.tar.zst freebsd-ports-gnome-22084e17f721ebb9a063f5603491229fcfc70d9b.zip |
- Fix trailing whitespace in pkg-descrs, categories [p-x]*
Approved by: portmgr blanket
Diffstat (limited to 'sysutils/runwhen')
-rw-r--r-- | sysutils/runwhen/pkg-descr | 32 |
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/ |