in reply to Cron on Mac OS X

As Fletch mentioned in your previous post, launchd is now the 'preferred' mechanism. In particular, cron probably isn't running by default. A silly question: did you start it?

UPDATE: Also, it seems that you asked this same question in your other thread about an hour and a half ago, so it's not really appropriate to make a fresh post here.

Replies are listed 'Best First'.
Re^2: Cron on Mac OS X
by Ninth Prince (Acolyte) on Sep 09, 2008 at 15:44 UTC

    Sorry about the double-posting -- I thought that had gone off somewhere else. I'm still trying to figure out how this site works.

    I did some looking into launchd and it looked much more involved than setting up a crontab. That said, I still can't get this thing to work. To answer your question, I have not turned on crontab. How would I go about doing that?

    Thanks.

[reply]
      crontab itself doesn't need to be turned on as such—it's used only to tell cron to use a particular crontab file. However, cron does need to be running in order to know to do anything. I don't know about Leopard, but, on Tiger, cron is started up by launchd in response to a file called com.vix.cron.plist in /System/Library/LaunchDaemons. (That file records the path, tells it to RunAtLoad, and gives it WatchPaths and a QueueDirectory, which are /etc/crontab and /var/cron/tab, respectively.)
[reply]
[d/l]
[select]
        On OS X 10.5, cron should be running by default. I just did a fresh install a few months ago, and didn't have to do anything to activate it.
[reply]

In Section Seekers of Perl Wisdom