Am 14.08.2013 13:43, schrieb Paul J Stevens: > On 08/14/2013 10:43 AM, Reindl Harald wrote: >> >> >> Am 14.08.2013 08:58, schrieb Paul J Stevens: >>> On 08/14/2013 08:27 AM, Thomas Raschbacher wrote: >>> >>>> Maybe put a flag somewhere so that it won't display it more than once >>>> when run from dbmail-util -M ? >>> >>> I've lowered the loglevel to INFO for now >> >> if you are at it (with really *low priority*) could you also take a >> look that /usr/sbin/dbmail-util -y -c -t -u -b -p -d -r 24h >> $LOGFILE >> does not result in cron-mails due stderror-outputs if there are no real >> errors - i hestitate to do 2>> $LOGFILE > > You should. I already modified the master branch so stderr *always* ends > up in the errorlog file. Stderr on the console should always be empty
in case of the console stderr *should go* to the console in this case having dbmail-util running as daily cron you would receive a email in case of real errors the problem is that regular messages like the one below are treatet as error-messages which trigger cron-mails daily Ok. Found [1] unconnected physmessages. Ok. Orphaned physmessages deleted. Ok. Found [1] unconnected mimeparts. Ok. Orphaned mimeparts deleted.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ DBmail mailing list [email protected] http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
