GNU bug report logs - #24251
Potential cp bug: directories created with --parents and --no-preserve=mode retain original mode bits don't match ~umask

Previous Next

Package: coreutils;

Reported by: Mark Mitchell <mark81 <at> gmail.com>

Date: Wed, 17 Aug 2016 15:35:02 UTC

Severity: normal

Done: Pádraig Brady <P <at> draigBrady.com>

Bug is archived. No further changes may be made.

Full log


Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Mark Mitchell <mark81 <at> gmail.com>
To: bug-coreutils <at> gnu.org
Subject: Potential cp bug: directories created with --parents and
 --no-preserve=mode retain original mode bits don't match ~umask
Date: Wed, 17 Aug 2016 11:42:40 +0000
[Message part 1 (text/plain, inline)]
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 :-).

-Mark
[Message part 2 (text/html, inline)]
[test-output.txt (text/plain, attachment)]
[test-cp-parents-umask.sh (application/x-sh, attachment)]

This bug report was last modified 8 years and 336 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.