'cron'에 해당되는 글 1건

  1. 2008.12.31 [펌]man crontab 1,5

[펌]man crontab 1,5

Legacy 2008. 12. 31. 15:34
분 시 일 월 요일 유저 명령어 순이다 근데 이걸 왜케 맨날 까먹는 걸까..ㅡㅜ;
가장 많이 쓰는 것도
*/1 이와 같은 구문 이다 매 1분 마다 혹은 매 1시간 마다.. 된장.. 늘 꺼꾸로 써서 오류를 만들어 낸다..
암튼 이제는 쉬운것도 다 까먹는 바보가 되어 가는게 정말 짜증이다.. 흑흑

crontab -l : 등록된 목록 보기
crontab -e : 목록 수정 하기 또는 등록하기

걍 터미널 상에서 쳐봐.. 그럼 뭐라도 나온다..

자주 하는 실 수중 또 하나..
cp, mv 이런 파일이 위치한 path 가 잡혀 있거나 full path 로 실행 시키시길 바란다..
난 늘 같은 실수는 하는 것 같기도 하고.. 바보가 되어서 잊은 것 같기도 하고.. 된장..

만든 shell script 를 실행 하면 잘 된다.. 하지만 crond 가 잘 실행을 못한다..
그럼 빤하다.. 내가 잘 못한거다..

오늘도 역시 한건 했다.. path 생략하고.. 기냥 했다.. 난 바보인가?? ^^;;

*     *   *   *    *  command to be executed
-     -    -    -    -
|     |     |     |     |
|     |     |     |     +----- day of week (0 - 6) (Sunday=0)
|     |     |     +------- month (1 - 12)
|     |     +--------- day of month (1 - 31)
|     +----------- hour (0 - 23)
+------------- min (0 - 59)


CRONTAB(1)							    CRONTAB(1)

NAME

crontab - maintain crontab files for individual users (V3)

SYNOPSIS

crontab [ -u user ] file crontab [ -u user ] { -l | -r | -e }

DESCRIPTION

crontab is the program used to install, deinstall or list the tables used to drive the cron(8) daemon in Vixie Cron. Each user can have their own crontab, and though these are files in /var/spool/cron/crontabs, they are not intended to be edited directly. If the /etc/cron.allow file exists, then you must be listed therein in order to be allowed to use this command. If the /etc/cron.allow file does not exist but the /etc/cron.deny file does exist, then you must not be listed in the /etc/cron.deny file in order to use this command. If neither of these files exists, then depending on site-dependent con- figuration parameters, only the super user will be allowed to use this command, or all users will be able to use this command. For standard Debian systems, all users may use this command. If the -u option is given, it specifies the name of the user whose crontab is to be tweaked. If this option is not given, crontab exam- ines "your" crontab, i.e., the crontab of the person executing the com- mand. Note that su(8) can confuse crontab and that if you are running inside of su(8) you should always use the -u option for safety's sake. The first form of this command is used to install a new crontab from some named file or standard input if the pseudo-filename ``-'' is given. The -l option causes the current crontab to be displayed on standard output. See the note under DEBIAN SPECIFIC below. The -r option causes the current crontab to be removed. The -e option is used to edit the current crontab using the editor specified by the VISUAL or EDITOR environment variables. After you exit from the editor, the modified crontab will be installed automati- cally. If neither of the environment variables is defined, then the default editor /usr/bin/editor is used.

DEBIAN SPECIFIC

The "out-of-the-box" behaviour for crontab -l is to display the three line "DO NOT EDIT THIS FILE" header that is placed at the beginning of the crontab when it is installed. The problem is that it makes the sequence crontab -l | crontab - non-idempotent -- you keep adding copies of the header. This causes pain to scripts that use sed to edit a crontab. Therefore, the default behaviour of the -l option has been changed to not output such header. You may obtain the original behaviour by setting the environment vari- able CRONTAB_NOHEADER to 'N', which will cause the crontab -l command to emit the extraneous header.

SEE ALSO

crontab(5), cron(8)

FILES

/etc/cron.allow /etc/cron.deny

STANDARDS

The crontab command conforms to IEEE Std1003.2-1992 (``POSIX''). This new command syntax differs from previous versions of Vixie Cron, as well as from the classic SVR3 syntax.

DIAGNOSTICS

A fairly informative usage message appears if you run it with a bad command line.

BUGS

Although cron requires that each entry in a crontab end in a newline character, the neither the crontab command nor the cron daemon will detect this error. Instead, the crontab will appear load normally. How- ever, the command will never run. The best choice is to ensure that your crontab has a blank line at the end.

AUTHOR

Paul Vixie <paul@vix.com> 4th Berkeley Distribution 29 December 1993 CRONTAB(1)

 

 


 

: