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:from:to:subject:date:message-id:references
	:in-reply-to:content-type:content-transfer-encoding
	:mime-version; q=dns; s=default; b=ZfSfliruNNMR0gdozYhkEPlm/vbOH
	EQLjx6uv0QYU4UhhH4HhA5RV32fI+mhXMFXAxbMXL22BtirgVlJaU9p7uC/1/X77
	ZSaFGaEgXTYK3YnMh/oopEuH5AMYfykpLqcsWyBuWEXiJ7YbdQDOpuq4zlR8/CFL
	ilsaLRqm52V4II=
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:from:to:subject:date:message-id:references
	:in-reply-to:content-type:content-transfer-encoding
	:mime-version; s=default; bh=cVg5Z2+OF3e1t5FfOsI0AynS50w=; b=JNy
	afDMuuXtrEQKj5iuQFSZkeZYE/iDNQXji+FxHeyGiFNPM6XJRB65iZVwuD6ZDu0S
	s8PJNRZ1hYy7KtXRpYT1wXVQMypwZ/KGyvaXOACrIspGdNQLXJRDQlbbnwo4q1np
	Vfllh7muEOP1UX1QKtG29kdMzM6j9CFFnbLePeGA=
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
X-Spam-SWARE-Status: No, score=-4.1 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,MIME_BASE64_BLANKS,RCVD_IN_DNSWL_MED,RCVD_IN_HOSTKARMA_W,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS,TW_MK autolearn=ham version=3.3.1
X-IronPortListener: Outbound_SMTP
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AisLACAxkVGcKEew/2dsb2JhbABagweDc7xqBAIBDX0WbQeCHwEBAQMBEhERSgsCAQgNDQIGIAICAh0TFRACBBsah2QGoVqKEJAkgSaNUTiCQjJhA44bj0qKfIMPgic
From: "Lavrentiev, Anton (NIH/NLM/NCBI) [C]" <lavr AT ncbi DOT nlm DOT nih DOT gov>
To: "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject: RE: Why mkgroup does not list group members?
Date: Mon, 13 May 2013 18:30:51 +0000
Message-ID: <5F8AAC04F9616747BC4CC0E803D5907D0AF796AB@MLBXv04.nih.gov>
References: <5F8AAC04F9616747BC4CC0E803D5907D0AF7961F AT MLBXv04 DOT nih DOT gov> <20130513175045 DOT GJ8890 AT calimero DOT vinschen DOT de> <5F8AAC04F9616747BC4CC0E803D5907D0AF7964F AT MLBXv04 DOT nih DOT gov> <20130513180639 DOT GM8890 AT calimero DOT vinschen DOT de> <5F8AAC04F9616747BC4CC0E803D5907D0AF7968A AT MLBXv04 DOT nih DOT gov> <20130513182319 DOT GN8890 AT calimero DOT vinschen DOT de>
In-Reply-To: <20130513182319.GN8890@calimero.vinschen.de>
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id r4DIVHoZ022361

> I'm shuddering to think of the memory requirements if all gr_mem
> fields are filled in a bigger company.

Well, for supplementary groups (which it was supposed to be used for)
that does not actually look like very overwhelming...

Anton Lavrentiev
Contractor NIH/NLM/NCBI