Re: TEST RELEASE: Cygwin 1.7.33-0.7

[Corinna Vinschen <corinna-cygwin@cygwin.com>]

[-- Attachment #1: Type: text/plain, Size: 3348 bytes --]

On Nov  7 13:04, Pierre A. Humblet wrote:
> > -----Original Message-----
> > From: Pierre A. Humblet 
> > Sent: Thursday, November 06, 2014 16:09
> > 
> > > -----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?
> > 
> > Right, and ditto for exim config and postinstall How much time do I have?
> > 
> > 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" recently.
> > 
> > How does getent handle that case? Is it detectable from a config file?
>  
> Corinna
> 
> 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)  

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

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]