Free Shell Accounts
Free SSH shells for you!

By: falcon | July 20, 2017

This morning, the power went out for the fourth time in about two weeks.  The shell server is directly connected to the power and although it is a laptop, the battery has no capacity and so it will turn off each time there is a power failure.  I turn it back on as soon as I can.


I don't know what is happening with our power grid, since prior to these two weeks, there hasn't been a power outage in two months.  And the power was steady for nearly a year before that.  But nonetheless, it is rendering my service quite unreliable.  I apologize to all users who have been inconvenienced by these outages.


What are my options?  I can try to obtain battery backup, either by purchasing another laptop with a working battery included, or I can purchase an uninterruptable power supply (UPS).  Either of these options would require donations of hundreds of dollars.  I doubt that would happen.


The only other thing I can think of is to switch to a virtual private server(VPS) located in a datacentre with included protection against power failures.  My residential ISP contract continues until Nov 2018, so I won't have funds available for a VPS until that contract is over.


Having examined my options, it doesn't look like there is anything I can do about it right now.  I did start this service primarily for those who want to learn Linux and the command line, and that is still possible for people who log in to try the commands and then log out.  It is only the secondary service of allowing users to run programs 24/7 which is affected by these power failures.  I suppose that if these users need reliability  then I have failed to be suitable for such usage.  I guess I can live with that.

Category: Uncategorized 

Tags: shell, server 

Comments:

Jerry

Posted on : November 18, 2017

These failures are now gone. You shouldn't worry about them. Order the bestessays writing at this site.


Alotl

Posted on : August 02, 2017

Hi, just minor issue. Your server's clock is 8 minutes behind a real time.
This can be easily fixed with command:

ntpdate 0.north-america.pool.ntp.org

from root's cron once a week. Use full patch to ntpdate.

Best!


Post a Comment