PDA

View Full Version : Where is the manual for v.4


julianluton
06-23-2008, 06:50 AM
Hi,
Sorry for the dumb question, but where is the manual for v.4
I am trying to check my crontab entry, and a search of these forums points me to
http://wiki.cerberusdemo.com/index.php/Setting_up_a_Scheduled_Task_in_Linux
but that page won't load...

Also I am looking to find where the Cerberus writes it's logs and how to turn up logging on the parser.

Many thanks,
Julian

dsugita
06-23-2008, 04:47 PM
Hi Julian,
The cerb4 wiki has been moved to http://wiki.cerb4.com

julianluton
06-24-2008, 01:55 AM
Hi Darren,

Cool - thanks for that.

Why not redirect the old wiki to the new one, then fools like me wouldn't get stuck!

If any one out there gets stuck like me, the above link should now read.

http://wiki.cerb4.com/wiki/Setting_up_a_Scheduled_Task_in_Linux

Regards,
Julian

TOG
08-27-2008, 04:58 PM
Hi,
Sorry for the dumb question, but where is the manual for v.4
I am trying to check my crontab entry, and a search of these forums points me to
http://wiki.cerberusdemo.com/index.php/Setting_up_a_Scheduled_Task_in_Linux
but that page won't load...

Also I am looking to find where the Cerberus writes it's logs and how to turn up logging on the parser.

Many thanks,
Julian

Hi Julian,

Did you find where the Cerberus logs are and how to turn up the logging for the parser? I am looking for the same things and haven't been able to find them in the documentation yet.

Thanks.

julianluton
08-28-2008, 05:35 AM
As best as I could see Cerberus is pretty lame at the whole logging thing.

I did get my problem fixed up in the end.
What issues are you having with the parser?

TOG
08-28-2008, 02:22 PM
I had the parser set to bounce any unrouted mail but I did not receive a bounce during my testing... so I was looking for the parser logs to find out why a bounce was not sent.

Thanks.

Hildy
08-28-2008, 04:15 PM
Okay, lets address a couple things...

1) The logging in the parser is much better now; click the "run now" links from the Helpdesk Setup -> Scheduler page to see the url format. Log levels run to 7 for debug, and the default from there (6) should be "info" or something like that.

2) That said, the "bounce" option is.... well, misnamed, perhaps. At this time, it doesn't bounce email back to the sender, it just drops it completely. (I'm not sure without checking whether it keeps the .msg file in /storage/mail/fail or not.)

TOG
08-28-2008, 04:26 PM
Okay, lets address a couple things...

1) The logging in the parser is much better now; click the "run now" links from the Helpdesk Setup -> Scheduler page to see the url format. Log levels run to 7 for debug, and the default from there (6) should be "info" or something like that.

2) That said, the "bounce" option is.... well, misnamed, perhaps. At this time, it doesn't bounce email back to the sender, it just drops it completely. (I'm not sure without checking whether it keeps the .msg file in /storage/mail/fail or not.)

Hi Dan,

Thanks for the reply...

1) are the parser logs stored anywhere or are they only displayed?

2) Okay that explains what I am seeing :) I don't think it keeps the .msg file as my /storage/mail/fail is empty.

Thanks again.

Hildy
08-28-2008, 04:37 PM
They're only displayed. If you want to store them, you could use the log_level option on your cron, and cron will mail you the script output. The reason we *don't* have them on the cron by default, though, is so that you would typically only get mailed output if there was an error (so you can check it out).