From mboxrd@z Thu Jan 1 00:00:00 1970 From: Xpl++ Subject: Re: [RFC] Prefixing cgroup generic control filenames with "cgroup." Date: Fri, 29 Feb 2008 13:38:20 +0200 Message-ID: <47C7EEAC.7010907@amln.net> References: <6599ad830802281314s25c033d6tc021725ae28aef8d@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <6599ad830802281314s25c033d6tc021725ae28aef8d-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: Paul Menage Cc: Peter Zijlstra , LKML , Linux Containers , Andrew Morton , Balbir Singh , Pavel Emelianov List-Id: containers.vger.kernel.org Paul Menage ??????: > ... > > A compromise might be to keep "tasks" unprefixed, and say that future > names get the "cgroup." prefix; in this case I'd be inclined to add > the prefix to notify_on_release and release_agent on the grounds that > there's much less chance of breaking anyone with those files since (I > suspect) they're much less used. > This makes most sense to me. It won't break any existing software (most likely) while it seems reasonable to leave 'tasks' unprefixed as this is something that any software using any subsystem of cgroup would be using anyway and it is not that much associated with a particulat subsystem. Regards, Peter Litov.