日期:2014-05-16  浏览次数:20745 次

crontab命令
我敲命令crontab   -l
中看到了类似   #58   2   *   *   *   date的命令
不知道前面的#是什么意思   ,是不是注释掉这个JOB呢?

------解决方案--------------------
#后面的就是注释
类似ini文件里的;
c里的//
------解决方案--------------------
注释,请结帖
------解决方案--------------------
是注释,没错
------解决方案--------------------
NAME
crontab -- tables for driving cron

DESCRIPTION
A crontab file contains instructions to the cron(8) daemon of the general
form: ``run this command at this time on this date ' '. Each user has
their own crontab, and commands in any given crontab will be executed as
the user who owns the crontab. Uucp and News will usually have their own
crontabs, eliminating the need for explicitly running su(1) as part of a
cron command.

Blank lines and leading spaces and tabs are ignored. Lines whose first
non-space character is a pound-sign (#) are comments, and are ignored.
Note that comments are not allowed on the same line as cron commands,
since they will be taken to be part of the command. Similarly, comments
are not allowed on the same line as environment variable settings.

An active line in a crontab will be either an environment setting or a
cron command. An environment setting is of the form,

name = value

where the spaces around the equal-sign (=) are optional, and any subse-
quent non-leading spaces in value will be part of the value assigned to
name. The value string may be placed in quotes (single or double, but
matching) to preserve leading or trailing blanks. The name string may
also be placed in quote (single or double, but matching) to preserve
leading, trailing or inner blanks.

Several environment variables are set up automatically by the cron(8)
daemon. SHELL is set to /bin/sh, PATH is set to /usr/bin:/bin, and
LOGNAME and HOME are set from the /etc/passwd line of the crontab 's
owner. HOME, PATH and SHELL may be overridden by settings in the
crontab; LOGNAME may not.

(Another note: the LOGNAME variable is sometimes called USER on BSD sys-
tems... On these systems, USER will be set also).

In addition to LOGNAME, HOME, PATH, and SHELL, cron(8) will look at
MAILTO if it has any reason to send mail as a result of running commands
in ``this ' ' crontab. If MAILTO is defined (and non-empty), mail is sent
to the user so named. MAILTO may also be used to direct mail to multiple
recipients by seperating recipient users with a comma. If MAILTO is
defined but empty (MAILTO= " "), no mail will be sent. Otherwise mail is
sent to the owner of the crontab. This option is useful if you decide on
/bin/mail instead of /usr/lib/sendmail as your mailer when you install
cron -- /bin/mail does not do aliasing, and UUCP usually does not read
its mail.

The format of a cron command is very much the V7 standard, with a number
of upward-compatible extensions. Each line has five time and date
fields, followed by a user name (with optional ``: <group> ' ' and
``/ <login-class> ' ' suffixes) if this is the system crontab file, followed
by a command. Commands are executed by cron(8) when the minute, hour,
and month of year fields match the current time, and when at least one of