A page in your DokuWiki was added or changed. Here are the details:

Date        : 2017/01/09 17:36
Browser     : Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 
Firefox/45.0
IP-Address  : 78.43.90.159
Hostname    : HSI-KBW-078-043-090-159.hsi4.kabel-badenwuerttemberg.de
Old Revision: ---
New Revision: 
http://wiki.x2go.org/doku.php/doc:deployment-stories:x2go-at-university-of-california-irvine
Edit Summary: created
User        : stefanbaur

====== X2Go at the University of California, Irvine ======


I'm one of the Research Computing domain specialists at the University of 
California, Irvine.  We provide >1000 applications (pre- and self-compiled) for 
our ~1500 cluster users.  Most are commandline but we have a large minority that 
use graphics (MATLAB, Mathematica, ANSYS, SAS, STATA, CLCBio, etc) and for these 
we use X2Go, not only because it is Open Source, but because we have repeatedly 
compared it to commercial packages and found that either they are much harder to
configure for our users, or they lack features that some of our users like 
(mostly shared folders), or their performance is either no better or 
considerably worse than X2Go.

We teach the use of it in our 
[[http://moo.nac.uci.edu/~hjm/biolinux/Linux_Tutorial_12.html|Linux on HPC]] 
tutorial to allow the use of specific GUI apps (esp editors and file transfer 
tools) and **highly** recommend it as a multiplatform access tool.

I also use it as a remote sysadmin tool (especially with 
[[doc:installation:pyhoca-gui|PyHoca]]) to debug user access problems or to 
keep long-running GUI processes alive to monitor periodically (our BeeGFS 
filesystem monitor, the hated MegaRAID processes, etc).

I'd be happy to answer specific questions about how we use it as well.


- [[harry.manga...@uci.edu|Harry Mangalam]], PhD

UC Irvine

--
This mail was generated by DokuWiki at
http://wiki.x2go.org/

_______________________________________________
x2go-commits mailing list
x2go-commits@lists.x2go.org
http://lists.x2go.org/listinfo/x2go-commits

Reply via email to