Man page or keyword search:   man All Sections 1 - General Commands 2 - System Calls 3 - Subroutines, Functions 4 - Special Files 5 - File Formats 6 - Games and Screensavers 7 - Macros and Conventions 8 - Maintenence Commands 9 - Kernel Interface New Commands Server 4.4BSD AIX Alpinelinux Archlinux Aros BSDOS BSDi Bifrost CentOS Cygwin Darwin Debian DigitalUNIX DragonFly ElementaryOS Fedora FreeBSD Gentoo GhostBSD HP-UX Haiku Hurd IRIX Inferno JazzOS Kali Knoppix LinuxMint MacOSX Mageia Mandriva Manjaro Minix MirBSD NeXTSTEP NetBSD OPENSTEP OSF1 OpenBSD OpenDarwin OpenIndiana OpenMandriva OpenServer OpenSuSE OpenVMS Oracle PC-BSD Peanut Pidora Plan9 QNX Raspbian RedHat Scientific Slackware SmartOS Solaris SuSE SunOS Syllable Tru64 UNIXv7 Ubuntu Ultrix UnixWare Xenix YellowDog aLinux   33470 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

LXC-STOP(1)							   LXC-STOP(1)

NAME
       lxc-stop - stop the application running inside a container

SYNOPSIS
       lxc-stop	 -n  name [ -W ]  [ -r ]  [ -t timeout ]  [ -k ]  [ --nokill ]
       [ --nolock ]

DESCRIPTION
       lxc-stop reboots, cleanly shuts down, or kills all the processes inside
       the container. By default, it will request a clean shutdown of the con‐
       tainer by sending lxc.haltsignal	 (defaults  to	SIGPWR)	 to  the  con‐
       tainer's	 init  process,	 waiting up to 60 seconds for the container to
       exit, and then returning. If the container fails to cleanly exit in  60
       seconds,	 it  will  be sent the lxc.stopsignal (defaults to SIGKILL) to
       force it to shut down.

       The [-W], [-r], [-k] and [--nokill] options specify the action to  per‐
       form.   [-W] indicates that after performing the specified action, lxc-
       stop should immediately exit, while [-t TIMEOUT] specifies the  maximum
       amount  of  time	 to wait for the container to complete the shutdown or
       reboot.

OPTIONS
       -r,--reboot
	      Request a reboot of the container.

       -k,--kill
	      Rather than  requesting  a  clean	 shutdown  of  the  container,
	      explicitly  kill	all tasks in the container. This is the legacy
	      lxc-stop behavior.

       --nokill
	      Only request a clean shutdown, do not kill the  container	 tasks
	      if the clean shutdown fails.

       --nolock
	      This  option  avoids  the use of any of the API lxc locking, and
	      should only be used if lxc-stop is hanging due to a  bad	system
	      state.

       -W,--nowait
	      Simply  perform the requestion action (reboot, shutdown, or hard
	      kill) and exit.

       -t,--timeout TIMEOUT
	      Wait TIMEOUT seconds before hard-stopping the container.

EXIT VALUE
       0      The container was successfully stopped.

       1      An error occurred while stopping the container.

       2      The specified container exists but was not running.

DIAGNOSTIC
       The container was not found
	      The specified container was not created before with the lxc-cre‐
	      ate command.

SEE ALSO
       lxc(7),	lxc-create(1), lxc-destroy(1), lxc-start(1), lxc-stop(1), lxc-
       execute(1), lxc-console(1), lxc-monitor(1), lxc-wait(1), lxc-cgroup(1),
       lxc-ls(1),  lxc-info(1), lxc-freeze(1), lxc-unfreeze(1), lxc-attach(1),
       lxc.conf(5)

AUTHOR
       Daniel Lezcano <daniel.lezcano@free.fr>

			  Thu Jul 3 13:01:56 PDT 2014		   LXC-STOP(1)

Vote for polarhome