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:date:from:to:subject:message-id:reply-to :references:mime-version:content-type:in-reply-to; q=dns; s= default; b=L8iiN8ffoKxJOeFi3EoqvWIfrkJ1ioAzCWUZ9k1zyaYXjOYC7U2gE JmS+xE+KmAfrrt2iPJK+WknhscvV81rU8bt8bOCZBn7d3oh+ni0ctNKMwMX48jNM ScPCI3w2EiS2118IeUYu1JZyoedc36U1gPqV1DuUsGwWvCAJPnIZYw= 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:date:from:to:subject:message-id:reply-to :references:mime-version:content-type:in-reply-to; s=default; bh=4SuhUdU/6KJIiWalt3/KPeV59T4=; b=r5LqAEYSiYQQl0Vf6C4NblZua4sE dZt57ZH2oxrKw4f3qdWhpmnKKP9/+SgGlEVpK+spzNuVapUZurlZd1g7FU0yzp1T 9XSKNN8rYfyvYVgXpJzNUoEnsUQkJtBHyQpt6Lr+f5IZGdJAMyOjv+t/hSSbAaSc VQ5m58UicgtztAk= 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=-5.9 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2 X-HELO: calimero.vinschen.de Date: Mon, 10 Nov 2014 12:09:17 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: TEST RELEASE: Cygwin 1.7.33-0.7 Message-ID: <20141110110917.GD2782@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20141106155247 DOT GA32104 AT calimero DOT vinschen DOT de> <20141106185102 DOT GL28195 AT calimero DOT vinschen DOT de> <044301cffab5$52eca9e0$f8c5fda0$@ieee.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="IDYEmSnFhs3mNXr+" Content-Disposition: inline In-Reply-To: <044301cffab5$52eca9e0$f8c5fda0$@ieee.org> User-Agent: Mutt/1.5.23 (2014-03-12) --IDYEmSnFhs3mNXr+ Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Nov 7 13:04, Pierre A. Humblet wrote: > > -----Original Message----- > > From: Pierre A. Humblet=20 > > Sent: Thursday, November 06, 2014 16:09 > >=20 > > > -----Original Message----- > > > From: Corinna Vinschen > > > Sent: Thursday, November 06, 2014 13:51 > > > > > > On Nov 6 13:38, Kelley Cook wrote: > > > > On Thu, Nov 6, 2014 at 10:52 AM, Corinna Vinschen wrote: > > > > > Hi Cygwin friends and users, > > > > > > > > > > > > > > > I just released a 7th TEST version of the next upcoming Cygwin > > > > > release, 1.7.33-0.7. > > > > > > > > > > > > > I discovered that /usr/bin/cron-config which is part of the cron > > > > package will need to be updated as it attempts to parse /etc/group . > > > > > > Right, it should use getent instead. Pierre? > >=20 > > Right, and ditto for exim config and postinstall How much time do I hav= e? > >=20 > > Now cron-config checks if a username appears multiple times in passwd. > > Typically one instance is a domain id and the other one is a local id. > > That causes havoc with cron > > It happens fairly frequently; there was even such a "bug report" recent= ly. > >=20 > > How does getent handle that case? Is it detectable from a config file? >=20=20 > Corinna >=20 > I just realized that deleting the /etc/passwd file in existing domain > systems may change usernames, which will break cron and other programs > that use files named after usernames. Also the (local) privileged > username will change. Yes. Is there a way to accommodate that? Maybe a postinstall script checking for existing user cron files and renaming them if required? The privileged user name shouldn't matter much after configuration. > For now I have made the following changes to cron-config: > calling getent > checking if /etc/passwd exists > dealing with the extended names for privileged users (they may > contain a +, don't use EREs)=20=20 I just scanned it quickly, but the change looks good. For all of this, apart from the Cygwin-internal stuff, I'm in the same boat as anybody else. I'm not entirely sure about all the consequences this change will have, and we might all be missing something crucial during the transition. > Do you intend to keep mkpasswd/mkgroup ? Yes. It's still supposed to be used if somebody needs passwd entries for some reason. For the details, see the preliminary documentation at https://cygwin.com/preliminary-ug/ntsec.html and https://cygwin.com/preliminary-ug/using-utils.html#mkpasswd and https://cygwin.com/preliminary-ug/using-utils.html#mkgroup. Note also the discussion with Christian starting at https://cygwin.com/ml/cygwin/2014-11/msg00095.html I have a potential patch in the loop which implements what I wrote here: https://cygwin.com/ml/cygwin/2014-11/msg00121.html > I still don't have a 64 bit system, but it's coming this year. It will > take me some time to prepare a new cron package and get familiar with > the new package upload procedure. I am attaching a cron-config diff. > Feel free to update the 32 and 64 bit cron packages if you want that > done quickly. cronbug does not seem to require any changes. Thanks, Corinna --=20 Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat --IDYEmSnFhs3mNXr+ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJUYJzdAAoJEPU2Bp2uRE+g6KMP/2hcb6w7joqf/upqw+xjoVC+ CjENYr93nKQVbLP9rhS5vv2K/YyTq5gPsxCEnHrUqo5Jn+HN4EUHxvdjEcWPA3XQ fKNYHI/6FzvgZPrfk6dVIAn4aQ6XoDxW8fugpfNyw1vu/NNEQKWhuuTh9rXB5yFm k5OaZ5xmAq54heKWfn0BeJLGZmGqtI+KM5x3s1Z8kXGqWJQtY/5AtmW1PHEmgKJs bHX+oAa0qk1Z8sCyIZK6LBfnNzjFBIy5PGJxu6OoB0iw5cgc/VtYB3e9uqcgi7db XdWjJ0orqF9EZNAibAuxMpP/mZxLRxWUvi3CAsG7b/nD2TglzI5tcsyZ+ECH9xoq ojvomF081CsqEZJrsjjfSvJAwzMoj0jZt/YXfuBFZtQR333riTHdjFuKbk3M2r3p HUF7HGsQRgvvqdsh0Dr+OZo9MaJ3GOETQ+Zi/7J+pB2bqMfhGAaVLgC2Hv8t5IVo X1OK6/ONfiKquZ5uiWNBse7ys5xeyVm5j5Vfgx+5F49cZCslrs0rQxMK95/QGZ9w h6wHxulL1FOIu65TCPLTCop1948stUpu/7gTk7MT79HIoxxAjGxycBH7NwwN+T3y ZZdeO98XD7c7jxwdxAL8L3serXw0cfWvDUsUuEburPsG6GzE7J2gxkNONTwRm1/2 UK2D6d+ALe+Px418NmNQ =TB+C -----END PGP SIGNATURE----- --IDYEmSnFhs3mNXr+--