From: Marian Marinov <mm-l@yuhu.biz>
To: Stephan Mueller <smueller@chronox.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: RFC: sysctl fixes
Date: Wed, 04 Mar 2015 17:53:49 +0200 [thread overview]
Message-ID: <54F72A8D.1070402@yuhu.biz> (raw)
In-Reply-To: <2702382.luOtcDVGpO@tauon>
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
>
>
next prev parent reply other threads:[~2015-03-04 15:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-04 13:18 RFC: sysctl fixes Marian Marinov
2015-03-04 15:48 ` Stephan Mueller
2015-03-04 15:53 ` Marian Marinov [this message]
[not found] ` <54F7061B.80002-NV7Lj0SOnH0@public.gmane.org>
2015-03-05 14:43 ` Marian Marinov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54F72A8D.1070402@yuhu.biz \
--to=mm-l@yuhu.biz \
--cc=linux-kernel@vger.kernel.org \
--cc=smueller@chronox.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.