AT(1)									      General Commands Manual									     AT(1)



NAME
       at, batch, atq, atrm - queue, examine or delete jobs for later execution

SYNOPSIS
       at [-V] [-q queue] [-f file] [-mMlv] timespec...
       at [-V] [-q queue] [-f file] [-mMkv] [-t time]
       at -c job [job...]
       atq [-V] [-q queue] [-o timeformat]
       at [-rd] job [job...]
       atrm [-V] job [job...]
       batch
       at -b

DESCRIPTION
       at and batch read commands from standard input or a specified file which are to be executed at a later time, using /bin/sh.

       at      executes commands at a specified time.

       atq     lists  the user's pending jobs, unless the user is the superuser; in that case, everybody's jobs are listed.  The format of the output lines (one for each job) is:
	       Job number, date, hour, queue, and username.

       atrm    deletes jobs, identified by their job number.

       batch   executes commands when system load levels permit; in other words, when the load average drops below 0.8, or the value specified in the invocation of atd.

       At allows fairly complex time specifications, extending the POSIX.2 standard.  It accepts times of the form HH:MM to run a job at a specific time of day.  (If that time is
       already	past,  the  next  day is assumed.)  You may also specify midnight, noon, or teatime (4pm) and you can have a time-of-day suffixed with AM or PM for running in the
       morning or the evening.	You can also say what day the job will be run, by giving a date in the form month-name day with an optional year, or giving a  date  of	 the  form
       MMDD[CC]YY,  MM/DD/[CC]YY, DD.MM.[CC]YY or [CC]YY-MM-DD.	 The specification of a date must follow the specification of the time of day.	You can also give times like now +
       count time-units, where the time-units can be minutes, hours, days, or weeks and you can tell at to run the job today by suffixing the time with today and to run  the  job
       tomorrow by suffixing the time with tomorrow.

       For example, to run a job at 4pm three days from now, you would do at 4pm + 3 days, to run a job at 10:00am on July 31, you would do at 10am Jul 31 and to run a job at 1am
       tomorrow, you would do at 1am tomorrow.

       The definition of the time specification can be found in /usr/share/doc/packages/at/timespec.

       For both at and batch, commands are read from standard input or the file specified with the -f option and executed.  The working directory, the environment (except for the
       variables BASH_VERSINFO, DISPLAY, EUID, GROUPS, SHELLOPTS, TERM, UID, and _) and the umask are retained from the time of invocation.

       As  at  is  currently  implemented  as  a  setuid program, other environment variables (e.g.  LD_LIBRARY_PATH or LD_PRELOAD) are also not exported.  This may change in the
       future.	As a workaround, set these variables explicitly in your job.

       An at - or batch - command invoked from a su(1) shell will retain the current userid.  The user will be mailed standard error and standard output  from	his  commands,	if
       any.  Mail will be sent using the command /usr/sbin/sendmail.  If at is executed from a su(1) shell, the owner of the login shell will receive the mail.

       The  superuser  may  use these commands in any case.  For other users, permission to use at is determined by the files /etc/at.allow and /etc/at.deny.  See at.allow(5) for
       details.

OPTIONS
       -V      prints the version number to standard error and exit successfully.

       -q queue
	       uses the specified queue.  A queue designation consists of a single letter; valid queue designations range from a to z and A to Z.  The a queue is the default  for
	       at and the b queue for batch.  Queues with higher letters run with increased niceness.  The special queue "=" is reserved for jobs which are currently running.

       If  a  job  is  submitted  to  a	 queue	designated with an uppercase letter, the job is treated as if it were submitted to batch at the time of the job.  Once the time is
       reached, the batch processing rules with respect to load average apply.	If atq is given a specific queue, it will only show jobs pending in that queue.

       -m      Send mail to the user when the job has completed even if there was no output.

       -M      Never send mail to the user.

       -f file Reads the job from file rather than standard input.

       -t time run the job at time, given in the format [[CC]YY]MMDDhhmm[.ss]

       -l      Is an alias for atq.

       -r      Is an alias for atrm.

       -d      Is an alias for atrm.

       -b      is an alias for batch.

       -v      Shows the time the job will be executed before reading the job.

       Times displayed will be in the format "Thu Feb 20 14:50:00 1997".

       -c     cats the jobs listed on the command line to standard output.

       -o fmt  strftime-like time format used for the job list

FILES
       /var/spool/atjobs
       /var/spool/atspool
       /proc/loadavg
       /var/run/utmp
       /etc/at.allow
       /etc/at.deny

SEE ALSO
       at.allow(5), at.deny(5), atd(8), cron(1), nice(1), sh(1), umask(2).

BUGS
       The correct operation of batch for Linux depends on the presence of a proc- type directory mounted on /proc.

       If the file /var/run/utmp is not available or corrupted, or if the user is not logged on at the time at is invoked, the mail is sent to the userid found in the environment
       variable LOGNAME.  If that is undefined or empty, the current userid is assumed.

       At and batch as presently implemented are not suitable when users are competing for resources.  If this is the case for your site, you might want to consider another batch
       system, such as nqs.

