XPost: alt.os.linux, sci.electronics.repair   
   From: robin_listas@es.invalid   
      
   On 2017-11-15 14:26, Peter Köhlmann wrote:   
   > Carlos E.R. wrote:   
   >   
   >> On 2017-11-15 08:25, ATANARJUAT wrote:   
   >>> On Wed, 15 Nov 2017 07:22:29 -0000 (UTC), Blake Snyder wrote   
   >>>  in response to Blake Snyder    
   >>>   
   >>>> Klugey approach?   
   >>>>   
   >>>> Set a WatchDog Timer reboot.   
   >>>>   
   >>>> Specify an IP that won't respond to pings, set up the WatchDog timer to   
   >>>> ping it every 24*60*60 seconds, with a fail count of 7. (or suitable   
   >>>> numbers that the GUI will accept).   
   >>>   
   >>> You could even have it ping a machine on your network somewhere that you   
   >>> could take off-line when you wanted to reboot everything.   
   >>   
   >> Do you know of a reasonably cheap hardware device that can monitor   
   >> something on the network, and powercycle it when needed? A watchdog that   
   >> acts on a hung device, say.   
   >>   
   >> I know one or two, but they are expensive.   
   >> A timer reboot is too aggressive when a reboot is not needed.   
   >>   
   >   
   > Use a Raspberry   
      
   Yes, that's one of the methods I'm considering for when I have the time.   
      
   --   
   Cheers, Carlos.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)