Author Topic: Cron Tasks - Can not get to Function  (Read 1565 times)

Decka

  • Posts: 20
    • View Profile
Cron Tasks - Can not get to Function
« on: January 13, 2005, 09:56:07 pm »
Hi,
I have been trying to get CRON set up on my host account for quite some time now but with no success.

My host is Host4Profit so you would think given that this is one of the listed ones that should work with Listmail I should have no problem.

The CRON event code I am currently using is :-

00 01 * * * /usr/bin/wget -O /dev/null -T 0 /home/user/user-www/listmail/dailymail.php?pw=PASSWORD 1> /dev/null 2> /dev/null

This is taken from the Listmail manual but with my host details inputted.
The USER is the PATH to my host directory (this is not the actual one).
LISTMAIL is the directory name (not the actual one)
PASSWORD is my dailymail password (not the real one).

I am not sure if the -O after wget is meant to be O or 0, that is O as in the letter or 0 as in zero.

I have set up my host cron to send an email message when the CRON job runs but I never get a message. A scheduled email task within listmail also never gets actioned.

Can anyone suggest what the problem is ?

DW

  • Administrator
  • Posts: 3787
    • View Profile
    • https://legacy.listmailpro.com
Cron Tasks - Can not get to Function
« Reply #1 on: January 15, 2005, 01:43:18 am »
Replace:

/home/user/user-www/listmail/dailymail.php?pw=PASSWORD

With:

http://site.com/listmail/dailymail.php?pw=PASSWORD


Here's the help page: http://www.listmailpro.com/help/10.html

Regards!
Dean Wiebe
ListMailPRO Author & Developer - Help | Support | Hosting

Decka

  • Posts: 20
    • View Profile
Cron Tasks - Can not get to Function
« Reply #2 on: January 18, 2005, 01:28:35 am »
Hi,

DW, thanks for the reply, that fixed the problem. I got my first email notice today that the CRON task had run.

I was using the path to my site directories supplied by Host4Profit in their CRON manager. I should have stuck with using your suggested path using the direct URL, then it would have worked.

It was my fault for relying on what the webhost says.