| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
use free_entry() instead of free() to free a struct _entry.
PR: 28108
Submitted by: Mark Peek <mark@whistle.com>
|
|
|
|
|
| |
Otherwise, "crontab -l > file; vi file; crontab file" adds an extra set
of "DO NOT EDIT" markers each and every time which is a bit silly.
|
|
|
|
| |
- MAN[1-9] -> MAN.
|
| |
|
|
|
|
|
|
|
| |
smashing argv[0] doesn't have the intended effect of changing the ps(1)
output these days.
PR: 25850
|
|
|
|
|
|
| |
- replaced Oo/Oc enclosures with Op;
- removed hard sentence breaks;
- removed doubled space.
|
|
|
|
|
| |
for any change of the time zone offset from GMT. To enable use the
option -s.
|
|
|
|
|
| |
child processes or starting children with no fd 0 (stdin) at all etc.
This is currently breaking on hub.freebsd.org.
|
|
|
|
| |
Seperate does not exist in the english language.
|
| |
|
| |
|
|
|
|
|
|
| |
to be used as the -width parameter, it is provided solely for backwards
compatibility with old mdoc(7). To make this work, mdocNG is forced to
provide a dummy ``Ds'' macro.
|
|
|
|
|
|
|
|
|
| |
enabled by the option "-s" (for dSt). This returned the default behavior
to its original form.
The new option name is not "-d" because that would cause associations with
"debug" and cron already has "-x" for debugging, so this would cause
confusion.
|
|
|
|
|
|
|
| |
for the jobs that fall into the disappearing or duplicated time
interval.
PR: bin/24494
|
|
|
|
| |
Bd/Ed; these hardly degrade the quality of the produced output.
|
| |
|
|
|
|
| |
Use _PATH_* where where possible.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
program to read any file which is a valid crontab file.
The fix is based on that used in NetBSD and OpenBSD - we keep the
file open while the user is editing it. This means that files must
be edited in place. Cron attempts to warn you if your editor does
not do this. The fact that the file must be edited in place is also
noted in the man page.
This patch has been confirmed to work by atleast one person on
-security and has been tested locally.
Obtained from: OpenBSD
|
|
|
|
| |
a crontab you were planning to edit.
|
|
|
|
| |
cases due to vfork()
|
|
|
|
|
|
|
| |
abusing sendmail by any other way via MAILTO tag (since sendmail is running
from daemon). Now run sendmail from user, as any other cron user command.
Obtained from: Inspired by OpenBSD, but implementation is different
|
|
|
|
| |
Obtained from: OpenBSD popen.c v1.3
|
|
|
|
|
|
| |
It helps perl f.e.
Obtained from: OpenBSD do_command.c v1.7
|
| |
|
| |
|
|
|
|
|
|
| |
Rev 1.8 made the type consistently incorrect.
Noted by: Ben Smithurst <ben@scientia.demon.co.uk>
|
|
|
|
|
|
|
|
|
|
|
| |
allocated memory was instead pointed to a static string. A later
free() on the value of the pointer was a possible source of reported
"warning: pointer to wrong page" messages from cron.
Use consistent types in sizeof when malloc'ing memory for the
environment.
PR: kern/12248, bin/11169, bin/9722
|
| |
|
|
|
|
|
|
|
|
| |
Fix setting of "hour" bitmap when @hourly keyword is specified.
MFC candidate after 4.0-RELEASE.
Problem-found-by: Sheldon Hearn <sheldonh@uunet.co.za>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
* Clarify quoting value in of name = value pairs.
* Describe the @reboot, @yearly, @annually, @monthly, @weekly,
@daily, @midnight and @hourly extensions.
PR: 17261
Submitted by: MIHIRA Yoshiro <sanpei@sanpei.org>
Obtained from: NetBSD
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Savings Time on cron(8). If we ever introduce some work-around code for
handling jobs scheduled for a time that "doesn't happen" due to DST,
the section should be renamed to IMPLEMENTATION NOTES.
PR: 10947
Reported by: Scott Drassinower <scottd@cloud9.net>
Submitted by: Seth Bromberger <seth@freebie.dp.ny.frb.org>
Reviewed by: mpp
|
|
|
|
|
|
|
| |
by cron'
PR: 12520
Submitted by: (not specified)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
which init thoughtfully revoke()'s when starting a getty on ttyv0. This
Cron's popen() was passing these fd's through to cron children (ie:
sendmail, *not* normal cron jobs). The side effects were usually
not noticed, but it tripped up postfix which did a sanity check to see
that stdin/out/err were open, and got EBADF even thought the fd's were
in use. I seem to recall sendmail itself has hacks to work around
this problem, it had a checkfd012() function, possibly for this same
problem. (Postfix has a workaround too now though..)
This is a hack, not a fix. It's probably best to check and perhaps
close/reopen() /dev/console if needed each time around the event loop.
It would probably be useful to actually see any error messages from cron.
|
|
|
|
|
| |
PR: 9506
Submitted by: Peter Jeremy <peter.jeremy@alcatel.com.au>
|
|
|
|
|
|
|
| |
Prevent cron from going crazy if the time steps. For example, if you
have a system with hundreds of users and lots of different crontabs
and your time steps back an hour, the old cron would then attempt to
run an hours worth of cron jobs in a few seconds.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
libraries so that `ld -f' in can create correct dependencies for
yet-to-be-built libraries.
Get the default BINDIR correctly (by including ../Makefile.inc recursively.
Override the default it it is wrong.
Don't override defaults when the defaults are correct.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use getpwnam before getpwuid since two users with same uids can exists
(affects new login classes code only)
The same fixes as in inetd: by default run `system crontab things' with
daemon login class now, not restrict them to user class breaking
compatibility with old way (so-called nobody limits problem)
Implement user[:group][/login-class] syntax in system crontab
for more flexible control (the same as in inetd)
|
| |
|
| |
|