Difference: Automount (6 vs. 7)

Revision 72018-07-11 - WilliamSeligman

 			 META TOPICPARENT 
			 name="LinuxCluster" 
		
  Nevis Linux Cluster - Automount
- META TOPICPARENT
+ name="LinuxCluster"
  A practical example of automount
-<
<
+My home directory is /a/home/tanya/seligman. Thanks to NIS,
->
>
+My home directory is /nevis/tanya/home/seligman. Thanks to NIS,
 this is my home directory no matter which Linux box I'm logged
into. All of my various configuration files and scripts are available
in my ~seligman directory; for example, ~/.zshrc is
 When I get a chance to do physics, I might simulate the ATLAS
liquid-argon calorimeter using Geant4. My desktop Linux box is
tanya. The source code for all that work is in
-<
<
+/a/home/tanya/seligman/geant4 (or ~seligman/geant4,
->
>
+/nevis/tanya/home/seligman/geant4 (or ~seligman/geant4,
 or simply ~/geant4 for me).

The ATLAS workgroup server is kolya, so I store my compiled
binary files and libraries in
-<
<
+/a/home/kolya/seligman/g4work. That way, when my programs
->
>
+/nevis/kolya/home/seligman/g4work. That way, when my programs
 execute, their physical location is on the same computer that's
running the programs. I prefer to compile and execute my programs on
the server kolya, which is much faster than my desktop
 ssh kolya "at -f ~/geant4/calo/LArHits-0.5/cmd/electron.cmd now"

When I generate big ROOT Tree files or any other form of output, I can
-<
<
+store them in /a/data/kolya/seligman/LArHits, which has a lot of
->
>
+store them in /nevis/kolya/data/seligman/LArHits, which has a lot of
 available disk space.

Note that these directory names are the same on every system in the Linux cluster: my own desktop tanya, the server kolya, the student desktop workstation eeyore, etc. You have access to all of my work through the same directory names.

Obviously, I don't type in all these long names every time I want to change directories.  If you look at ~seligman/.myprofile, you'll see aliases that I've defined for these directory names.  For example:
-<
<
+setenv G4WORKDIR /a/home/kolya/seligman/g4work
setenv LArDataDir /a/data/kolya/seligman/LArHits
->
>
+setenv G4WORKDIR /nevis/kolya/home/seligman/g4work
setenv LArDataDir /nevis/kolya/data/seligman/LArHits
 However, all this fails if tanya goes down. Then
-<
<
+the /a/home/tanya directory would be inaccessible, and I'd
->
>
+the /nevis/tanya/home directory would be inaccessible, and I'd
 have problems logging onto other machines in the Linux cluster. As an
alternative, I could keep my home directory on the server (i.e.,
-<
<
+/a/home/kolya/seligman), since if the ATLAS server goes down
->
>
+//nevis/kolya/home/seligman), since if the ATLAS server goes down
 I couldn't do any analysis work anyway.

 Caveat

View topic | History: r7 < r6 < r5 < r4 | More topic actions...