R. Clayton (rclayton@monmouth.edu)
(no date)
I think that batch processing or a single process scheduler is not the
correct answer as they don't guarantee that deadlock can't happen.
That's possible, although I'd need to hear a description of how deadlock might
occur.
As a single process (batch process) can try and allocate more resources than
the Os can supply and then with usual kind of resources and even though there
is a single process only, there is still a deadlock possibility.
Except that a process that requests more resources than exists will be denied,
which will lead to termination or whatever. Asking for more resources than
exist should never lead to deadlock because such requests can never be granted.
I asked the undergraduates if a process can deadlock with itself. Because it
can, it might be possible to argue that case for this question, but it would be
a weak argument because the mechanism that leads to deadlock (self joining)
wouldn't probably be available in a monoprograming system.
You might be able to argue that a process could deadlock with the operating
system (it's been known to happen). Off hand, I can't think of any way this
could occur legitimately, rather than because of a design or implementation
error.
This archive was generated by hypermail 2.0b3 on Fri Aug 23 2002 - 19:30:04 EDT