Dave Brodin:
> 84 processes: 13 running, 71 sleeping
> CPU: 1.9% user, 0.0% nice, 98.1% system, 0.0% interrupt, 0.0% idle
> Mem: 171M Active, 6548M Inact, 842M Wired, 246M Cache, 827M Buf, 104M Free
> Swap: 4096M Total, 60K Used, 4096M Free
>
> PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU
> COMMAND
> 3350 postfix 1 100 0 37580K 5572K RUN 4 0:08 25.32%
> smtpd
> 3353 postfix 1 100 0 37580K 5572K RUN 7 0:08 25.31%
> smtpd
> 3351 postfix 1 20 0 37580K 5572K lockf 3 0:07 23.97%
> smtpd
> 3354 postfix 1 99 0 37580K 5572K CPU1 7 0:07 23.97%
> smtpd
> 3357 postfix 1 99 0 37580K 5572K CPU4 6 0:07 23.65%
> smtpd
> 3371 postfix 1 100 0 37580K 5572K CPU5 3 0:06 23.26%
> smtpd
> 3368 postfix 1 100 0 37580K 5572K CPU6 1 0:06 22.99%
> smtpd
I have never seen smtpd use up significant amounts of CPU, except
with Stan Hoeppner's extremely large PCRE or CIDR tables.
How does this configuration differ from the machine that "works"?
> > How bit is the "passwd" file? What's in nsswitch.conf or
> > equivalent for "passwd"?
>
> There are 18,983 entries in the passwd file.
>
> This is my nsswitch.com:
>
> group: compat
> group_compat: nis
> hosts: files dns
> networks: files
> passwd: compat
> passwd_compat: nis
> shells: files
> services: compat
> services_compat: nis
> protocols: files
> rpc: files
That's the default for FreeBSD, which uses Berkeley DB for password
and group files (I'm running FreeBSD 8.X here).
Wietse
