
Howdy,
I see in the crontab for the otrs user (which I finally turned on ;)
that there's this section:
# --
# cron/postmaster - postmaster cron of the OpenTRS
# Copyright (C) 2002 Martin Edenhofer

Hi Bryan, On Fri, Oct 18, 2002 at 10:08:41AM -0400, Bryan Fullerton wrote:
I see in the crontab for the otrs user (which I finally turned on ;) that there's this section:
# -- # cron/postmaster - postmaster cron of the OpenTRS # Copyright (C) 2002 Martin Edenhofer
# -- # $Id: .procmailrc,v 1.7 2002/05/12 22:04:43 martin Exp $ # -- # This software comes with ABSOLUTELY NO WARRANTY. # -- # check every 60 minutes the spool dorectory of OpenTRS */60 * * * * /etc/rc.d/otrs cleanup Where do I find the command that's supposed to live as /etc/rc.d/otrs? No mention of it (or the Cron.sh file) in the INSTALL docs.
Ja, correct. I added it to the INSTALL 2 weeks ago. You will find this command in $OTRS_HOME/scripts/suse-rcotrs. You can use '$OTRS_HOME/scripts/suse-rcotrs cleanup' on FreeBSD (not start, stop, ...). The "cleanup" option: ===================== If an incoming email can't process (e. g. database down, ...) through PostMaster.pl, this email will be spooled in $OTRS_HOME/var/spool/. This cronjob take each spooled email and pipe it through PostMaster.pl. If the exit status of PostMaster.pl was successful (exit 0) the spooled email will be deleted.
Bryan
Martin -- Martin Edenhofer - <martin at edenhofer.de> - http://martin.edenhofer.de/ -- Perfection is our goal, excellence will be tolerated. -- J. Yahl

On Friday, October 18, 2002, at 10:41 AM, Martin Edenhofer wrote:
Ja, correct. I added it to the INSTALL 2 weeks ago.
Aah, ok. Is the CVS version stable enough to run in production?
You will find this command in $OTRS_HOME/scripts/suse-rcotrs. You can use '$OTRS_HOME/scripts/suse-rcotrs cleanup' on FreeBSD (not start, stop, ...).
I've grabbed out the (small) part that I need to run for cleaning, see attached script. You might want to consider having things run by cron only output errors, otherwise there's lots of email even when things are running OK. Also, for some reason scripts/suse-rcotrs seems to have a space between the # and ! in the #!/bin/sh line, which prevents it from being able to run as a script. Is this intentional? Thanks! Bryan

On Fri, Oct 18, 2002 at 11:17:10AM -0400, Bryan Fullerton wrote:
Ja, correct. I added it to the INSTALL 2 weeks ago.
Aah, ok. Is the CVS version stable enough to run in production?
Not yet. We added a lot of new features. But in 1-2 weeks. ,)
You will find this command in $OTRS_HOME/scripts/suse-rcotrs. You can use '$OTRS_HOME/scripts/suse-rcotrs cleanup' on FreeBSD (not start, stop, ...).
I've grabbed out the (small) part that I need to run for cleaning, see attached script.
I added it to the CVS.
You might want to consider having things run by cron only output errors, otherwise there's lots of email even when things are running OK.
I add always ">> /dev/null" to the cronjobs. -=> Just error emails.
Also, for some reason scripts/suse-rcotrs seems to have a space between the # and ! in the #!/bin/sh line, which prevents it from being able to run as a script. Is this intentional?
No. I changed it.
Bryan
Martin -- Martin Edenhofer - <martin at edenhofer.de> - http://martin.edenhofer.de/ -- "There are two major products that come out of Berkeley: LSD and Unix. We don't believe this to be a coincidence." -- Jeremy S. Anderson

On Friday, October 18, 2002, at 12:08 PM, Martin Edenhofer wrote:
Not yet. We added a lot of new features. But in 1-2 weeks. ,)
Great!
You might want to consider having things run by cron only output errors, otherwise there's lots of email even when things are running OK.
I add always ">> /dev/null" to the cronjobs. -=> Just error emails.
Yeah, me too, but the samples weren't, so I wasn't sure if there was any important output from the commands. :) Thanks! Bryan
participants (2)
-
Bryan Fullerton
-
Martin Edenhofer