It's UWAweek 50

help2002

This forum is provided to promote discussion amongst students enrolled in CITS2002 Systems Programming.
Please consider offering answers and suggestions to help other students! And if you fix a problem by following a suggestion here, it would be great if other interested students could see a short "Great, fixed it!"  followup message.
Displaying the 3 articles in this topic
Showing 3 of 835 articles.
Currently 8 other people reading this forum.


 UWA week 34 (2nd semester, week 5) ↓
SVG not supported

Login to reply

👍?
helpful
12:03pm Wed 21st Aug, ANONYMOUS

(20) Which of the following is NOT a reason for the fork system call failing? A. the user already has too many processes running. B. The whole computer system has exhausted is available memory. C. the value returned by fork is -1. D. the parameter passed to fork is not a valid process-identifier Anyone can tell why D is the not the reason? C:the value returned by fork is -1. C option seems to be the result not reason, right?


SVG not supported

Login to reply

👍?
helpful
1:53pm Wed 21st Aug, Zhengxun L.

First, I think C is also right answer because the question asks for "reason",and option C is the "result" caused by the fail. Option D is correct because it presents a scenario that is not applicable to the fork() system call. Since fork() does not accept parameters, there is no way for an "invalid process-identifier" to cause it to fail.


SVG not supported

Login to reply

👍?
helpful
2:36pm Wed 21st Aug, Christopher M.

"Zhengxun Lan" <22*6*3*5@s*u*e*t*u*a*e*u*a*> wrote:
> Option D is correct because it presents a scenario that is not applicable to the fork() system call. Since fork() does not accept parameters, there is no way for an "invalid process-identifier" to cause it to fail.
This is correct.

The University of Western Australia

Computer Science and Software Engineering

CRICOS Code: 00126G
Written by [email protected]
Powered by history
Feedback always welcome - it makes our software better!
Last modified  8:08AM Aug 25 2024
Privacy policy