> > Is running amavisd-nanny -c 1 >/dev/null
> > from cron every hour (or so) sufficient to ensure that?
>
> I guess so, although I'm not doing this myself.
> It can't hurt to put its output to a log file to be able
> to investigate past events if need occurs. And if
> a need for killing a child p
Ralf,
> Is running amavisd-nanny -c 1 >/dev/null
> from cron every hour (or so) sufficient to ensure that?
I guess so, although I'm not doing this myself.
It can't hurt to put its output to a log file to be able
to investigate past events if need occurs. And if
a need for killing a child process
Ralf,
> Is running amavisd-nanny -c 1 >/dev/null
> from cron every hour (or so) sufficient to ensure that?
I do so ...
--
Andreas Schulze
Internetdienste | P252
DATEV eG
90329 Nürnberg | Telefon +49 911 319-0 | Telefax +49 911 319-3196
E-Mail info @datev.de | Internet www.datev.de
Sitz: 90429 N
I've seen that amavisd-nanny will kill children that are lingering
around and not reporting back to the DB.
Is running
amavisd-nanny -c 1 >/dev/null
from cron every hour (or so) sufficient to ensure that?
--
Ralf Hildebrandt
Geschäftsbereich IT | Abteilung Netzwerk
Charité - Universitätsmed
Hi all,
I am using amavisd-nanny for the first time.
I don't quite understand what to read. I couldn't understand explanation in
the documentation.
Can someone help me to understand what are the dots mean and how to read my
amavisd-nanny?
Thank you in advance.
Justin
PID 06473: 0:02
