Path: utzoo!attcan!uunet!ncrlnk!ncrcae!hubcap!gatech!ncar!mailrus!cornell!oravax!fred
From: fred@oravax.UUCP (Charles Mills)
Newsgroups: comp.unix.questions
Subject: Re: Implement a Remote Fork facility
Message-ID: <529@oravax.UUCP>
Date: 9 Nov 88 20:21:13 GMT
References: <1777@pembina.UUCP> <16@elgar.UUCP> <8831@smoke.BRL.MIL>
Reply-To: fred@oravax.odyssey.UUCP (Charles Mills)
Organization: Odyssey Research Associates, Ithaca, New York
Lines: 19

In article <8831@smoke.BRL.MIL> gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>) writes:
>In article <16@elgar.UUCP> ag@elgar.UUCP (Keith Gabryelski) writes:
>>How does one stop a process in a way that it can be restarted after a
>>cold boot?
>
>You obviously can't, in general.

Wouldn't it be appropriate to explain why this is obvious?  It clearly wasn't
obvious, for example, to ag@elgar.UUCP (Keith Gabryelski).

Certainly there's no way of ensuring that the process's open file descriptors
can be meaningfully assigned when it's restarted, and perhaps it's this
to which you allude.  Except for that, though, I see no particular
problem in principle, though all the solutions I've heard about have
defects or failures of generality.  If you are aware of other reasons
why it can't be done, I'm sure I'm not the only person who'd be curious to
see them.

fred