- From: Chad Woolley <
>
- To: Thomas Bishop <
>
- Cc:
- Subject: [[chef-dev]] Re: [[chef-dev]] CHEF-1621 - "recursive" attribute on "directory" resource does not apply users and groups to entire path
- Date: Sun, 3 Oct 2010 17:42:30 -0700
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=XSuoaSsOTyznii/CNYWrqEN+EbDwmzHvDX074ZWutw0Z5KgXAd2OurYBznSrU8eW/1 kQHycOz9iIqhTTKeFPUufPSBwFvq8MtCw6STgbHdPFEccWXUdSf6W7VbiF1LaDqc4Msk 682jhFrrBb5qxaSFskNziP+C/7D/RlzJE8j58=
On Sun, Oct 3, 2010 at 5:08 PM, Thomas Bishop
<
>
wrote:
>
1. I'm probably influenced by how I would do this on the command
>
line. (mkdir -p /data/realtime/fetched/radar; chmod -R 777 /data;
>
chown -R ldm:ldm /data;)
On the command line, if I wanted an entire tree owned by a non-root
user, I would do this:
mkdir -p /home/ldm/realtime/fetched/radar
IF the top level dir happened to not be root-writeable, I would do this first:
sudo mkdir /data
sudo chown ldm:ldm /data
mkdir -p /data/realtime/fetched/radar
I think you are coming from a root-user perspective, and assuming that
everything for which you don't explicitly specify should be
root-owned.
I'm assuming that if I'm issuing a command to create something (e.g. a
directory tree) for a non-root user, *everything* that command creates
should be owned by that non-root user. If I wanted part of my
directory tree owned by root, I would do that with a separate command
without the owner specified.
-- Chad
- [[chef-dev]] CHEF-1621 - "recursive" attribute on "directory" resource does not apply users and groups to entire path, Thomas Bishop, 10/02/2010
- [[chef-dev]] Re: [[chef-dev]] CHEF-1621 - "recursive" attribute on "directory" resource does not apply users and groups to entire path, Chad Woolley, 10/02/2010
- [[chef-dev]] Re: [[chef-dev]] CHEF-1621 - "recursive" attribute on "directory" resource does not apply users and groups to entire path, Thomas Bishop, 10/03/2010
- [[chef-dev]] Re: [[chef-dev]] CHEF-1621 - "recursive" attribute on "directory" resource does not apply users and groups to entire path, Chad Woolley, 10/03/2010
- [[chef-dev]] Re: [[chef-dev]] Re: [[chef-dev]] CHEF-1621 - "recursive" attributeon "directory" resource does not apply users and groups to entire path, Seth Falcon, 10/03/2010
- [[chef-dev]] Re: [[chef-dev]] Re: [[chef-dev]] Re: [[chef-dev]] CHEF-1621 -"recursive" attributeon "directory" resource does not apply users and groups to entire path, Chad Woolley, 10/03/2010
- [[chef-dev]] Re: [[chef-dev]] Re: [[chef-dev]] Re: [[chef-dev]] Re: [[chef-dev]]CHEF-1621 -"recursive" attributeon "directory" resource does not apply users and groups to entire path, Daniel DeLeo, 10/04/2010
- Message not available
- [[chef-dev]] Re: [[chef-dev]] Re: [[chef-dev]] Re: [[chef-dev]] CHEF-1621-"recursive" attributeon "directory" resource does not apply users and groups to entire path, Daniel DeLeo, 10/05/2010
- [[chef-dev]] Re: [[chef-dev]] Re: [[chef-dev]] Re: [[chef-dev]] Re: [[chef-dev]]CHEF-1621-"recursive" attributeon "directory" resource does not apply users and groups to entire path, Seth Falcon, 10/12/2010
- [[chef-dev]] Re: [[chef-dev]] Re: [[chef-dev]] Re: [[chef-dev]] Re: [[chef-dev]]Re: [[chef-dev]]CHEF-1621-"recursive" attributeon "directory" resource does not apply users and groups to entire path, Thomas Bishop, 10/13/2010
- [[chef-dev]] Re: [[chef-dev]] Re: [[chef-dev]] Re: [[chef-dev]] Re: [[chef-dev]]Re: [[chef-dev]]CHEF-1621-"recursive" attributeon "directory" resource does not apply users and groups to entire path, Seth Falcon, 10/14/2010
- [[chef-dev]] Re: [[chef-dev]] Re: [[chef-dev]] Re: [[chef-dev]] Re: [[chef-dev]]Re: [[chef-dev]]CHEF-1621-"recursive" attributeon "directory" resource does not apply users and groups to entire path, Thomas Bishop, 10/18/2010
Archive powered by MHonArc 2.6.16.