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=EiXQsqg2cnz3hpjIP+B5qcFAIkIhfTFe4aSwJ/qAIA2dQNlTH6iqT
	zdKV3faO55AlZuBHMUK2vAs/ifRLQX1IbCVmNfnFLQuArjWaaUe+pyh0xbcrQlQP
	jMb9YESrQ5j5qAfdiMaKcEBmgNE9BwHUENzh6t2WKt1q3cwiYcn2dg=
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=AtxRxZVcIGgEGZzqFoFIpCcbzsM=; b=y5WAwOElP7zGaAuO8Xa2Y408yqGU
	JsCzVPoPUIQnB0nJT7h/WyUJa0buvIL5lW0HOnT9g381ZgZ1C0DiwWZgkqpGzH1w
	1EZo9hNWMuJJePN2NmW5jUK2jCFeICjlivaUM225ugsItXmsFa0HYQhhBdJqWRR+
	vE44K1eHucpeDZI=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
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
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, 23 Feb 2015 11:37:22 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.35-0.3
Message-ID: <20150223103722.GE437@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <announce DOT 20150218105937 DOT GA28211 AT calimero DOT vinschen DOT de> <87d255htw7 DOT fsf AT Rainer DOT invalid> <20150220095617 DOT GO26084 AT calimero DOT vinschen DOT de> <54E75BB9 DOT 90807 AT coverity DOT com> <20150220162442 DOT GA26084 AT calimero DOT vinschen DOT de> <54E763CD DOT 9000307 AT coverity DOT com> <20150220170354 DOT GE26084 AT calimero DOT vinschen DOT de> <01a801d04dfb$559829f0$00c87dd0$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="G6nVm6DDWH/FONJq"
Content-Disposition: inline
In-Reply-To: <01a801d04dfb$559829f0$00c87dd0$@gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)

--G6nVm6DDWH/FONJq
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Feb 21 12:25, cyg Simple wrote:
> > From: Corinna Vinschen
> >=20
> > Maybe it is actually simpler than that.  Invalidating the cache as a wh=
ole
> > probably never makes sense.  In fact there are two reasons for
> > invalidation:
> >=20
> > - The pw_name, pw_shell, pw_home, pw_gecos settings for a user changed.
> >=20
>=20
> How is pw_name going to change without a logoff?

You're looking at the current user only.  I'm talking about creating
arbitrary passwd entries.

> > - The interface to the DC was broken and there are entries of the type
> >   Achim mentioned, "DOM+User(RID)".
> >=20
> > The first case can only be fixed by invalidating the cache on a regular=
 basis.  If
> > we didn't fetch the info for a user for, say, 5 minutes, drop the entry=
 from the
> > cache and renew the information by asking the DC again.
> >=20
>=20
> Maybe too many requests to the DC for all users?  Couldn't you just
> reinitialize if the network data changes?  There are times when I
> would be on the DC and times when I am not with the same account.

Doesn't matter, we're not invalidating the cache yet anyway.  It was
just idle musing.


Corinna

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

--G6nVm6DDWH/FONJq
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBAgAGBQJU6wLiAAoJEPU2Bp2uRE+gH4sP/0jgCWW2fPDISzrwuKghkW2B
6InCt7QVjmBfLlJ1WK+QltrEjli7aVCp8qOybU+oHPtd9zsKp0EtOjYF3DN6L3ix
a45jvMhbZWT1/RNijmsYtfgmKoQx/Jh/Y5XgM2X3zmJqnHGKrrwWDBiybnCydb0K
QfQWZN5PfwCyo7ZNKcMezQlB3Rp8wiZcsT9Q4ByOkWhe6YFSfxkL/jO3bf5+oXbs
pRZA9udbXOOUr13XI87uuZZyt1o2W64YNIMg/7oy8Q/62AucoYbZul69sF0F2wgo
3l6P2xoHWgQPe9kAI+y/MUqdbXeCMDzDVeGrJIapuvLoxGQj9SKU8J3rpkCbNx6g
s98WOMw4b2h7VIOno0KiYEwwrI29kH/dLrJeWcXrrL4u7M0pIbfvuzNo64unZY4b
KRlKGaFMqxF5cBdcwogz8Lrn1oTQwf7GAweFDtdoKvVv9/GdgasMoabSREZgtK2M
zNwdGNdXFWk0+Vm28m2lRbNheV1bi+vblYmx6T7ULqTC4V/vn3RoexAYSgrJnUoW
8uYyrB02g/yJVkPJCsQ9vZxmaUfqZGVl+o42UzK71UgxuNG1nL88bFJkV2vzhTmH
xNkeZ1cFfENit82mgiyhNr0Ep/+5Shsk40+wZhgYX5pHNglDyPn+JLPaRRKr93wZ
AvnIooMfDqfam7psirXq
=2KHq
-----END PGP SIGNATURE-----

--G6nVm6DDWH/FONJq--