summaryrefslogtreecommitdiffstats
path: root/usr.sbin/cron/cron
diff options
context:
space:
mode:
authordd <dd@FreeBSD.org>2001-07-15 08:06:20 +0000
committerdd <dd@FreeBSD.org>2001-07-15 08:06:20 +0000
commit911ca14c8798a89d240d36ecbc63b5df5dd99f66 (patch)
tree62f210bf3aee25e49335dc77030fff6e97fbe447 /usr.sbin/cron/cron
parenta145482cf625d5f04072fd1d20b5c2062cbe8e47 (diff)
downloadFreeBSD-src-911ca14c8798a89d240d36ecbc63b5df5dd99f66.zip
FreeBSD-src-911ca14c8798a89d240d36ecbc63b5df5dd99f66.tar.gz
Remove whitespace at EOL.
Diffstat (limited to 'usr.sbin/cron/cron')
-rw-r--r--usr.sbin/cron/cron/cron.820
1 files changed, 10 insertions, 10 deletions
diff --git a/usr.sbin/cron/cron/cron.8 b/usr.sbin/cron/cron/cron.8
index da6b9d7..9ac8823 100644
--- a/usr.sbin/cron/cron/cron.8
+++ b/usr.sbin/cron/cron/cron.8
@@ -14,9 +14,9 @@
.\" * I'll try to keep a version up to date. I can be reached as follows:
.\" * Paul Vixie <paul@vix.com> uunet!decwrl!vixie!paul
.\" */
-.\"
+.\"
.\" $FreeBSD$
-.\"
+.\"
.Dd December 20, 1993
.Dt CRON 8
.Os
@@ -81,9 +81,9 @@ Enable special handling of situations when the GMT offset of the local
timezone changes, such as the switches between the standard time and
daylight saving time.
.Pp
-The jobs run during the GMT offset changes time as
+The jobs run during the GMT offset changes time as
intuitively expected.
-If a job falls into a time interval that disappears
+If a job falls into a time interval that disappears
(for example, during the switch from
standard time) to daylight saving time or is
duplicated (for example, during the reverse switch), then it's handled
@@ -92,12 +92,12 @@ in one of two ways:
The first case is for the jobs that run every at hour of a time interval
overlapping with the disappearing or duplicated interval.
In other words, if the job had run within one hour before the GMT offset change
-(and cron was not restarted nor the
+(and cron was not restarted nor the
.Xr crontab 5
changed after that)
or would run after the change at the next hour.
They work as always, skip the skipped time or run in the added
-time as usual.
+time as usual.
.Pp
The second case is for the jobs that run less frequently.
They are executed exactly once, they are not skipped nor
@@ -106,10 +106,10 @@ executed twice (unless cron is restarted or the user's
is changed during such a time interval).
If an interval disappears
due to the GMT offset change, such jobs are
-executed at the same absolute point of time as they would be in the
+executed at the same absolute point of time as they would be in the
old time zone.
-For example, if exactly one hour disappears, this
-point would be during the next hour at the first minute that is
+For example, if exactly one hour disappears, this
+point would be during the next hour at the first minute that is
specified for them in
.Xr crontab 5 .
.It Fl o
@@ -123,6 +123,6 @@ are specified, the option specified last wins.
.El
.Sh SEE ALSO
.Xr crontab 1 ,
-.Xr crontab 5
+.Xr crontab 5
.Sh AUTHORS
.An Paul Vixie Aq paul@vix.com
OpenPOWER on IntegriCloud