mirror of
https://git.FreeBSD.org/ports.git
synced 2025-01-03 06:04:53 +00:00
a0e5aa5641
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 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 - 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 deny users. Author: Paul Jarc <prj@po.cwru.edu> WWW: http://multivac.cwru.edu/runwhen/ PR: 58789 Submitted by: David Thiel <lx@redundancy.redundancy.org>
15 lines
459 B
Plaintext
15 lines
459 B
Plaintext
--- package/compile Thu Oct 30 20:56:44 2003
|
|
+++ package/compile.new Fri Oct 31 16:07:38 2003
|
|
@@ -1426,7 +1426,10 @@
|
|
|
|
make_37() {
|
|
echo && echo_ Making compile/host/skalibs &&
|
|
- ln -s "$depend_skalibs" compile/move/skalibs
|
|
+ mkdir compile/move/skalibs &&
|
|
+ ln -s "$depend_skalibs/include/skalibs" compile/move/skalibs/include &&
|
|
+ ln -s "$depend_skalibs/lib/skalibs" compile/move/skalibs/library
|
|
+
|
|
}
|
|
find_sums_37() {
|
|
rm -f compile/tmpdir/sums &&
|