Re: server doesn't detect closed sockets?

Thanks for providing runnable test code. I can reproduce the behavior you are seeing.

I'm not sure what the ->connected method is supposed to detect. Testing for not eof instead achieves the expected behavior. In the parent, change

while ($req->connected) {
[download]

until ( $req->eof ) {
[download]

Anno

Comment on Re: server doesn't detect closed sockets? Select or Download Code

Replies are listed 'Best First'.
Re^2: server doesn't detect closed sockets? by kingkongrevenge (Scribe) on Aug 02, 2007 at 13:04 UTC
`eof $req` is always false until the client has written to the socket and the data is unread, so that doesn't work. I looked at the source of `IO::Socket::connected` and it's just calling peername on the socket. So I inserted these lines into the while loop code to see what's going on: `print "peername: " . $req->peername . "\n"; print "peerpath: " . $req->peerpath . "\n";` [download] `peername` is always a string of one space, regardless of whether data has been written or read from the socket, or whether the socket has been closed in the client. How do I set the peername from the client side on a unix domain socket? Peerpath displays as binarygiberish1 the first call, binarygiberish2, the second, then binarygiberish3, and then the binarygiberish2 and binarygiberish3 alternate forever. What is the binary giberish and how can I unpack it? Maybe this is a useful testable value?	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^2: server doesn't detect closed sockets?
by kingkongrevenge (Scribe) on Aug 02, 2007 at 13:04 UTC

eof $req

I looked at the source of IO::Socket::connected and it's just calling peername on the socket. So I inserted these lines into the while loop code to see what's going on:

print "peername: " . $req->peername . "\n";
print "peerpath: " . $req->peerpath . "\n";
[download]

peername is always a string of one space, regardless of whether data has been written or read from the socket, or whether the socket has been closed in the client. How do I set the peername from the client side on a unix domain socket?

Peerpath displays as binarygiberish1 the first call, binarygiberish2, the second, then binarygiberish3, and then the binarygiberish2 and binarygiberish3 alternate forever. What is the binary giberish and how can I unpack it? Maybe this is a useful testable value?

[reply]
[d/l]
[select]