home bbs files messages ]

Just a sample of the Echomail archive

Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.

   RBERRYPI      Support for the Raspberry Pi device      21,939 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 18,986 of 21,939   
   56g.1183 to The Natural Philosopher   
   Re: How to safely power d   
   03 Jan 24 01:03:28   
   
   INTL 3:770/1 3:770/3   
   REPLYADDR 56g.1183@ztq4.net   
   REPLYTO 3:770/3.0 UUCP   
   MSGID: <1UudnZRUDqQtZQn4nZ2dnZfqnPSdnZ2d@earthlink.com> 43b80ae0   
   REPLY:  56ba87ea   
   PID: SoupGate-Win32 v1.05   
   On 12/14/23 5:23 AM, The Natural Philosopher wrote:   
   > On 13/12/2023 23:12, Pancho wrote:   
   >> ou could use a heart-beat type mechanism.   
   >>   
   >> The PiHole repeatedly sends a check to remote service, the heart-beat   
   >>   
   >> If the heart-beat stops, you can first get a script on the PiHole to   
   >> trigger a reboot itself, if the PiHole hasn't locked up.   
   >>   
   >> If the PiHole has genuinely frozen, doesn't recover in a timely way,   
   >> the remote end of the heart beat serivice could signal a seperate   
   >> tasmota style power switch to cycle the power on the PiHole.   
   >   
   > Experience shows that there are a range of situations that can disable   
   > user access. Some of them will also disable any self-rebooting type   
   > systems you might employ.   
   >   
   > In such cases the only option is a power cycle.   
   >   
   > BUT if its happening regularly, the answer is to FIX THE CODE that is   
   > causing it or replace the hardware.   
   >   
   > I remember one SPARC machine sent in to us thatĀ  'always worked for half   
   > an hour, but then stopped'   
   >   
   > CPU fan was wrecked by dust.   
   >   
   > Pis are cheap enough that a total swapout wont cost an ARM (sic!) and a   
   > legĀ  so that is the easiest way to eliminate a hardware fault.   
   >   
   > Code wise, you can disable services one at a time until its stable, or   
   > look in the log files,   
      
      
      There's a cheap, rude, crude, fix that I've used   
      for a number of units ... crontab a reboot at maybe   
      midnight. Clears all bullshit and errors from memory   
      and maybe only 60 seconds of downtime.   
      
      Linux/PI is good, but some kinds of errors and/or   
      memory leaks DO seem to accumulate despite best   
      efforts.   
      
      Crontab a root @reboot to get everything going again.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)   
   SEEN-BY: 10/0 1 15/0 90/1 103/705 105/81 106/201 128/260 129/305 135/225   
   SEEN-BY: 153/757 7715 218/0 1 601 700 840 870 930 220/70 221/1 6 226/17   
   SEEN-BY: 226/30 100 227/114 229/110 112 113 200 206 307 317 400 426   
   SEEN-BY: 229/428 452 470 550 616 664 700 240/1120 266/512 267/800   
   SEEN-BY: 282/1038 291/111 292/854 301/1 113 812 310/31 320/219 322/757   
   SEEN-BY: 335/364 341/66 342/200 396/45 460/58 633/280 712/848 770/1   
   SEEN-BY: 770/3 100 330 340 772/210 220 230 5020/400 1042 5058/104   
   SEEN-BY: 5075/35   
   PATH: 770/3 1 218/840 221/6 301/1 218/700 229/426   
      

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca