X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type:content-transfer-encoding; q=dns; s=default; b=m+pR7wDzIfn7N3xM6dw3i4FSudrUMJo6EIAx6/mZ1fl dYVdDd3kNxqI3jxI2m0U+QQhENZdHw7aM1VJEXD1KjgMp955Ebx15gSJ0i1S28nc 7qx9Wqii/4OptcLam0Ip5DXo/VBWCxrUiXxCyOfKk+OPdVrxJEzMc5+RuEt4XNow = DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type:content-transfer-encoding; s=default; bh=xdF89w/WoXPJZC4fQD6YP4dVHQ4=; b=fHisyDr44Jn/F2SDc XhklDOuOgbbuj4Cs+qv80t98ETfvACUco3/ucYgzGft6rhW8zV1bCng1/6wQmG40 QNe1KJsr/pGs3pHpE3Zsa9xuomjvIqxSG2mwX6PPdia1m9OpgT5QODnR2Qwb8PSW edmTMqr1bnwTXDJWMSv4Sp9DM4= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=1.5 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD autolearn=no version=3.3.2 spammy=moss AT cs DOT umass DOT edu, D*cs.umass.edu, U*moss, sk:mosscs X-HELO: kautler.net X-Gm-Message-State: AEkoousEffShPNXwK/Wwx3yBeCzYJDsFVdXh/d/wWlmJVn2Y4fCryl41vlxBD6eQWPcFI9dG0UGgkqNtHl5gFg== X-Received: by 10.28.131.208 with SMTP id f199mr13451910wmd.116.1471852798405; Mon, 22 Aug 2016 00:59:58 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References:

From: =?UTF-8?Q?Bj=C3=B6rn_Kautler?= Date: Mon, 22 Aug 2016 09:59:37 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Wrong file permissions To: moss AT cs DOT umass DOT edu, cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id u7M80i1w019216 Hi Eliot, thanks for your answer. It seems this was an issue with the NTFS permissions. I also was not able to access the folders via Windows Explorer. After also fixing the Windows permissions it works now as expected so far. Do you really think I got a new SID on the new box when logging in with the same user of the same domain? Can I check this somehow? Why should the setup be redone on a new box? I'd need to do redo all installations, configuration, and so on. Besides ths permsissions issue I had, why shouldn't I just copy over the whole cygwin root directory? Everything cygwin related should be in there, isn't it? Regards Björn 2016-08-19 16:17 GMT+02:00 Eliot Moss : > On 8/19/2016 8:27 AM, Björn Kautler wrote: >> >> Hi, >> >> I have a problem I hope you can help me to solve. >> I switched to a new box at work and copied over my whole cygwin folder via >> rsync from the old box to the new one. >> But now if I do "touch tmp", the file gets 060 permissions and not 644 >> like >> before. >> This is very disturbing, as not even "cat <<> with >> "bash: cannot create temp file for here-document: Permission denied". >> >> I hope you can help me with this one. > > > First, I suspect that Corinna, et al., will be interested in the output > of icacls applied to a file/folder in question, and possibly cygcheck > output. Second, rsync'ing your stuff over probably does not respect > that you almost certainly have a new Windows SID on your new box. You > probably need to change over ownership. And any group(s) you assigned > probably did not carry over either. Yeah, it's a pain moving to a new > box. I suspect others on the list will have suggestions as to best > procedure to follow when moving over. > > In any case, this suggests using Windows commands (manipulation from > a File Explorer opened with admin privileges) to insure that all your > files have the right owner, and (if you follow my scheme mentioned > below) to add a new group to the files (that can also be done using > a recursive chgrp once things are in a state to allow it). > > For my part, I have found it helpful (or to my taste anyway) to create > a new group, distinct from my user identity. (Windows typically kind > of conflates the two, i.e., each user *is* a group, and that group is > typically the primary group of files for which you are the primary > user / creator.) I then chgrp all my Cygwin files to that group, and > also set folders to propagate their group to newly created files > (g+s, or 2000, permission on directories). For my backup programs > to work I also set for all files/folders to have read access by > SYSTEM and for that to propagate from folders. For files created by > Windows programs I still sometimes need to adjust their group manually > (sigh). > > I hope this hasn't been too terse for you to get some useful guidance. > > Cygwin community: Do we have guidance in the FAQ about moving a Cygwin > installation to a new box? (I mean the user's files, not the install > done by setup -- which (IMO) should be redone on a new box, not copied.) > > Regards -- Eliot Moss > > -- > 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 > -- 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