Re: keeping proccess active after client closed connection (more info)
Ilya wrote:
>
> sorry to reply to my own message. but here is a little bit more info
> output of truss on imapd process which stayed active after client closed
> connection,it starts just before i quit mutt
>
> select(0x1,0xbfbff2e4,0x0,0x0,0xbfbff2c8)= 1 (0x1)
> gettimeofday(0xbfbff26c,0x0) = 0 (0x0)
> read(0x0,0x812a000,0x5) = 5 (0x5)
> read(0x0,0x812a005,0x28) = 40 (0x28)
> stat("cyrus.index",0xbfbff314) = 0 (0x0)
> fstat(13,0xbfbff314) = 0 (0x0)
> flock(0xe,0x2) = 0 (0x0)
> lseek(14,0x430,0)= 1072 (0x430)
> write(14,0xbfbfefcc,4) = 4 (0x4)
> lseek(14,0x434,0)= 1076 (0x434)
> write(14,0xbfbfefcc,4) = 4 (0x4)
> lseek(14,0x438,0)= 1080 (0x438)
> write(14,0xbfbfefcc,4) = 4 (0x4)
> lseek(14,0x43c,0)= 1084 (0x43c)
> write(14,0xbfbfefcc,4) = 4 (0x4)
> lseek(14,0x19f4,0) = 6644 (0x19f4)
> writev(0xe,0xbfbff094,0xa) = 236 (0xec)
> fsync(0xe) = 0 (0x0)
> lseek(14,0x1ae0,0) = 6880 (0x1ae0)
> write(14,0xbfbff270,4) = 4 (0x4)
> fsync(0xe) = 0 (0x0)
> flock(0xe,0x8) = 0 (0x0)
> munmap(0x2838f000,0x8000)= 0 (0x0)
> munmap(0x283f1000,0x56000) = 0 (0x0)
> close(11)= 0 (0x0)
> munmap(0x28386000,0x96) = 0 (0x0)
> close(12)= 0 (0x0)
> munmap(0x28387000,0x8000)= 0 (0x0)
> close(13)= 0 (0x0)
> munmap(0x2839b000,0x56000) = 0 (0x0)
> sendto(0x6,0xbfbff284,0x1e,0x0,0x8103ac0,0x10) ERR#2 'No such file or
> directory'
> open("/var/imap/msg/shutdown",0,00) ERR#2 'No such file or
> directory'
> select(0x1,0xbfbff2e4,0x0,0x0,0xbfbff2c8)= 0 (0x0)
> write(1,0x8134000,53)= 53 (0x35)
> gettimeofday(0xbfbff26c,0x0) = 0 (0x0)
> select(0x1,0xbfbff2e4,0x0,0x0,0xbfbff2c8)= 1 (0x1)
> gettimeofday(0xbfbff26c,0x0) = 0 (0x0)
> read(0x0,0x812a000,0x5) = 5 (0x5)
> read(0x0,0x812a005,0x28) = 40 (0x28)
> sendto(0x6,0xbfbff294,0x1f,0x0,0x8103ac0,0x10) ERR#2 'No such file or
> directory'
> write(1,0x8134000,69)= 69 (0x45)
> sendto(0x6,0xbfbff6b4,0x1f,0x0,0x8103ac0,0x10) ERR#2 'No such file or
> directory'
> close(8) = 0 (0x0)
> unlink(0x8107d40)= 0 (0x0)
> close(0) = 0 (0x0)
> close(1) = 0 (0x0)
> close(2) = 0 (0x0)
> break(0x8135000) = 0 (0x0)
> write(3,0xbfbff8b0,4)= 4 (0x4)
> sigaction(SIGALRM,0xbfbff89c,0x0)= 0 (0x0)
> setitimer(0x0,0xbfbff894,0xbfbff884) = 0 (0x0)
> SIGNAL 14
> SIGNAL 14
> SIGNAL 14
> fcntl(0x7,0x9,0xbfbff900)ERR#92 'Unknown error: 92'
> sigreturn(0xbfbff724)ERR#92 'Unknown error: 92'
>
> PS
> i dont have "/var/imap/msg/shutdown" , but should I? my msg directory is empty
No! This will prevent users from logging in (after displaying the
shutdown message as an ALERT).
Ken
--
Kenneth Murchison Oceana Matrix Ltd.
Software Engineer 21 Princeton Place
716-662-8973 x26 Orchard Park, NY 14127
--PGP Public Key--http://www.oceana.com/~ken/ksm.pgp
Re: keeping proccess active after client closed connection (more info)
sorry to reply to my own message. but here is a little bit more info
output of truss on imapd process which stayed active after client closed
connection,it starts just before i quit mutt
select(0x1,0xbfbff2e4,0x0,0x0,0xbfbff2c8)= 1 (0x1)
gettimeofday(0xbfbff26c,0x0) = 0 (0x0)
read(0x0,0x812a000,0x5) = 5 (0x5)
read(0x0,0x812a005,0x28) = 40 (0x28)
stat("cyrus.index",0xbfbff314) = 0 (0x0)
fstat(13,0xbfbff314) = 0 (0x0)
flock(0xe,0x2) = 0 (0x0)
lseek(14,0x430,0)= 1072 (0x430)
write(14,0xbfbfefcc,4) = 4 (0x4)
lseek(14,0x434,0)= 1076 (0x434)
write(14,0xbfbfefcc,4) = 4 (0x4)
lseek(14,0x438,0)= 1080 (0x438)
write(14,0xbfbfefcc,4) = 4 (0x4)
lseek(14,0x43c,0)= 1084 (0x43c)
write(14,0xbfbfefcc,4) = 4 (0x4)
lseek(14,0x19f4,0) = 6644 (0x19f4)
writev(0xe,0xbfbff094,0xa) = 236 (0xec)
fsync(0xe) = 0 (0x0)
lseek(14,0x1ae0,0) = 6880 (0x1ae0)
write(14,0xbfbff270,4) = 4 (0x4)
fsync(0xe) = 0 (0x0)
flock(0xe,0x8) = 0 (0x0)
munmap(0x2838f000,0x8000)= 0 (0x0)
munmap(0x283f1000,0x56000) = 0 (0x0)
close(11)= 0 (0x0)
munmap(0x28386000,0x96) = 0 (0x0)
close(12)= 0 (0x0)
munmap(0x28387000,0x8000)= 0 (0x0)
close(13)= 0 (0x0)
munmap(0x2839b000,0x56000) = 0 (0x0)
sendto(0x6,0xbfbff284,0x1e,0x0,0x8103ac0,0x10) ERR#2 'No such file or
directory'
open("/var/imap/msg/shutdown",0,00) ERR#2 'No such file or
directory'
select(0x1,0xbfbff2e4,0x0,0x0,0xbfbff2c8)= 0 (0x0)
write(1,0x8134000,53)= 53 (0x35)
gettimeofday(0xbfbff26c,0x0) = 0 (0x0)
select(0x1,0xbfbff2e4,0x0,0x0,0xbfbff2c8)= 1 (0x1)
gettimeofday(0xbfbff26c,0x0) = 0 (0x0)
read(0x0,0x812a000,0x5) = 5 (0x5)
read(0x0,0x812a005,0x28) = 40 (0x28)
sendto(0x6,0xbfbff294,0x1f,0x0,0x8103ac0,0x10) ERR#2 'No such file or
directory'
write(1,0x8134000,69)= 69 (0x45)
sendto(0x6,0xbfbff6b4,0x1f,0x0,0x8103ac0,0x10) ERR#2 'No such file or
directory'
close(8) = 0 (0x0)
unlink(0x8107d40)= 0 (0x0)
close(0) = 0 (0x0)
close(1) = 0 (0x0)
close(2) = 0 (0x0)
break(0x8135000) = 0 (0x0)
write(3,0xbfbff8b0,4)= 4 (0x4)
sigaction(SIGALRM,0xbfbff89c,0x0)= 0 (0x0)
setitimer(0x0,0xbfbff894,0xbfbff884) = 0 (0x0)
SIGNAL 14
SIGNAL 14
SIGNAL 14
fcntl(0x7,0x9,0xbfbff900)ERR#92 'Unknown error: 92'
sigreturn(0xbfbff724)ERR#92 'Unknown error: 92'
PS
i dont have "/var/imap/msg/shutdown" , but should I? my msg directory is empty
On Wed, Apr 03, 2002 at 08:53:53PM -0500, Ilya wrote:
> 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 {
> checkpointcmd="ctl_cyrusdb -c" period=30
> delp
keeping proccess active after client closed connection
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 {
checkpointcmd="ctl_cyrusdb -c" period=30
delprune cmd="ctl_deliver -E 3" period=1440
tlsprune cmd="tls_prune" period=1440
}
