Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Message-ID: <058801c2d4cd$f15949a0$ab7886d9@webdev> Reply-To: "Elfyn McBratney" From: "Elfyn McBratney" To: "cygwin" Cc: "christophe thiebot" , "Peter Canning" References: <050501c2d4ab$7097ae00$ab7886d9 AT webdev> <20030215082740 DOT GG5822 AT cygbert DOT vinschen DOT de> Subject: Get it sorted! (was Re: Group name getting set to 'mkpasswd') Date: Sat, 15 Feb 2003 08:40:48 -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 > On Sat, Feb 15, 2003 at 04:33:47AM -0000, Elfyn McBratney wrote: > > Also this was in the strace output that Peter sent in, I withheld this bit, > > as I didn't quite know whether this was intended (from mkpasswd's side) > > > > 65 19353 [main] mkpasswd 1148 pwdgrp::read_group: Completing > > /etc/group: > > mkpasswd:S-1-5-21-1045767534-453787399-1741382010-513:401:canning > > > > Just wondered what to reply with. Is it a simple matter of running mkgroup? > > or mkpasswd? > > Yup. The group name says it all. One for the archives: If anyone finds their group name or username set to "run" or "mkpasswd" or "mkgroup"...You need to do exactly that, run mkpasswd or mkgroup to update /etc/passwd or /etc/group respectively. There's some new detection code to let you know when your /etc/{group,passwd} file is stale. So Peter Canning, you will need to run mkpasswd. And to Christophe Thiebot, you will need to run mkgroup. I've CCd in case your not on the list ;-) Regards, Elfyn McBratney elfyn AT exposure DOT org DOT 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/