ListMailPRO Email Marketing Software Forums

ListMailPRO Email Marketing Software Forums => General Help & How-To => Topic started by: davidmccready on August 07, 2006, 06:18:26 am

Title: Cron setup
Post by: davidmccready on August 07, 2006, 06:18:26 am

Dean

Here is the interesting difference between what you have suggested:

/usr/bin/wget -O /dev/null -T 0 http://example.com/mail/dailymail.php?pw=****** 1> /dev/null 2> /dev/null

And what the server company suggests:
php /home/CpanelUsername/public_html/mail/dailymail.php?pw=******

However neither seem to work.
Note that the actual days and times are set on the control pannel.

Thanks for looking at this.

David

Title: Cron setup
Post by: DW on August 07, 2006, 11:22:45 am

David,

If your host is running CPanel you should be able to set this up successfully.  What your host suggest _might_ work, but it depends on a second set of PHP settings.  The "wget" program may not be available on your server.  Try an alternative, "curl", as follows:

Timing (12:05am): 5 0 * * *
Command (1-line): curl -o /dev/null http://example.com/mail/dailymail.php?pw=****** 1> /dev/null 2> /dev/null

Regards

Title: Cron setup
Post by: davidmccready on August 08, 2006, 01:01:12 am

Dean

Initial signs are good.
That appeared to work for Cpanel.

Thanks
David

Title: Cron setup
Post by: listmailpro on August 08, 2006, 11:13:57 am

David, I remember back when my hosting company (SuccessfulHosting.com) changed their servers over, I had a heck of a time getting this to work again. My currently working method is VERY similar to what Dean just posted, so I wanted to provide it as guidance for you as well.

Here's what I have running (preceeded by '0 6 * * *' for timing):

/usr/bin/curl -o /dev/null http://example.com/mail/dailymail.php?pw=******

What Dean's last reply showed:
curl -o /dev/null http://example.com/mail/dailymail.php?pw=****** 1> /dev/null 2> /dev/null

Title: Cron setup
Post by: DW on August 08, 2006, 11:46:51 am

Thanks for your reply 'listmailpro' :D

I'd like to point out the very subtle differences between my suggestion and what worked for you.

I omitted the full path to curl because it is often found in the "system path", which means you can run it from "anywhere".

I added the "1> /dev/null 2> /dev/null" to suppress all output, which prevents you being emailed output if there is any.

Regards