[pve-devel] applied: [PATCH container] pct: remove leftover outdated POD content
Wolfgang Bumiller
w.bumiller at proxmox.com
Wed Feb 15 11:13:35 CET 2017
applied
On Fri, Feb 10, 2017 at 08:53:54PM +0100, Thomas Lamprecht wrote:
> gets generated by pve-docs
>
> Signed-off-by: Thomas Lamprecht <t.lamprecht at proxmox.com>
> ---
> src/PVE/CLI/pct.pm | 62 ------------------------------------------------------
> 1 file changed, 62 deletions(-)
>
> diff --git a/src/PVE/CLI/pct.pm b/src/PVE/CLI/pct.pm
> index 4ffb8db..53d110c 100755
> --- a/src/PVE/CLI/pct.pm
> +++ b/src/PVE/CLI/pct.pm
> @@ -803,65 +803,3 @@ our $cmddef = {
>
>
> 1;
> -
> -__END__
> -
> -=head1 NAME
> -
> -pct - Tool to manage Linux Containers (LXC) on Proxmox VE
> -
> -=head1 SYNOPSIS
> -
> -=include synopsis
> -
> -=head1 DESCRIPTION
> -
> -pct is a tool to manages Linux Containers (LXC). You can create
> -and destroy containers, and control execution
> -(start/stop/suspend/resume). Besides that, you can use pct to set
> -parameters in the associated config file, like network configuration or
> -memory.
> -
> -=head1 EXAMPLES
> -
> -Create a container based on a Debian template
> -(provided you downloaded the template via the webgui before)
> -
> -pct create 100 /var/lib/vz/template/cache/debian-8.0-standard_8.0-1_amd64.tar.gz
> -
> -Start a container
> -
> -pct start 100
> -
> -Start a login session via getty
> -
> -pct console 100
> -
> -Enter the lxc namespace and run a shell as root user
> -
> -pct enter 100
> -
> -Display the configuration
> -
> -pct config 100
> -
> -Add a network interface called eth0, bridged to the host bridge vmbr0,
> -set the address and gateway, while it's running
> -
> -pct set 100 -net0 name=eth0,bridge=vmbr0,ip=192.168.15.147/24,gw=192.168.15.1
> -
> -Reduce the memory of the container to 512MB
> -
> -pct set -memory 512 100
> -
> -=head1 FILES
> -
> -/etc/pve/lxc/<vmid>.conf
> -
> -Configuration file for the container <vmid>
> -
> -=head1 SEE ALSO
> -
> -L<B<qm(1)>>, L<B<pvesh(1)>>
> -
> -=include pve_copyright
> --
> 2.1.4
More information about the pve-devel
mailing list