* KAMEZAWA Hiroyuki <kamezawa.hiroyu@xxxxxxxxxxxxxx> [2009-02-25 16:35:55]: > From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@xxxxxxxxxxxxxx> > > cgroup's subsys has "readonly" files, but default permission is always > rw-r--r--. This allows to create r--r--r-- file to subsys. > (The user can do chmod on this read-only file. But this behavior is not > different from current pseudo file systems as /proc.) > > Reason: > When I wrote tools for maintain cgroup, I can't find which file is > writable intarfece or not via cgroup file systems. (finally, I did > dirty approach.) > IMHO, showing "this file is read-only" in explicit way is useful > for user-land (tools). In other story, a file whose name sounds read-only > may have "trigger" operation and support reseting. In this case, > "writable" is informative. Perfect, Thanks, Looks good to me -- Balbir _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
