Re: Problem with cron jobs

The trigger program handles one domain at a time, and one list at a 
time, starting with GLOBAL.  If the tokens for a particular list are not 
expiring, you need to figure out what tasks run at the same time as that 
list's token update, for that domain and every domain that appears 
earlier in the list of domains at your site.

One easy step would be to use the "showtokens ALL" command to find the 
first domain that shows old tokens.  Chances are that the trigger 
problem is caused by that domain or the previous domain.

Are you running mj_trigger with the "-v 700" switch to get full 
debugging information?

Michael


Brock Rozen wrote:
> Let's just say that I had tokens from November...and that nobody in 
> their right mind keeps tokens (willingly) that long. :)