Anonymous FTP on the central UNIX system at SLAC permits SLAC users and non-SLAC collaborators to exchange files easily. Authorized SLAC UNIX users can store files in FTP space so that collaborators without a SLAC UNIX account may retrieve them. Similarly, file space exists where collaborators without a SLAC UNIX account may store files for SLAC users.
The rest of the page gives the procedures for two tasks:
Note: The following discussion assumes familiarity with the UNIX ftp command. Give the UNIX command man ftp for more information about the ftp command.
Note: If needed, you can add additional subdirectories under the subdirectory created by unix-admin. You will have all AFS file access privileges, except administrator privileges, for any subdirectories you choose to create. See the AFS Users' Guide for more information.
The SLAC person has notified the collaborator of the subdirectory and filename, and the collaborator now wants to transfer the file. For example, collaborator Ann wants to transfer the file calibration.dat from her SLAC colleague Bill. Assuming Bill has placed the file in users/bill, Ann can login to SLAC's FTP site to retrieve the file with the following commands (shown in bold):
ftp ftp.slac.stanford.edu
Name: anonymous
Password: ann@hep.physics.edu (the password will not display on screen)
(At this point you are in the directory '/afs/slac/public' although pwd returns '/'.)
cd users/bill
binary (assuming that the data format is binary; the default is ascii)
get calibration.dat (mget if it were a group of files)
quit
Of course, if the collaborator has access to AFS at SLAC, instead of using anonymous FTP, he or she may simply cd
to /afs/slac.stanford.edu/public/users, /afs/slac.stanford.edu/public/groups,
or /afs/slac.stanford.edu/public/software
and copy in the file.
The subdirectory incoming has been reserved for collaborators who want to send files to SLAC users. For example, assume that Ann wants to transfer the file cheptalk.ps to SLAC user Bill.
WARNING: Files are automatically expired from the incoming directory after three days. If Bill does not retrieve the file within that time it will be deleted. |
Note: The collaborator can verify that the file(s) has been properly transferred by giving the ls or dir command.
Alternatively, if the sender has access to AFS, he or she may simply cd
to /afs/slac.stanford.edu/public/incoming/bill
and copy the file.
Bill removes the file with the commands:
Note: Please make sure that files are removed from subdirectory incoming; that's why we suggest you use the mv rather than cp command.
* Although it is possible to write files into incoming directly, OCIO highly recommends that a subdirectory be created to identify who the files are intended for.
Imported form web page, 2020 April 03.