New Feature!

A while back I asked for your suggestions. What follows is an implementation of one of them that I think is a great addition to Eskimo. I hope that you agree.

If you go to our website, https://www.eskimo.com/, under Web Apps,  you will notice there is a new item called Host Terminal or Shell.

At the authentication prompt use:

Login: public
Password: public

This replaces the old SSH Shell functionality but is much better.

It allows connections to different hosts, it does not require Java  or anything other than an HTML5 compliant browser.

Second, if you choose Desktop rather than Terminal, you can get a full graphical desktop up and use any of the graphical applications from a web browser.

If you choose Terminal, you will get a text login prompt and you can type your login and password and then you will be in a terminal.

If you choose Desktop, you will get a graphical login prompt and you type your login and password and your desktop will appear.

Please be sure to logout when you are done or it can leave a session running wasting memory. If you are idle for 60 minutes, it will in theory timeout and tear the session down but this does not work 100% of the time.

I do not have sound working yet. There will be many changes to come to this and eventually all the hosts will be present. But I wanted people to get a look at it and start using as soon as possible so that I can be aware of any bugs while I’m still working on it.

I don’t have all the hosts working yet but will add them as I get them working.

      The web server was not responding because the encryption key and certificate of one of my customers sites did not match.  I was unaware this condition would affect the entire server.

     We will be rebooting the majority of our servers early in the morning shortly after midnight Saturday February 16th, 2019, for a kernel upgrade.

     The update of Apache to 2.4.38 has been completed.

     There will be a brief interruption in web servers (less than 60 seconds) to upgrade from Apache 2.4.37 to 2.4.38 later this afternoon.

     These machines had NFS and/or NIS issues after reboot last night but have been restored to service.

     I’m going to reboot all the servers sometime after midnight tonight, assuming power is still on and stable at that time, to make effective a kernel upgrade.

     I apologize for the brief interruption in services around 2:30PM today.  After I disabled quotas, all the free disk space went away.  Only problem is disk usage did not show it allocated to anyone.  Something in that machines kernel or file system was corrupted.  After I rebooted the machine, disk usage was back to 26% which is about normal.

     Still the quota system is acting weird.  I’ve turned it off (in theory) for now and will reboot the server and re-enable later tonight if it stays sane while turned off.  Because it’s a kernel process and not behaving properly I really can’t be sure that it is turned off so if it continues to be a problem I may be forced to boot the system in the day.

     Not sure why but the quota system went berserk today and decided I had about ten times as much disk usage as I actually had.  I do not know if other accounts were affected but I ran a system wide audit to correct the quota values.