I noticed the problem with dynDNS only.
However root of the bug is in ewget lib, and I'm not sure if this is even noticeable in ewget.
Search found 3 matches
- Tue Aug 23, 2011 2:41 am
- Forum: Other Issues
- Topic: ddns_gargoyle leaves sockets in CLOSE_WAIT status
- Replies: 5
- Views: 3695
- Mon Aug 22, 2011 5:30 pm
- Forum: Other Issues
- Topic: ddns_gargoyle leaves sockets in CLOSE_WAIT status
- Replies: 5
- Views: 3695
Re: ddns_gargoyle leaves sockets in CLOSE_WAIT status
ddns-gargoyle leaves open sockets, so you have to restart it to free resources.
- Sun Aug 21, 2011 8:43 am
- Forum: Other Issues
- Topic: ddns_gargoyle leaves sockets in CLOSE_WAIT status
- Replies: 5
- Views: 3695
ddns_gargoyle leaves sockets in CLOSE_WAIT status
Hello,
I'm using Gargoyle 1.3.16
I've notice a problem, that ddns_gargoyle is leaving CLOSE_WAIT connections.
As I can see the libewget.c (used by ddns_gargoyle) has a bug in destroy_connection_http function.
Shouldn't be there close(socket) before free(socket)?
Best Regards,
MJ
I'm using Gargoyle 1.3.16
I've notice a problem, that ddns_gargoyle is leaving CLOSE_WAIT connections.
As I can see the libewget.c (used by ddns_gargoyle) has a bug in destroy_connection_http function.
Shouldn't be there close(socket) before free(socket)?
Best Regards,
MJ