background process and problems with connection

[rspadim]

guys when running as a background process, forever
while(1){ read emails from database; send email; disconnect; }

i get a lot of close_wait at netstat, i think it's a netsocket problem, but i changed net socket to shutdown() and fclose() the socket before close, and it persist, any idea what could we do?

check netstat running 1hour (near to 100emails), i'm using non persistent connections

[beto@xyz ~]# netstat -an | grep CLOSE_WAIT
tcp 54 0 192.168.0.5:34375 208.84.244.140:587 CLOSE_WAIT
tcp 54 0 192.168.0.5:34365 208.84.244.140:587 CLOSE_WAIT
tcp 54 0 192.168.0.5:34390 208.84.244.140:587 CLOSE_WAIT
tcp 54 0 192.168.0.5:34385 208.84.244.140:587 CLOSE_WAIT
tcp 54 0 192.168.0.5:34379 208.84.244.140:587 CLOSE_WAIT
tcp 54 0 192.168.0.5:34369 208.84.244.140:587 CLOSE_WAIT
tcp 54 0 192.168.0.5:34362 208.84.244.140:587 CLOSE_WAIT
tcp 54 0 192.168.0.5:34366 208.84.244.140:587 CLOSE_WAIT
tcp 54 0 192.168.0.5:34360 208.84.244.140:587 CLOSE_WAIT
tcp 54 0 192.168.0.5:34383 208.84.244.140:587 CLOSE_WAIT
tcp 54 0 192.168.0.5:34368 208.84.244.140:587 CLOSE_WAIT
tcp 54 0 192.168.0.5:34364 208.84.244.140:587 CLOSE_WAIT
tcp 54 0 192.168.0.5:34372 208.84.244.140:587 CLOSE_WAIT
tcp 54 0 192.168.0.5:34357 208.84.244.140:587 CLOSE_WAIT

[CloCkWeRX]

#9

[rspadim]

guy checking all possible shutdown/close, i think the problem is the openssl actived and streams, i don't know how to include a shutdown in stream code or if it exists when using openssl, maybe we should send this problem to php bug tracker, creating a reprodutible test case
something like connect, set crypt on, disconnect, execute this 1000 times and you have many CLOSE_WAIT

[jparise]

Related: pear/Net_Socket#4

[jparise]

There hasn't been any activity on this issue in years so I'm going to close it. Please reopen it if there's new or additional information.