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=Y/Yu5gxn+Q8ij9+QiXpeDl58FjTyT jg1CSXOWxCJJNGc1/qbauFp/OlSmEE0WSND0pT0xuiGBh+uZKinCZwY93X1PZLUR Z1iVZ/p452lsncwksocHdYZez60aPn2rDBzBVHjTpgRzuocENgMLyIAvt0F3SUMm QrsAs2wrfuJbO0= 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=OFHJcZoHrfVCDuhrBtLN+3sGjOk=; b=yGo 2rXjAoIkawc7u5mZB8kNXJ783ADmYO5SrwxaoIAYOyg0CEf5UcJMbKlT6USkZNls yO+VA/w9sv5l9dIM7Yl/cwj/r+ANH/pzCJFD51tJUtTIkcuDFMY3L1THso6t6Kr6 6JdoXlrHA1tG1VPNjBizBXg/OW/FqFh0NUNC8Lkc= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Delivered-To: corinna-cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 X-Spam-User: qpsmtpd, 2 recipients X-HELO: nihxway2out.hub.nih.gov X-IronPortListener: Outbound_SMTP X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqAEAPyg9lKcKEep/2dsb2JhbABZhBu/WIEfdIIlAQEBAwESKEQLAgEIIgsJEB8TJQIEARoah1sInmmqWReOTDgKgxqBFASOY5tpgW+BPoIq From: "Lavrentiev, Anton (NIH/NLM/NCBI) [C]" To: Corinna Vinschen , "cygwin AT cygwin DOT com" Subject: RE: get rid of getpwent? (Was: cygwin-1.7.28 getpwent header declaration changes ?) Date: Sat, 8 Feb 2014 21:29:40 +0000 Message-ID: <5F8AAC04F9616747BC4CC0E803D5907D0C47C84B@MLBXv04.nih.gov> References: <52F339CA DOT 5070305 AT gmail DOT com> <20140206090117 DOT GD2821 AT calimero DOT vinschen DOT de> <52F361C5 DOT 3000807 AT gmail DOT com> <20140206141321 DOT GI2821 AT calimero DOT vinschen DOT de> <52F40208 DOT 5030901 AT etr-usa DOT com> <20140207094917 DOT GN2821 AT calimero DOT vinschen DOT de> <52F53D7C DOT 5050201 AT etr-usa DOT com> <20140207213013 DOT GT2821 AT calimero DOT vinschen DOT de> <5F8AAC04F9616747BC4CC0E803D5907D0C47C45C AT MLBXv04 DOT nih DOT gov>,<20140208103801 DOT GV2821 AT calimero DOT vinschen DOT de> In-Reply-To: <20140208103801.GV2821@calimero.vinschen.de> Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 X-IsSubscribed: yes Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id s18LUWcp009823 > and I fail to see how this is related to the on-the-fly generation of passwd and group entries Well, if a cygwin app was run under such an account, it might be affected, that's all... Anton Lavrentiev Contractor NIH/NLM/NCBI -- 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