AUTHOR
       At was mostly written by Thomas Koenig, ig25@rz.uni-karlsruhe.de.



										    2009-11-14										     AT(1)
SCP(1)									    BSD General Commands Manual									    SCP(1)

NAME
     scp — secure copy (remote file copy program)

SYNOPSIS
     scp [-12346BCpqrv] [-c cipher] [-F ssh_config] [-i identity_file] [-l limit] [-o ssh_option] [-P port] [-S program] [[user@]host1:]file1 ... [[user@]host2:]file2

DESCRIPTION
     scp copies files between hosts on a network.  It uses ssh(1) for data transfer, and uses the same authentication and provides the same security as ssh(1).	 Unlike rcp(1),
     scp will ask for passwords or passphrases if they are needed for authentication.

     File names may contain a user and host specification to indicate that the file is to be copied to/from that host.	Local file names can be made explicit using absolute or
     relative pathnames to avoid scp treating file names containing ‘:’ as host specifiers.  Copies between two remote hosts are also permitted.

     The options are as follows:

     -1	     Forces scp to use protocol 1.

     -2	     Forces scp to use protocol 2.

     -3	     Copies between two remote hosts are transferred through the local host.  Without this option the data is copied directly between the two remote hosts.  Note that
	     this option disables the progress meter.

     -4	     Forces scp to use IPv4 addresses only.

     -6	     Forces scp to use IPv6 addresses only.

     -B	     Selects batch mode (prevents asking for passwords or passphrases).

     -C	     Compression enable.  Passes the -C flag to ssh(1) to enable compression.

     -c cipher
	     Selects the cipher to use for encrypting the data transfer.  This option is directly passed to ssh(1).

     -F ssh_config
	     Specifies an alternative per-user configuration file for ssh.  This option is directly passed to ssh(1).

     -i identity_file
	     Selects the file from which the identity (private key) for public key authentication is read.  This option is directly passed to ssh(1).

     -l limit
	     Limits the used bandwidth, specified in Kbit/s.

     -o ssh_option
	     Can be used to pass options to ssh in the format used in ssh_config(5).  This is useful for specifying options for which there is no separate scp command-line flag.
	     For full details of the options listed below, and their possible values, see ssh_config(5).

		   AddressFamily
		   BatchMode
		   BindAddress
		   ChallengeResponseAuthentication
		   CheckHostIP
		   Cipher
		   Ciphers
		   Compression
		   CompressionLevel
		   ConnectionAttempts
		   ConnectTimeout
		   ControlMaster
		   ControlPath
		   ControlPersist
		   GlobalKnownHostsFile
		   GSSAPIAuthentication
		   GSSAPIDelegateCredentials
		   HashKnownHosts
		   Host
		   HostbasedAuthentication
		   HostKeyAlgorithms
		   HostKeyAlias
		   HostName
		   IdentityFile
		   IdentitiesOnly
		   IPQoS
		   KbdInteractiveAuthentication
		   KbdInteractiveDevices
		   KexAlgorithms
		   LogLevel
		   MACs
		   NoHostAuthenticationForLocalhost
		   NumberOfPasswordPrompts
		   PasswordAuthentication
		   PKCS11Provider
		   Port
		   PreferredAuthentications
		   Protocol
		   ProxyCommand
		   PubkeyAuthentication
		   RekeyLimit
		   RhostsRSAAuthentication
		   RSAAuthentication
		   SendEnv
		   ServerAliveInterval
		   ServerAliveCountMax
		   StrictHostKeyChecking
		   TCPKeepAlive
		   UsePrivilegedPort
		   User
		   UserKnownHostsFile
		   VerifyHostKeyDNS

     -P port
	     Specifies the port to connect to on the remote host.  Note that this option is written with a capital ‘P’, because -p is already reserved for preserving the times
	     and modes of the file in rcp(1).

     -p	     Preserves modification times, access times, and modes from the original file.

     -q	     Quiet mode: disables the progress meter as well as warning and diagnostic messages from ssh(1).

     -r	     Recursively copy entire directories.  Note that scp follows symbolic links encountered in the tree traversal.

     -S program
	     Name of program to use for the encrypted connection.  The program must understand ssh(1) options.

     -v	     Verbose mode.  Causes scp and ssh(1) to print debugging messages about their progress.  This is helpful in debugging connection, authentication, and configuration
	     problems.

EXIT STATUS
     The scp utility exits 0 on success, and >0 if an error occurs.

SEE ALSO
     rcp(1), sftp(1), ssh(1), ssh-add(1), ssh-agent(1), ssh-keygen(1), ssh_config(5), sshd(8)

HISTORY
     scp is based on the rcp(1) program in BSD source code from the Regents of the University of California.

AUTHORS
     Timo Rinne 
     Tatu Ylonen 

BSD										   May 19, 2015										       BSD