|
2005-10-03
, 17:25
|
Posts: 949 |
Thanked: 14 times |
Joined on Jul 2005
|
#2
|
|
2005-10-03
, 17:30
|
|
Posts: 1,436 |
Thanked: 3,144 times |
Joined on Jul 2005
|
#3
|
|
2005-10-03
, 21:49
|
Posts: 52 |
Thanked: 1 time |
Joined on Aug 2005
|
#4
|
|
2005-11-05
, 18:15
|
Posts: 93 |
Thanked: 2 times |
Joined on Aug 2005
|
#6
|
|
2005-11-05
, 18:32
|
Posts: 211 |
Thanked: 3 times |
Joined on Oct 2005
|
#7
|
|
2005-11-16
, 21:53
|
Posts: 155 |
Thanked: 10 times |
Joined on Nov 2005
@ central georgia, usa
|
#8
|
I have no idea what a cron job is. Sounds obscene and icky.
|
2006-01-01
, 00:45
|
Posts: 41 |
Thanked: 0 times |
Joined on Dec 2005
@ Brasil
|
#9
|
cron is a daemon (service if you're from Redmond) that runs jobs at particular dates/times. think of it as the windows scheduler.
the "output" of a cron job is put in the email folder of the user account that runs the job.
|
2006-01-17
, 22:38
|
Posts: 155 |
Thanked: 10 times |
Joined on Nov 2005
@ central georgia, usa
|
#10
|
Pardon, I resent that "service if you're from Redmond". In my Mandriva box (and most RH derived distros, AFAIK) you can type
#service crond start|stop
for example, so calling it a service is not Redmon-centric. I would personally define a daemon as a manager of service(s); so that the crond daemon manages the cron service; the xinetd daemon may manage a lot of services, and so on. A bit OT, I guess, sorry.
Thanks.