> What I am failing to understand is that the "OS can never put these processes
> to sleep". If that is true then what about the kernel total control of the sys
> resources? What about the kernel always dividing sys resources among users
> according to sys policy?
>
> I am still thinking that the assertion about "the OS can never put these
> processes to sleep" is not accurate. Am I wrong?
>
>
It can put them to sleep, in a sense that it can do anything. It also can reboot the
system or format your hard drive; but it won't put it to sleep since the process
keeps doing stuff; there is no point making a process that is doing something
sleep.
>
> > If you're continually calling the kernel, how could it put your app to
> > sleep? That's what they invented select/poll for.
> >
>
Yep
>
> BTW: I should have said that the section of the book I was referring to was a
>preparation for their discussion about select. Basically, a process like the one
> I am referring to is a demo process which does
> while (forever) {
> read(NON_BLOCKING I/O file descriptor)
> }
Actually, it DOES put it to sleep any time you call read(), but it immediatly wakes up
:)
>
>
> =================================================================
> To unsubscribe, send mail to [EMAIL PROTECTED] with
> the word "unsubscribe" in the message body, e.g., run the command
> echo unsubscribe | mail [EMAIL PROTECTED]
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
