theCAT
  
Report a Problem:
Email: support@cat.pdx.edu
Phone: 503-725-5420
Location: FAB 82-01
  USERS PLATFORMS SYSTEM RESOURCES    
Home Students Fac/Staff CS Tutors Guidelines Windows Linux Mac Mail Network Software Web TheCAT Sitemap Contact
arrowHome arrow Home arrow News Sunday, 19 February 2017  
Home
News
Eduroam access now available to PSU faculty/staff/students Print
Written by Janaka Jayawardena   
Thursday, 02 February 2017

PSU (via the Office of Information Technologies) has joined Eduroam. If you travel to other campuses, this means that your Odin ID login credentials can be used to get on the Internet by using the wifi at cooperating academic/research institutions. This includes local universities, such as OSU and UO, as well as a large list of US-based institutions:


https://www.eduroam.us/institutions_list


and international locations:


https://www.eduroam.org/where/

 

Read more...
Time to switch to our new OpenVPN server Print
Written by Janaka Jayawardena   
Tuesday, 31 January 2017

 If you are a current OpenVPN user, we would like you to move to this new server as soon as you can. If you have not downloaded a new configuration from the CAT website in the last month or so, you will need to update your OpenVPN settings. Please visit:


https://cat.pdx.edu/network/vpn-services-in-mcecs-2.html


and go through the section that is appropriate for your computer. We would like to decommission the old OpenVPN server soon.




Read more...
Redhat Linux Systems are firewalled Print
Written by Janaka Jayawardena   
Monday, 16 January 2017

As of late December, 2016, all our CAT supported RedHat systems are firewalled from the Internet. This is to prepare us for end-of-support for RedHat 5 as well as the slower distribution of patches. Systems affected are:


eve.ece.pdx.edu

walle.ece.pdx.edu

mo.ece.pdx.edu


archive.cecs.pdx.edu


If you are accessing these systems remotely for the purposes of ssh/VNC/X, you will need to ensure that you are on the VPN. To learn about OpenVPN access to the MCECS network, start here:

 https://cat.pdx.edu/network/vpn-services-in-mcecs-2.html

 

Last Updated ( Monday, 16 January 2017 )
Automated killing of X/VNC Sessions Print
Written by Janaka Jayawardena   
Thursday, 12 January 2017

[This only applies to our Linux users with graphical sessions. Regular remote logins to a shell using ssh are not affected.]


Our automated termination of idle VNC/X sessions has been in place for many years. As of Fall 2016, we also introduced automatic termination of Linux workstation logins deemed to be idle. Here is what our current set of controls looks like:


Linux Lab Workstations


Any workstation login session idle for over 3 hours will be terminated. The affected workstation session receives a popup warning window that is displayed on the desktop 10 minutes before the session is terminated. Idle implies no X server user input.


Affects:


CS Linux lab workstations

FAB 55-17 Linux workstations

ECE VLSI Lab workstations


VNC/X termination


All remotely established VNC/X sessions that are idle for over 48 hours are terminated. Idle implies no X server user input.


Affects:


ECE: eve, walle, mo, velocesolo

CS: ada, babbage, CS Linux lab systems

MCECS: ruby, rita, FAB 55-17 Linux workstations


We find that many users forget to log off when leaving the labs, resulting in locked workstations. We also find that many VNC/X users will not re-attach to their old sessions, starting new ones instead. These control measures have been taken to ensure availability of resources to all the users of these systems.

 

These controls are not in effect on research-focused compute servers or desktops.


If you are planning on running long running un-attended sessions using either of these graphical desktop based environments, learn about the guidelines for running them at:

 https://cat.pdx.edu/guidelines/long-running-jobs.html

and then contact the CAT for consultation and approval if your use requires it. (Approval is based on resource consumption and non-peak-time use.)

Last Updated ( Thursday, 12 January 2017 )
Explorer Freezing on Windows 10 Print
Written by thyme   
Monday, 03 October 2016

Recently Windows Explorer has become unresponsive and freezing on Windows 10. This causes the Start Menu, Taskbar and Desktop to become unresponsive.

We are researching the root cause. In the meantime we have a few troubleshooting steps. 

Last Updated ( Friday, 21 October 2016 )
Read more...

©1999 - 2017 TheCAT