From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2012-December/020954.html | 123 +++++++++++++++++++++++++++ 1 file changed, 123 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-December/020954.html (limited to 'zarb-ml/mageia-dev/2012-December/020954.html') diff --git a/zarb-ml/mageia-dev/2012-December/020954.html b/zarb-ml/mageia-dev/2012-December/020954.html new file mode 100644 index 000000000..2df9d4961 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-December/020954.html @@ -0,0 +1,123 @@ + + + + [Mageia-dev] starting openssh inside a chroot, as per mageia wiki + + + + + + + + + +

[Mageia-dev] starting openssh inside a chroot, as per mageia wiki

+ Guillaume Rousse + guillomovitch at gmail.com +
+ Thu Dec 27 11:55:09 CET 2012 +

+
+ +
Le 27/12/2012 11:29, Pascal Terjan a écrit :
+>> It seems like the systemd way of starting would be:
+>> systemctl start openssh.service
+>>
+>> But, then produces an error:
+>>
+>> [root at localhost /]# systemctl start openssh.service
+>> Running in chroot, ignoring request.
+>>
+>>
+>> So,  Any thoughts on what is the recommended way, and I'll be happy to
+>> update the wiki to reflect this.
+>
+> Last time I tried, I gave up after various attempts and now went back
+> to the basics: running "sshd" and killing it to stop it.
+> Maybe I'll fetch some old initscript.
+I guess using a specific unit file, using builtin systemd chroot 
+support, should help. See 
+http://0pointer.de/blog/projects/changing-roots for details.
+
+-- 
+BOFH excuse #346:
+
+Your/our computer(s) had suffered a memory leak, and we are waiting for 
+them to be topped up.
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1