Quanah,

I noticed when running amavisd-status, it always reports 0 children
for the first 2 checks (when using 1 second intervals):

$ ./amavisd-status
process-id task-id     elapsed in    elapsed-bar (dots indicate idle)
          or state   idle or busy

0 active, 0 idling processes


0 active, 0 idling processes


0 active, 10 idling processes
..........

0 active, 10 idling processes
..........

Yes, this is normal.

The amavisd-status starts with no information on the number of running
amavisd child processes. The actual count is broadcast periodically
by the 'amavis-services childproc-minder' process, so this is when
the amavisd-status catches up, every couple of seconds.

  Mark

Reply via email to