From: "Pierre A. Humblet" <Pierre.Humblet@ieee.org>
To: <cygwin@cygwin.com>
Subject: RE: TEST RELEASE: Cygwin 1.7.33-0.7
Date: Thu, 06 Nov 2014 21:09:00 -0000 [thread overview]
Message-ID: <03eb01cffa05$e0c65af0$a25310d0$@ieee.org> (raw)
In-Reply-To: <20141106185102.GL28195@calimero.vinschen.de>
> -----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?
Pierre
--
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:[~2014-11-06 21:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20141106155247.GA32104@calimero.vinschen.de>
2014-11-06 18:38 ` Kelley Cook
2014-11-06 18:51 ` Corinna Vinschen
2014-11-06 21:09 ` Pierre A. Humblet [this message]
2014-11-06 21:37 ` Corinna Vinschen
2014-11-07 18:05 ` Pierre A. Humblet
2014-11-10 11:09 ` Corinna Vinschen
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='03eb01cffa05$e0c65af0$a25310d0$@ieee.org' \
--to=pierre.humblet@ieee.org \
--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).