#
259065 |
|
07-Dec-2013 |
gjb |
- Copy stable/10 (r259064) to releng/10.0 as part of the 10.0-RELEASE cycle. - Update __FreeBSD_version [1] - Set branch name to -RC1
[1] 10.0-CURRENT __FreeBSD_version value ended at '55', so start releng/10.0 at '100' so the branch is started with a value ending in zero.
Approved by: re (implicit) Sponsored by: The FreeBSD Foundation |
#
256281 |
|
10-Oct-2013 |
gjb |
Copy head (r256279) to stable/10 as part of the 10.0-RELEASE cycle.
Approved by: re (implicit) Sponsored by: The FreeBSD Foundation
|
#
242101 |
|
25-Oct-2012 |
sobomax |
Second attempt to add @every_second keyword support. Due to multiple requests, default to the previous 60-seconds scheduling method unless there is any @every_second entries to conserve CPU cycles and power.
This change also improves scheduling in the default mode by running as close to the beginning of the minnute as possible by replacing sleep(3) with nanosleep(2). Previously, the tasks would run anywhere within the first second of the minute and that offset drifted back and forth each time cron(8) was engaged.
MFC after: 1 month
|
#
241651 |
|
17-Oct-2012 |
sobomax |
Remove harmless, but superfluous local change that creeped in along with the r241649.
|
#
241649 |
|
17-Oct-2012 |
sobomax |
Revert latest changes to cron, until better version is worked out (I hope).
Requested by: few
|
#
241576 |
|
15-Oct-2012 |
sobomax |
Add per-second scheduling into the cron(8). Right now it's only available via the new @every_second shortcut. ENOTIME to implement crontab(5) format extensions to allow more flexible scheduling.
In order to address some concerns expressed by Terry Lambert while discussing the topic few years ago, about per-second cron possibly causing some bad effects on /etc/crontab by stat()ing it every second instead of every minute now (i.e. atime update), only check that database needs to be reloaded on every 60-th loop run. This should be close enough to the current behaviour.
Add "@every_minute" shortcut while I am here.
MFC after: 1 month
|
#
184809 |
|
10-Nov-2008 |
matteo |
Make usr.sbin/cron/crontab and usr.sbin/cron/lib WARNS=3 clean
Tested with: make universe
MFC after: 3 days
|
#
180096 |
|
29-Jun-2008 |
marck |
Add -m option to cron(8), overriding default mail recipient for cron mails, unless explicitly provided by MAILTO= line in crontab. This feature can be useful in massive hosting environment, where most users do not care about autogenerated mails.
Setting recipient to null string disables default mails at all.
Approved by: yar MFC after: 4 weeks
|
#
173412 |
|
07-Nov-2007 |
kevlo |
Cleanup of userland __P use
|
#
170890 |
|
17-Jun-2007 |
yar |
Add PAM support to cron(8). Now cron(8) will skip commands scheduled by unavailable accounts, e.g., those locked, expired, not allowed in at the moment by nologin(5), or whatever, depending on cron's pam.conf(5). This applies to personal crontabs only, /etc/crontab is unaffected.
In other words, now the account management policy will apply to commands scheduled by users via crontab(1) so that a user can no longer use cron(8) to set up a delayed backdoor and run commands during periods when the admin doesn't want him to.
The PAM check is done just before running a command, not when loading a crontab, because accounts can get locked, expired, and re-enabled any time with no changes to their crontabs. E.g., imagine that you provide a system with payed access, or better a cluster of such systems with centralized account management via PAM. When a user pays for some days of access, you set his expire field respectively. If the account expires before its owner pays more, its crontab commands won't run until the next payment is made. Then it'll be enough to set the expire field in future for the commands to run again. And so on.
Document this change in the cron(8) manpage, which includes adding a FILES section and touching the document date.
X-Security: should benefit as users have access to cron(8) by default
|
#
149430 |
|
24-Aug-2005 |
pjd |
Use pidfile(3) in cron(8).
Note, that when cron(8) cannot create pidfile, it'll exit. I didn't changed this behaviour, but its better to ignore errors other than EEXIST, so daemon can be started on systems where /var/ file system doesn't support locking (like NFS without rpc.lockd(8)).
|
#
129280 |
|
16-May-2004 |
yar |
Add two new options to cron(8), -J and -j. They allow to specify the maximum amount of time jitter for root and other users, respectively. Before starting a job, cron(8) will sleep a random number of seconds, from 0 to the amount specified. This can help to smooth down load spikes when a lot of jobs are to start at the beginning of a particular minute (e.g., the first minute of an hour.)
PR: bin/66474 Submitted by: Dmitry Morozovsky <marck <@> rinet.ru>
|
#
74010 |
|
09-Mar-2001 |
babkin |
The new version of the daylight time saving support. This time it works for any change of the time zone offset from GMT. To enable use the option -s.
|
#
71407 |
|
22-Jan-2001 |
babkin |
Backed out the DST support changes.
|
#
71301 |
|
20-Jan-2001 |
babkin |
Added sensible handling of switch to and from daylight saving time for the jobs that fall into the disappearing or duplicated time interval.
PR: bin/24494
|
#
69230 |
|
26-Nov-2000 |
kris |
Correct definition of MAXHOSTNAMELEN in ifdef'ed out code
|
#
62367 |
|
01-Jul-2000 |
ache |
Prevent user from breaking his limits and restrictions or 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
|
#
50479 |
|
27-Aug-1999 |
peter |
$Id$ -> $FreeBSD$
|
#
30895 |
|
02-Nov-1997 |
ache |
Log run-time parsing errors now
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)
|
#
29452 |
|
15-Sep-1997 |
charnier |
Use err(3). Rewrote man page in mdoc format.
|
#
22997 |
|
22-Feb-1997 |
peter |
Revert $FreeBSD$ to $Id$
|
#
21673 |
|
14-Jan-1997 |
jkh |
Make the long-awaited change from $Id$ to $FreeBSD$
This will make a number of things easier in the future, as well as (finally!) avoiding the Id-smashing problem which has plagued developers for so long.
Boy, I'm glad we're not using sup anymore. This update would have been insane otherwise.
|
#
20573 |
|
16-Dec-1996 |
pst |
Replace my "inane" usage of snprintf to copy strings with strncpy as used by OpenBSD. (Quite frankly, I think it's perfectly reasonable to use snprintf to copy strings, given that the semantics for strncpy() are utterly idiotic and there is no POSIX sstrncpy().)
While I'm at it, incorporate some of OpenBSD's bugfixes to cron.
NOT for 2.2
|
#
17436 |
|
04-Aug-1996 |
pst |
Fix up some more buffer overflow problems.
|
#
8857 |
|
30-May-1995 |
rgrimes |
Remove trailing whitespace.
|
#
2312 |
|
27-Aug-1994 |
jkh |
This commit was generated by cvs2svn to compensate for changes in r2311, which included commits to RCS files with non-trunk default branches.
|
#
2311 |
|
27-Aug-1994 |
jkh |
Paul Vixie's cron, version 3.0. Munged into bmake format. If this goes well, expect our two seperate directories for cron and crontab to go away shortly. Submitted by: jkh
|