Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <025601c2d8bb$fcbc0660$526286d9@webdev> From: "Elfyn McBratney" To: "cygwin" , References: Subject: Re: MANPATH Problems Date: Thu, 20 Feb 2003 08:42:22 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 > > AFAIK there's some new "detect stale group and passwd" code that detects a > > change and changes your user/group name accordingly. If you > > update the file > > anyway, as sid or gid may have changed, and see if that helps. > What would I have to type on the command line to get this new detection code > executed? Sorry, reading what I said what a bit in the details-lacking variety :-) What I meant was that cygwin1.dll now detects when the information in /etc/passwd and /etc/group is stale (?). So if your username or group name is set to mkpasswd or mkgroup that's the user's alert to update those that file or files. The code isn't executed by mkpasswd or mkgroup, it's part of the kernel, cygwin1.dll . Did updating the your /etc/group fix your problem? Regards, Elfyn McBratney elfyn@exposure.org.uk www.exposure.org.uk -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/