From 04d39279245834494baccfdb9349db8bf80abd13 Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Thu, 31 Oct 2013 01:25:44 +0100 Subject: machinectl: add new command to spawn a getty inside a container --- man/machinectl.xml | 13 +++++++++++++ man/systemd-nspawn.xml | 30 ++++++------------------------ 2 files changed, 19 insertions(+), 24 deletions(-) (limited to 'man') diff --git a/man/machinectl.xml b/man/machinectl.xml index f2fa6ce53e..c06d0c7abb 100644 --- a/man/machinectl.xml +++ b/man/machinectl.xml @@ -263,6 +263,19 @@ to select the signal to send. + + + login [ID] + + Open a terminal login + session to a container. This will + create a TTY connection to a specific + container and asks for execution of a + getty on it. Note that this is only + supported for containers running + systemd1 + as init system. + diff --git a/man/systemd-nspawn.xml b/man/systemd-nspawn.xml index 7d450f912c..c2be6d5446 100644 --- a/man/systemd-nspawn.xml +++ b/man/systemd-nspawn.xml @@ -123,10 +123,10 @@ see each other. The PID namespace separation of the two containers is complete and the containers will share very few runtime objects except for the - underlying file system. It is however possible to - enter an existing container, see - Example 4 below. - + underlying file system. Use + machinectl1's + login command to request an + additional login prompt in a running container. systemd-nspawn implements the - - Example 4 - - To enter the container, PID of one of the - processes sharing the new namespaces must be used. - systemd-nspawn prints the PID - (as viewed from the outside) of the launched process, - and it can be used to enter the container. - - # nsenter -m -u -i -n -p -t $PID - - nsenter1 - is part of - util-linux. - Kernel support for entering namespaces was added in - Linux 3.8. - - Exit status @@ -439,11 +421,11 @@ systemd1, chroot1, - unshare1, yum8, debootstrap8, pacman8, - systemd.slice5 + systemd.slice5, + machinectl1 -- cgit v1.2.3-54-g00ecf