From: Eliot Moss <moss@cs.umass.edu>
To: cygwin@cygwin.com
Subject: Re: Can I eliminate diagnostic messages from cp
Date: Fri, 20 May 2016 17:48:00 -0000 [thread overview]
Message-ID: <dbaf98e7-ab98-9157-3d10-ae7efc4f2a5e@cs.umass.edu> (raw)
In-Reply-To: <3e817f56-2193-6a63-ec27-1f49dc2b2e00@att.net>
On 5/20/2016 1:45 PM, lostbits wrote:
> I use cp as my backup tool from disk to USB. There are maybe 40,000 files involved and each one has
> a message of
> "cp: preserving permissions for <file>â: Not supported". These messages slow down the backup and
> obscure meaningful faults. Is there any option for removing the messages?
>
> My command line is: cp <directory> /<usb>
Umm, add command line flags that don't request the permissions to be set?
E.g., --no-preserve=mode
You can play around with the various options of preserving / not preserving
mode, ownership, date/time, etc.
Regards -- Eliot
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2016-05-20 17:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 17:45 lostbits
2016-05-20 17:48 ` Eliot Moss [this message]
2016-05-20 18:05 ` Andrey Repin
2016-05-22 7:09 ` Brian Inglis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dbaf98e7-ab98-9157-3d10-ae7efc4f2a5e@cs.umass.edu \
--to=moss@cs.umass.edu \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).