keeping proccess active after client closed connection

From: Ilya (no email)
Date: Wed Apr 03 2002 - 20:53:53 EST


Ive seen reports of Cyrus not closing TCP connection in mail list,
but no resolution to that problem.
I am seeing a similar issue on FreeBSD 4.5 with cyrus imap 2.1.3.
after telnet localhost 110
login and logout
the process for pop3 daemon is still present in the system after an hour:
11692 ?? I 0:00.04 pop3d: pop3d: alchemistry.net[192.168.0.3] (pop3d)
if I kill master process, 11692 still stays. I have to kill it manually to
get rid of it.
if i dont kill the process manually, master will not start properly, it says the
port is already taken.
same thing happens with imap. quick login with a mail client and than logout
and after 30min I still can see imapd process browsing the folder which mail client
opened.

cyrus imap 2.1.3
cyrus-sasl 2.1.2
everything on skiplist
FreeBSD 4.5 stable
START {
  recover cmd="ctl_cyrusdb -r"
}
SERVICES {
  imap cmd="imapd" listen="imap" prefork=0
  imaps cmd="imapd -s" listen="imaps" prefork=0
  pop3 cmd="pop3d" listen="pop3" prefork=0
  pop3s cmd="pop3d -s" listen="pop3s" prefork=0
  sieve cmd="timsieved" listen="sieve" prefork=0
  lmtpunix cmd="lmtpd" listen="/var/imap/socket/lmtp" prefork=0
}

EVENTS {
  checkpoint cmd="ctl_cyrusdb -c" period=30
  delprune cmd="ctl_deliver -E 3" period=1440
  tlsprune cmd="tls_prune" period=1440
}








Hosted Email Solutions

Invaluement Anti-Spam DNSBLs



Powered By FreeBSD   Powered By FreeBSD