search for: jun18

...elieve that rpc.idmapd is working as it should. Starting rpc.idmapd with -vvv dumps the mappings to /var/log/messages, and they are correct. In any case, clients don't all have the same DNS domain name. > What does ps aux | grep rpc give? rpc 1616 0.0 0.0 18972 992 ? Ss Jun18 0:00 rpcbind rpcuser 1649 0.0 0.0 25420 1380 ? Ss Jun18 0:00 rpc.statd root 1678 0.0 0.0 0 0 ? S Jun18 0:00 [rpciod/0] root 1679 0.0 0.0 0 0 ? S Jun18 0:01 [rpciod/1] root 5789 0.0 0.0 50112 2072 ? Ss 12:06...

...elieve that rpc.idmapd is working as it should. Starting rpc.idmapd with -vvv dumps the mappings to /var/log/messages, and they are correct. In any case, clients don't all have the same DNS domain name. > What does ps aux | grep rpc give? rpc 1616 0.0 0.0 18972 992 ? Ss Jun18 0:00 rpcbind rpcuser 1649 0.0 0.0 25420 1380 ? Ss Jun18 0:00 rpc.statd root 1678 0.0 0.0 0 0 ? S Jun18 0:00 [rpciod/0] root 1679 0.0 0.0 0 0 ? S Jun18 0:01 [rpciod/1] root 5789 0.0 0.0 50112 2072 ? Ss 12:06...

...39;ve found a Bug in current rc2 (same occours with rc1 and 0.99.9.1). I'am running dovecot with imap, pop3 and the ssl equivalents, after a nessus scan of my host with Bruteforce checks on IMAP, imap-login eats up lots of cpu. Before the scan: dovecot 22342 0.0 0.1 2320 636 ? SN Jun18 0:00 imap-login dovecot 5841 0.0 0.1 2320 692 ? SN Jun21 0:00 imap-login dovecot 5852 0.0 0.1 2320 692 ? SN Jun21 0:00 imap-login Looks wonderfull ;) After the scan: dovecot 20059 39.5 0.2 2340 820 ? RN 20:02 14:08 imap-login dovecot 20733 0.0 0.2 2320...