Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <ba40711f0507051351767b7a1e@mail.gmail.com>
Date: Tue, 5 Jul 2005 16:51:21 -0400
From: Lev Bishop <lev DOT bishop AT gmail DOT com>
Reply-To: Lev Bishop <lev DOT bishop AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: chmod suddenly ceased to work on old files - AFTER CYGWIN UPDATE
In-Reply-To: <25F7D2213F14794A8767B88203EA2BC9240C91@mucse201.eu.infineon.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Disposition: inline
References: <25F7D2213F14794A8767B88203EA2BC9240C91 AT mucse201 DOT eu DOT infineon DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id j65KpYh9018483

On 05/07/05, FischRon wrote:

> Actually I wasn't able to use "-d" with mkpasswd, because this command
> hung, so I did a "mkpasswd -l >/etc/passwd" instead. Maybe I should
> rerun mkgroup -l (without -d option)?

Really hung, or just taking a very very long time (it will, if it is a
large domain)?
If the latter, you could try using the -c and/or -u options to
mkpasswd to only get the information for a subset of the users (ie
just the ones who use your machine). Or construct the /etc/passwd file
by hand if you know what you're doing....

> But in any case, recreating the /etc/group file did nothing to remedy
> my problem.

What kind of server are these files on? If it is a SAMBA share (on eg
linux, as opposed to a SMB share from WinNT), then maybe this message
is helpful:
http://www.cygwin.com/ml/cygwin/2000-12/msg00567.html

Otherwise if it is an SMB share, maybe you need to give your accounts
(both locally and on the server) the "restore files and directories"
(SeRestorePrivilege) privilege, which may not be practical as its a
security hole. Though from reading the mailing list archives it seems
that so long as the machines are part of a domain and your user
account is a domain account, then this is supposed to be unnecessary.

Finally, you could always set the CYGWIN environment variable to
include 'nosmbntsec' to switch off all use of ntsec on shares.

Lev

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/