recentpopularlog in

kme : osc   20

NFSv4 ACLs | Department of Electrical Engineering & Computer Science
This is very important: once you have created your ACL with inherited access controls, you must then set the group field of your umask(2) to something permissive enough to allow any extra principals in your inherited list (other than the OWNER@, GROUP@, and EVERYONE@) to have the access you would like. Take a moment to let that sink in. For example, if you have an ACE like on a directory, then you need to set your umask to at most 007 (e.g. with a command like “umask 007”). If instead you only gave joeuser the RX permissions, you could set your umask to 027. No, it does not make any sense, and yes it is a bug, but it is not likely to be fixed soon.

Example: Give your research group, research1, read access to your project directory project1:

$ find project1 -type d -exec nfs4_setfacl -a "" {} \;$ find project1 -type f -exec nfs4_setfacl -a "" {} \;
filesystem  permissions  nfs4  acl  nfs4_setfacl  sysadmin  osc  solution  fuckina 
april 2017 by kme
linux - How can OpenGL graphics be displayed remotely using VNC? - Server Fault
On the OSC cluster nodes, this is a sure sign that you forgot to run your CUDA application with 'vglrun'.
x11  vnc  remotedesktop  opengl  errormessage  osc 
september 2016 by kme
CUDA | Ohio Supercomputer Center -
qsub -I -l nodes=1:ppn=1:gpus=1 -l walltime=00:20:00
cuda  hpc  osc  reference  devel 
august 2015 by kme

Copy this bookmark:

to read