1994-02-05 - Running regularly

Header Data

From: hughes@ah.com (Eric Hughes)
To: cypherpunks@toad.com
Message Hash: 8c5f5b36072c83fc889344a6865fc2d81f2d963402ddb6a6f144d7540ea1abed
Message ID: <9402050100.AA22751@ah.com>
Reply To: <CMM-RU.1.3.760406745.matthew@gandalf.rutgers.edu>
UTC Datetime: 1994-02-05 01:05:18 UTC
Raw Date: Fri, 4 Feb 94 17:05:18 PST

Raw message

From: hughes@ah.com (Eric Hughes)
Date: Fri, 4 Feb 94 17:05:18 PST
To: cypherpunks@toad.com
Subject: Running regularly
In-Reply-To: <CMM-RU.1.3.760406745.matthew@gandalf.rutgers.edu>
Message-ID: <9402050100.AA22751@ah.com>
MIME-Version: 1.0
Content-Type: text/plain


>If it turns out that it was just the process that was automatically killed
>on a time interval, then you could easily write a script that would spawn a
>new process and then kill the parent.

To continue the explanation, no single process would ever execute for
a long time, since it would, phoenix-like, periodically die and be
reborn.

A clever mail filter hack could also check to see if it was still
alive (say, with a socket) and then start it running again if it had
stopped.

Eric





Thread