Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Subject: Re: cygipc (and PostgreSQL) XP problem resolved!
From: Robert Collins <rbcollins AT cygwin DOT com>
To: cygwin AT cygwin DOT com
In-Reply-To: <20030511014650.GB18993@redhat.com>
References: <3EBC8ED0 DOT 4040906 AT ece DOT gatech DOT edu>
	 <20030510072239 DOT GA19367 AT cygbert DOT vinschen DOT de>
	 <1052554219 DOT 1824 DOT 14 DOT camel AT localhost>
	 <20030510082949 DOT GD19367 AT cygbert DOT vinschen DOT de>
	 <3EBD3179 DOT 6070004 AT ece DOT gatech DOT edu> <20030510171629 DOT GB11448 AT redhat DOT com>
	 <3EBD3896 DOT 8000202 AT ece DOT gatech DOT edu> <1052612200 DOT 897 DOT 31 DOT camel AT localhost>
	 <20030511012322 DOT GA18836 AT redhat DOT com> <1052617309 DOT 897 DOT 43 DOT camel AT localhost>
	 <20030511014650 DOT GB18993 AT redhat DOT com>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-iCU+4P46aHcJX5Xc67/R"
Organization: 
Message-Id: <1052618088.907.49.camel@localhost>
Mime-Version: 1.0
Date: 11 May 2003 11:54:48 +1000

--=-iCU+4P46aHcJX5Xc67/R
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Sun, 2003-05-11 at 11:46, Christopher Faylor wrote:
> On Sun, May 11, 2003 at 11:41:49AM +1000, Robert Collins wrote:
> >On Sun, 2003-05-11 at 11:23, Christopher Faylor wrote:
> >> Or we can just use Global atoms, as I suggested in cygwin-developers.
> >
> >IIRC Global atoms are not global these days - they are global within a
> >single login at a time. I can't comment further without looking into the
> >ftok spec again, which I don't have time for right now...
>=20
> If that is really true, that would defeat the purpose of a global atom.

Not at all. From memory: Global Atoms come from before multi-user
kernels in the windows world. They are used for things like registering
clipboard types - which are *not* meant to cross user boundaries.

> I'm not sure what ftok has to do with whether global atoms are global
> or not, however.

ftok creates keys for use in IPC programs. They often need to cross user
boundaries - similar in concept to the privilege separation logic in
sshd these days.

If we use a global atom that isn't truely global, this will break.

Rob
--=20
GPG key available at: <http://users.bigpond.net.au/robertc/keys.txt>.

--=-iCU+4P46aHcJX5Xc67/R
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQA+va1oI5+kQ8LJcoIRAlq3AKCvZmJ8GUXyzKRgRDD6QN35PSo0sQCgu8pu
KppO8aHyzSZGWDiamLCbYjw=
=Hxp3
-----END PGP SIGNATURE-----

--=-iCU+4P46aHcJX5Xc67/R--