Why is select used in Linux

Programs that want to continue running while also reading interactive user input¹ need to be multithreaded or they need to read input streams carefully and, specifically, conditionally.

Select(2) can be used to implement the second design pattern. It can determine whether input can be read without blocking the entire application.

---

^{1. Or some other input that arrives unpredictably.}

The select() system call tells you whether there is any data to read on the file descriptors that you're interested in. Strictly, it is a question of whether a read operation on the file descriptor will block or not.

If you execute read() on a file descriptor — such as that connected to a serial port — and there is no data to read, then the call will hang until there is some data to read. Programs using select() do not wish to be blocked like that.

You also ask:

Why do we have to increment the file descriptor by 1 and pass it while I am passing the file descriptor set already to select?

That's probably specifying the size of the FD_SET. The first argument to select() is known as nfds and POSIX says:

The nfds argument specifies the range of descriptors to be tested. The first nfds descriptors shall be checked in each set; that is, the descriptors from zero through nfds-1 in the descriptor sets shall be examined.

So, to test a file descriptor n, the value in nfds must be at least n+1.

You use select call when you have to constantly monitor file descriptors until they get ready for some IO without blocking.

Generally used when you want the IO (eg read() )non-blocking , read the :man page

Also read the related API's