From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932790AbbCDPx6 (ORCPT ); Wed, 4 Mar 2015 10:53:58 -0500 Received: from mail.bgservers.net ([85.14.7.126]:56503 "EHLO BlackPearl.yuhu.biz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752677AbbCDPx5 (ORCPT ); Wed, 4 Mar 2015 10:53:57 -0500 Message-ID: <54F72A8D.1070402@yuhu.biz> Date: Wed, 04 Mar 2015 17:53:49 +0200 From: Marian Marinov User-Agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Stephan Mueller CC: "linux-kernel@vger.kernel.org" Subject: Re: RFC: sysctl fixes References: <54F7061B.80002@yuhu.biz> <2702382.luOtcDVGpO@tauon> In-Reply-To: <2702382.luOtcDVGpO@tauon> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 03/04/2015 05:48 PM, Stephan Mueller wrote: > Am Mittwoch, 4. März 2015, 15:18:19 schrieb Marian Marinov: > > Hi Marian, > >> Hello, >> we are running hundreds of containers and we got some valid requests > >from customers that want to be able to change their container's >> hostname using the sysctl command. >> >> The current implementation does not allow each UTS namespace to change >> its own hostname. >> >> So we sponsored the development of fix for this issue. >> >> Please checkout the changes here: >> >> https://github.com/1HLtd/linux/compare/b24e2bdde4af656bb0679a101265ebb >> 8f8735d3c...sysctl-hostname-fixes >> >> If this fix is acceptable I'll send the patches as it is common. But >> first I want to know if you think this is the way to go. > The description in http://lwn.net/Articles/531381/ does not work? Stephan, the users can change the hostname of the container using the hostname command. I can also change their hostname when I'm creating the containers. However the customers need to be able to change the hostname of the machine using valid system command: sysctl kernel.hostname=newhost sysctl kernel.domainname=newdomain Both of these commands try to talk to the kernel via the /proc filesystem. This is why we propose these fixes. Without them, only the root on the host node can do this. Correct me, if I'm wrong. Marian >> Thank you, >> Marian >> >> -- >> To unsubscribe from this list: send the line "unsubscribe linux-kernel" >> in the body of a message to majordomo@vger.kernel.org >> More majordomo info at http://vger.kernel.org/majordomo-info.html >> Please read the FAQ at http://www.tux.org/lkml/ > > Ciao > Stephan > >