Visit Our UNIX and Linux User Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #344
Difficulty: Medium
In February 2005, Sun announced the Sun Grid, a grid computing deployment on which it offered utility computing services priced at US$2 per CPU/hour for processing and per GB/month for storage.
True or False?
Linux & Unix Commands - Search Man Pages

fetchfile(1) [bsd man page]

SENDFILE(1)						      General Commands Manual						       SENDFILE(1)

NAME
fetchfile - fetch file(s) via O-SAFT protocol SYNOPSIS
fetchfile [ -46lakdPriqQvVI ] [ -f user ] [ -s [user@]server ] [ -C[wr]=conffile ] filename fetchfile [ -lakdPriqQvVI ] [ -f user ] [ -s [user@]server ] [ -C[wr]=conffile ] -n filenumber DESCRIPTION
fetchfile fetches files from a SAFT server to the local user spool. In the SAFT server spool there must lay your sendfile public key to identify yourself. This key can be generated by the fetchfile -I com- mand and has to be transfered to the SAFT server at the very first time. This prevents other people to steal your files. You may list or fetch your files from the server. But remember, they are stored first in your local sendfile spool. You have to call receive to really receive them to your current directory. OPTIONS
-4, -6 Explicitly force IPv4 or IPv6 connections. By default, the program will try to resolve the name given, and choose the appropriate protocol automatically. If resolving a host name returns both IPv4 and IPv6 addresses, fetchfile will try to use the adresses in the order they are returned by the resolver. -l Only list the files on the server. -a Fetch all files. -k Keep files on server after fetching. -d Delete files without receiving. -n Specify the file number instead of the file name. -r Call receive automaticly afterwards. -f user Restrict file selection to this specifc user. -V Show version information and exit. -v Be verbose and show SAFT protocol messages. -P Send files to stdout directly. -i Ignore testing whether file has been already fetched. -q Quiet mode 1: print no transfer messages. -Q Quiet mode 2: print no transfer, information or warning messages. -I Initialize fetchfile and the pgp key pair. -s [user@]host Specify an alternate saft server and/or alternate user. -Cr=conffile Read configuration file "config" or "restrictions" from server. -Cw=conffile Write configuration file "config" or "restrictions" to server. ARGUMENTS
filename or filenumber Specify the name of the file or its number (with option -n). EXAMPLES
fetchfile -l fetchfile -a fetchfile -Cr=config -s saft.belwue.de FILES
/var/spool/sendfile/$USER/ Your local spool directory. $HOME/.sfspool/ Your local private spool directory if /var/spool/sendfile/$USER/ does not exist. config, restrictions Your configuration files for the server. See sendfile(1) for a description. SEE ALSO
receive(1), sendfile(1), fetchfile(7), sendfiled(8). AUTHOR
Ulli Horlacher - framstag@rus.uni-stuttgart.de 3rd Berkeley Distribution SENDFILE(1)

Check Out this Related Man Page

SENDFILE(1)						      General Commands Manual						       SENDFILE(1)

NAME
fetchfile - fetch file(s) via O-SAFT protocol SYNOPSIS
fetchfile [ -46lakdPriqQvVI ] [ -f user ] [ -s [user@]server ] [ -C[wr]=conffile ] filename fetchfile [ -lakdPriqQvVI ] [ -f user ] [ -s [user@]server ] [ -C[wr]=conffile ] -n filenumber DESCRIPTION
fetchfile fetches files from a SAFT server to the local user spool. In the SAFT server spool there must lay your sendfile public key to identify yourself. This key can be generated by the fetchfile -I com- mand and has to be transfered to the SAFT server at the very first time. This prevents other people to steal your files. You may list or fetch your files from the server. But remember, they are stored first in your local sendfile spool. You have to call receive to really receive them to your current directory. OPTIONS
-4, -6 Explicitly force IPv4 or IPv6 connections. By default, the program will try to resolve the name given, and choose the appropriate protocol automatically. If resolving a host name returns both IPv4 and IPv6 addresses, fetchfile will try to use the adresses in the order they are returned by the resolver. -l Only list the files on the server. -a Fetch all files. -k Keep files on server after fetching. -d Delete files without receiving. -n Specify the file number instead of the file name. -r Call receive automaticly afterwards. -f user Restrict file selection to this specifc user. -V Show version information and exit. -v Be verbose and show SAFT protocol messages. -P Send files to stdout directly. -i Ignore testing whether file has been already fetched. -q Quiet mode 1: print no transfer messages. -Q Quiet mode 2: print no transfer, information or warning messages. -I Initialize fetchfile and the pgp key pair. -s [user@]host Specify an alternate saft server and/or alternate user. -Cr=conffile Read configuration file "config" or "restrictions" from server. -Cw=conffile Write configuration file "config" or "restrictions" to server. ARGUMENTS
filename or filenumber Specify the name of the file or its number (with option -n). EXAMPLES
fetchfile -l fetchfile -a fetchfile -Cr=config -s saft.belwue.de FILES
/var/spool/sendfile/$USER/ Your local spool directory. $HOME/.sfspool/ Your local private spool directory if /var/spool/sendfile/$USER/ does not exist. config, restrictions Your configuration files for the server. See sendfile(1) for a description. SEE ALSO
receive(1), sendfile(1), fetchfile(7), sendfiled(8). AUTHOR
Ulli Horlacher - framstag@rus.uni-stuttgart.de 3rd Berkeley Distribution SENDFILE(1)

Featured Tech Videos