Re^3: Object Destructors and Signals

I'm just trying to catch the failure sooner rather than later.

The more often the worker updates the "I'm alive" timestamp, the sooner you can catch failures. It sounds like it doesn't update the timestamp at all right now.

Comment on Re^3: Object Destructors and Signals

Replies are listed 'Best First'.
Re^4: Object Destructors and Signals by bot403 (Beadle) on Nov 05, 2010 at 19:41 UTC
Oh I see. I have a generic "This row was last updated @" timestamp. I dont have an "I'm Alive" timestamp. Currently, working with the object involves spawning an external process that might not return for 1 minute or 100. I'm not sure when I'd get the chance to update the "I'm alive" timestamp while that operation is happening unless I spawned threads. However, its a neat idea and is hitting on a more genreal approach of using some sort of watchdog process either external or internal.	[reply]

Replies are listed 'Best First'.

Re^4: Object Destructors and Signals
by bot403 (Beadle) on Nov 05, 2010 at 19:41 UTC

Oh I see. I have a generic "This row was last updated @" timestamp. I dont have an "I'm Alive" timestamp.

Currently, working with the object involves spawning an external process that might not return for 1 minute or 100. I'm not sure when I'd get the chance to update the "I'm alive" timestamp while that operation is happening unless I spawned threads.

However, its a neat idea and is hitting on a more genreal approach of using some sort of watchdog process either external or internal.

[reply]