Article View: comp.std.unix
Article #676Re: qfork()
From: terri_watson
Date: Wed, 26 Dec 1990 22:42
Date: Wed, 26 Dec 1990 22:42
21 lines
1046 bytes
1046 bytes
Submitted-by: terri_watson@cis.ohio-state.edu Of course assuming that the parent doesn't care about the return value of qfork(), then one could manage to conform to the restrictions by: if (qfork() == 0) exit(execve(...)); or for the truly sick-at-heart: (status = qfork()) ? 1 : exit(execve(...)); (Of course it _could_ be argued that, in the second example, the very assignment of status = qfork() violates the rules, but I thought the humor value was high.) But _I'm_ not writing code like that! <grin> Terri Volume-Number: Volume 22, Number 40
Technical Details
Message-ID:
<16243@cs.utexas.edu>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!jsqReferences:
<16066@cs.utexas.edu> <16213@cs.utexas.edu>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!jsq From: terri_watson@cis.ohio-state.edu Newsgroups: comp.std.unix Subject: Re: qfork() Message-ID: <16243@cs.utexas.edu> Date: 26 Dec 90 22:42:07 GMT References: <16066@cs.utexas.edu> <16213@cs.utexas.edu> Sender: jsq@cs.utexas.edu Organization: Ohio State Computer Science Lines: 21 Approved: jsq@cs.utexas.edu (Moderator, John S. Quarterman) X-Submissions: std-unix@uunet.uu.net