[RESOLVED] select() returns "ready" even after producer is done (FIFO)

Hello,

I have a producer application that writes data into a FIFO, and I have a consumer application that reads data from FIFO utilizing select() and read() functions inside of a while(true) loop.

After producer is done (it closes and unlinks FIFO) select() on the consumer side keeps endlessly returning "ready" state, and read() returns 0 bytes. I've expected select() to return -1 once the FIFO was closed but it's not the case.

How do I catch that FIFO was closed on the producer side?

Thank you.

P.S. I should post my code but it's a large application, it would take me time to make it into a small prototype. I'd appreciate if someone knows the answer without me having to post the code.

Quote:

---

Originally Posted by vincegata

it would take me time to make it into a small prototype.

---

You're talking about your problem as if people were clairvoyant. At least I'm not but what's pretty clear without any psychic powers is that you haven't applied a very basic and important design principle, namely encapsulation.

Since the FIFO functionality seems to be spread out all over the application you now have a hard time pinpointing the problem. I suggest you redesign the FIFO making it a class so you can test it in isolation (and post it here if you need help). Then integrate it with the application.

My FIFO is a class, it is the producer and consumer applications use select() to monitor sockets and stdin besides the FIFO so the loop is quite involved.

Anyways, select() is not supposed to return any error when the app on the write side is closed. Read() returns 0 for bytes read for an indication of EOF which also happens when writer is shutdown - that's is the explanation.