Hi Bert,

Thanks for the help.  I was trying to solve a problem adjusting things
after an image restart and got into the weeds with fixing variables holding
what should be the current date and time.  That fix could have had a timing
problem with when the image was saved.  As it turns out adding a #startUp
class method allows me to easily fix things without concern for dates and
time and where the code was when the image was saved.

Lou

On Thu, 28 Feb 2013 23:30:08 +0100, Bert Freudenberg <bert at freudenbergs.de>
wrote:

>On 2013-02-28, at 22:38, Louis LaBrunda <Lou at Keystone-Software.com> wrote:
>
>> If a process is running when an image is saved, is the process stopped at
>> any point in particular?
>
>The active process is stopped in the snapshot primitive (a.k.a. "image saving") and resumes after it on startup. All other processes are waiting on some semaphore anyway.
>
>> If the saved image is started, is there any way the process can tell?
>
>Not the process itself. But you surely keep the process in a class somewhere, and the class can arrange to get notified on startup by adding itself to the startup list. See addToStartUpList:.
>
>> I'm running a process that keeps running for a look time.  It loops with a
>> delay and in the loop gets the date and time.  If the date and time were
>> obtained just before the save, they would be old at the time of the image
>> restart and need to be refreshed.
>
>
>Delays get adjusted after resuming from snapshot. So it should just work.
>
>- Bert -
>
>
-----------------------------------------------------------
Louis LaBrunda
Keystone Software Corp.
SkypeMe callto://PhotonDemon
mailto:Lou at Keystone-Software.com http://www.Keystone-Software.com