Today at 13:00 we had to reboot plompy, one of our LTSP terminal servers. We're sorry for any inconvenience. In order to prevent those terminal servers from clogging up memory in the future, we hereby announce the following maintenance reboot schedule:

plompy: first Sunday of each month, 02:00 am
plimpy: third Sunday of each month, 02:00 am

There will always be one functioning terminal server and upon login your thin client will choose the right one. Please don't forget to save your data when leaving for the weekend before those two Sunday dates (that's always a good idea anyways).

On Friday, September 17, at 22:00,  we will have to extraordinarily reboot our 64-bit Ubuntu workstations in order to deal with a nasty security issue. We're sorry for the short notice but we've been unpleasantly surprised by this just as much as you have. If you're reading this in time, please save all your data and log out if you can. Please note that also the terminal servers plimpy, plompy, plempy and plumpy (yes I know..) are affected. Thank you.

A firmware update on the RAID controller of our file server requires a reboot of this server. We schedule the reboot on Wednesday August 4, at 22:00. The downtime should take no more than 30 min. Please make sure all your data has been saved at that point.

We apologize for any inconvenience.

Update, 22:20: The server has rebooted and everything should work again.

Our terminal server plimpy (uptime: 47 days) is slowly clogging up with runaway processes, eating up memory and CPU. Since we cannot tell apart good processes from bad ones, we schedule a maintenance reboot for the Weekend, Saturday night June 19th in order to give the system a fresh start. We ask all users to save their data and log out of their thin clients.

BTW: Users of second generation thin clients (named tc00xx) are kindly invited to test our new ubuntu based terminal server plompy. If you're interested to give it a try, please let us know and we will configure your client.

Our terminal server plimpy (uptime: 80 days) is slowly clogging up with runaway processes, eating up memory and CPU. Since we cannot tell apart good processes from bad ones, we schedule a maintenance reboot for tomorrow, Wednesday February 24 at 18:00 in order to give the system a fresh start. We ask all users to save their data and log out of their thin clients. Update, 18:45: Plimpy is up and running again.

The update also affects "plimpy", our LTSP server. Please remember to save all your documents and log out this evening.

We installed new linux kernels for our systems and the machines need to be rebooted to run the new kernel. We will reboot the D-PHYS Linux Workstations this evening after 08:00 pm. Please log out this evening before you go home, save all unsaved work and don't start any long running jobs. You may also reboot your workstation yourself earlier.

Today around 14:20 the D-PHYS network started acting up. After about 20 minutes the problem could be tracked down to a machine running amok. Unfortunately, the terminal server plimpy did not survive the downtime and had to be rebooted at 16:10. We apologize for any inconvenience.