View Single Post
  #2   Spotlight this post!  
Unread 18-02-2016, 10:24
techhelpbb's Avatar
techhelpbb techhelpbb is offline
Registered User
FRC #0011 (MORT - Team 11)
Team Role: Mentor
 
Join Date: Nov 2010
Rookie Year: 1997
Location: New Jersey
Posts: 1,622
techhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond repute
Re: Shutting Down a Robot-Mounted Pi

Quote:
Originally Posted by viggy96 View Post
Hmmmm... Let's see, first, was referring purely to the software when I made those statements, not the hardware, and yes you can run into issues dealing with the SD card if the power is suddenly cut, IN SOME CASES. If you have set it up, correctly, and are using it as a vision co-processor, all you are doing is cutting the power while a programme is running. I have done exactly this hundreds, actually thousands, of times, with a Pi B+. I have used it for vision, and just unplugged it to turn it off. Every time, it booted correctly the next time I needed it. Of course, during setup, I made sure to never to that.

So please folks, don't question my intelligence.
It is possible if you are running Arch Linux with the swap file OFF that your systems will only be writing to storage when and if your application writes to storage. Raspbain quite often has swap enabled and written to the SD card. Depending on how swappiness (yes that's not made up it's a real thing) is setup your kernel may or may not use that swap if the memory space of your application starts to use up too much of the system's actual RAM.

This is not to question to you, or anyone's intelligence, just a point that currently I have 50,000+ copies of Linux online and running in various public and private clouds and datacenters. The smart thing to do is do a proper shutdown unless you know for a fact you've controlled the risk or have no better option.

For example I used to take Dell OptiPlex systems I had as leftovers from upgrades and put Ubuntu on them. Mess with the disk settings to spin down the hard drives and spin them up only on demand or every 6 hours (which ever was first and then spin them back down in 5 minutes). I would increase the write cache large enough that casual writes would come back from memory. I would remove the swap so that would not qualify to spin up the hard drive. Most of the drives lasted beyond 8 years and those that did not were already questionable (had de-allocated bad sectors that weren't mapped at the factory). These systems were used for print server farms like a giant version of the HP JetDirect driving down the cost of the printers because we could print to CUPS raw queues from Windows happily.

So again - there's plenty of simple ways shown here to accomplish this task from using a button and a script or SSH.
Why run any risk you don't need to?
Unlike other applications out there you really might take the chance you have an issue in the next match that hurts your competitive edge.

Last edited by techhelpbb : 18-02-2016 at 10:28.