check-sendfile(1) [debian man page]

CHECK-SENDFILE(1)						     Commands							 CHECK-SENDFILE(1)

NAME

       check-sendfile - Check if some files have arrived

SYNOPSIS

       check-sendfile

DESCRIPTION

       The check-sendfile command tests if there are files hosed in the user's sendfile spool area.  If so he will be informed about the files.

       This  command  should be started from /etc/profile to give all users a chance to notices that some files have arrived in their absence.	As
       the defauld behaviour of sendfiled is to write a note on the user's tty he won't notice receiption if he's not logged in.  The lack of need
       to be logged in is one of sendfile's advantages.

FILES

       /var/spool/sendfile/$user
	      Spool area for the specifig user.

SEE ALSO

       sendfile(1).

Debian GNU/Linux						    11 Feb 1998 						 CHECK-SENDFILE(1)

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)