[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#24251: Potential cp bug: directories created with --parents and --no
From: |
Pádraig Brady |
Subject: |
bug#24251: Potential cp bug: directories created with --parents and --no-preserve=mode retain original mode bits don't match ~umask |
Date: |
Thu, 18 Aug 2016 13:57:48 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 |
On 17/08/16 12:42, Mark Mitchell wrote:
> Hi,
>
> I'm writing to report a potential bug with cp. I don't think the mode bits
> always get properly set on directories created when using the --parents
> option combined with --no-preserve=mode option. I'm not sure what the
> expected behaviour is supposed to be, but my assumption is that the created
> directories would match process's ~umask (like mkdir -p).
>
> I've attached a simple script and its output to demonstrate the behaviour.
> I've tested this on the most recent master branch of the coreutils git
> repository (output of git describe is 'v8.25-55-gff2178b').
>
> Thanks for your efforts on these utilities, it is much appreciated :-).
I agree that's unexpected, especially since cp -r --no-preserve=mode
does not copy the permissions for created dirs.
I think this may have changed with:
http://git.sv.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=v5.92-435-gfdffb6b
I've adjusted things back in the attached.
thanks,
Pádraig.
cp-parents-no-preserve-mode.patch
Description: Text Data