1. 20 Oct, 2006 1 commit
    • Mike Hibler's avatar
      Wow, this should make me look important! · afa5e919
      Mike Hibler authored
      Two-day boondoggle to support "/scratch", an optional large, shared filesystem
      for users.  To do this, I needed to find all the instances where /proj is used
      and behave accordingly.  The boondoggle part was the decision to gather up all
      the hardwired instances of shared directory names ("/proj", "/users", etc.)
      so that they are set in a common place (via unexposed configure variables).
      This is a boondoggle because:
      
      1. I didn't change the client-side scripts.  They need a different mechanism
         (e.g., tmcd) to get the info, configure is the wrong way.
      
      2. Even if I had done #1 it is likely--no, certain--that something would
         fail if you tried to rename "/proj" to be "/mike".  These names are just
         too ingrained.
      
      3. We may not even use "/scratch" as it turns out.
      
      Note, I also didn't fix any of the .html documentation.  Anyway, it is done.
      To maintain my illusion in the future you should:
      
      1. Have perl scripts include "use libtestbed" and use the defined PROJROOT(),
         et.al. functions where possible.  If not possible, make sure they run
         through configure and use @PROJROOT_DIR@, etc.
      
      2. Use the configure method for python, C, php and other languages.
      
      3. There are perl (TBValidUserDir) and php (VALIDUSERPATH) functions which
         you should call to determine if an NS, template parameter, tarball or
         other file are in "an acceptable location."  Use these functions where
         possible.  They know about the optional "scratch" filesystem.  Note that
         the perl function is over-engineered to handles cases that don't occur
         in nature.
      afa5e919
  2. 12 Feb, 2005 1 commit
    • Kirk Webb's avatar
      · dede658b
      Kirk Webb authored
      Fixed up ops-install for new way of handling smb.conf file.  We copy in an
      smb.conf.head file now, and copy that to smb.conf initially on ops.
      exports_setup[.proxy] takes care of updating the share permissions for
      samba dynamically.
      dede658b
  3. 11 Feb, 2005 1 commit
    • Kirk Webb's avatar
      · 51472343
      Kirk Webb authored
      Removed some unneeded shares now that we autogen them.
      51472343
  4. 25 Jan, 2005 1 commit
    • Kirk Webb's avatar
      · 2023c936
      Kirk Webb authored
      Add a Samba template config file.  The listening interface, globally allowed
      access list, and workgroup are defined as follows:
      
         workgroup = @OURDOMAIN@
         hosts allow = @CONTROL_NETWORK@/@CONTROL_NETMASK@
         interfaces = @FSNODE_IP@
      
      I believe this is what we want, but am not sure about the workgroup setting.
      Note that this should ultimately just be the head of the smb.conf file, with
      the tail generated vis-a-vis /etc/exports .  For now it has some hard wired
      shares for /proj and /users, which is OK for the very short term on an
      inner elab.
      2023c936