On 22/05/17 08:36, Mike Scott wrote:
> On 19/05/17 09:32, The Natural Philosopher wrote:
>> On 19/05/17 09:28, Mike Scott wrote:
>>> On 18/05/17 22:31, Martin Gregorie wrote:
>>> ....
>>>>> I would imagine a startup script could be inserted into teh init.d
>>>>> system to, after the window manager stars up launch what apps in what
>>>>> window arrangements are desirable
>>>>>
>>>> Yes, that would work, and you could use frequently executed cron
>>>> jobs to
>>>> detect that some application has fallen over and restart it,
>>>> emailing yo
>>>> an alarm if it fails more than 'n' times in a row.
>>>
>>> Am I missing something here? What's wrong with each task being
>>> wrapped in a trivial shell script that loops forever, eg:
>>>
>>> while true; do xterm -e ssh myhost;  mail root -s 'ssh exited'
>>> >>
>>> or similar.
>>>
>>
>> Hmm. You are assuming it crashes in a way that will exit back to that?
>
> No, just fulfilling the OP's stated requirement: "Web browser and
> terminal windows should restart and connect to predefined addresses if
> closed by accident."
>

You don't think that crashing is a member of the set of 'closed by
accident' then?



>>
>> When we did watchdogs in milspec stuff it tended to be within the app,
>> write a number that increments every time you write it, outside the
>> app (under timer interrupt) if the number doesnt get updated for n
>> seconds, destroy the process and recreate it. (or in many cases reboot
>> the whole embedded system)
>>
>> That takes care of 'hung' processes as well
>
> Horses for courses. I don't think the OP is concerned to that level. IMBW.
>>
>>
>>
>
>


--
"I am inclined to tell the truth and dislike people who lie consistently.
This makes me unfit for the company of people of a Left persuasion, and
all women"

--- SoupGate-Win32 v1.05