BBSCP(1)           User Contributed Perl Documentation            BBSCP(1)

NAME
    bbscp - bbftp wrapper, provides an scp-like commandline interface

SYNOPSIS
    bbscp [OPTIONS] [[user@]host1:]file_or_dir1 [...] [[user@]host2:]dir2

DESCRIPTION
    bbscp copies files either from the localhost to a directory on a remote host, 
    or from a remote host to a directory on the localhost (see the -N option for 
    the only exception to this). It assembles the proper commandline for bbftp 
    (designed and tested for bbftp version 3.2.0, see RESTRICTIONS) and then 
    executes bbftp to perform the transfer(s). 

    The "-s", "-r 1", and "-p 8" options for bbftp are set by default, along with 
    the following options: 

         setoption keepaccess
         setoption keepmode
         setoption nocreatedir
         
    The option -p can be overridden on the command line.

    Note the following limitations and capabilities in different transfer 
    scenarios:

    copying from localhost to remote host

	  regular files               
		bbftp will overwrite a pre-existing file of the same name on the 
		remote host without asking for confirmation.  
         
	  directories               
		This script recursively transfers entire directories (only for 
		local-to-remote transfers!).           

	  symbolic links (see RESTRICTIONS)               
		Symlinks on the localhost are treated just like the thing they 
		point to, and are ignored if they point to something that 
		doesn't exist. 
      
	copying from remote host to localhost           

	  regular files               
		bbftp will overwrite a pre-existing file of the same name on the 
		localhost without asking for confirmation.           

	  directories               
		There is no way at this time to transfer entire directories from 
		a remote host to the localhost.           

	  symbolic links (see RESTRICTIONS)               
		Symlinks on the remote host are treated just like the thing they 
		point to (which means they are ignored if they point to a directory 
		or to something that doesn't exist).
		
OUTPUT
    The default output mode of the script displays "OK" or "FAILURE" for each of 
    the transfer operations that bbftp performs. This display occurs after bbftp 
    has finished running, so it may be delayed for some time depending on the 
    duration of the transfer(s).       

    The script switches to more verbose output if the user provides 1 or more of 
    the verbose output commandline options (-l, -t, -V, and -W).OPTIONS
    
OPTIONS
  -B    name/location of bbftp executable. default is "bbftp"

  -d    dry-run. script performs its duty but does not actually execute bbftp.
        the bbftp commandline is printed, along with the contents of the bbftp
        control-file

  -h    this help text

  -k    keep bbftp command file that this script creates

  -l    long-winded (extra verbose) output from bbftp. uses undocumented bbftp
        option (-d)

  -N    transfer a single file and rename it at the destination. both local-
        to-remote and remote-to-local transfer is supported

  -v    version of this script

  -X    set the size of the TCP send window (in kilobytes). default is the bbftp 
        default size

  -Y    set the size of the TCP receive window (in kilobytes). default is the
        bbftp default size
        
bbftp options that can be specified on the commandline of this script:

  -D[min_port:max_port]   (e.g. "-D", "-D40000:40100")

  -E <Server command to run>

  -L <SSH command>

  -p <number of parallel streams> 
        
  -R <bbftprc file>
  
RESTRICTIONS

    Version of bbftp           
	  It's very important to use bbftp version 3.2.0 with bbscp -- there's at 
	  least 1 known issue with using bbftp 3.1.0.       

    Wildcards           
	  If the -N option is not in use, wildcards can be used in remote host file 
	  specifications, but only for the names of files, not for 
	  directories. So, for example, "user@host:/tmp/file*" is acceptable, but 
	  "user@host:/tm*/file*" is not.       

    Symbolic links           
	  Symlinks are not bbftp's strong suit -- if you wish to transfer a 
	  collection of files that includes symlinks it is highly recommended that 
	  you first make a tar-file and then transfer the tar-file.       

    Use of -N option           
	  Wildcards are not supported in remote host file specifications w/-N.

	  If the destination is a symlink it will be overwritten, regardlessof 
	  what that symlink points to.
	  
EXAMPLES
    local file to remote directory (username must be the same on both machines)  

	  bbscp /u/gmatthew/data/file1 columbia4:target_dir       

    local file to remote file w/ different name           

	  bbscp -N /u/gmatthew/data/file1 columbia4:file89       

    multiple local files to remote directory           
	
	  bbscp /u/gmatthew/data/*file user@columbia4:/tmp       

    local directory to remote home directory           

	  bbscp /u/gmatthew/data user@columbia4:       

    remote file to local directory           

	  bbscp user@columbia4:data/file5 /u/gmatthew/source_dir       

    remote file to local file w/ different name           

	  bbscp -N user@columbia4:data/file5 /u/gmatthew/source_dir/file93       

    multiple remote files to local directory           

	  bbscp -V user@columbia4:/u/gmatthew/data/file* /tmp       

    multiple remote files to local directory           

	  bbscp -V user@columbia4:file1.txt user@columbia4:stuff.dat /tmp
	  
AUTHOR       
	Greg Matthews gmattew@nas.nasa.gov

perl v5.8.3                       2006-07-04                          BBSCP(1)