Difference: Automount (6 vs. 7)

Revision 72018-07-11 - WilliamSeligman

Line: 1 to 1
 
META TOPICPARENT name="LinuxCluster"

Nevis Linux Cluster - Automount

Line: 105 to 105
 

A practical example of automount

Changed:
<
<
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
Line: 114 to 114
 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
Changed:
<
<
/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

Changed:
<
<
/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
Line: 129 to 129
 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
Changed:
<
<
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:


Changed:
<
<
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

Changed:
<
<
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.,
Changed:
<
<
/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

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback