Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Message-Id: <5.1.0.14.2.20020913141745.027833e0@mail.biapo.com>
X-Sender: biapo7@mail.biapo.com
Date: Fri, 13 Sep 2002 14:27:38 -0400
To: cygwin@cygwin.com
From: rotaiv <rotaiv@biapo.com>
Subject: RE: mkpasswd takes 18 hours to finish!
In-Reply-To: <Pine.GSO.4.44.0209131122160.19696-100000@slinky.cs.nyu.edu
 >
References: <BADF3C947A1BD54FBA75C70C241B0B9E762F0E@ex02.idirect.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

At 9/13/2002  11:24 AM, Igor Pechtchanski wrote:

Not to be over technical but you should use:

   mkpasswd -d -u MY_USER_ID >> /etc/passwd

This will retrieve a single user from the current domain without 
enumerating all the users.  This takes less than a second on my system 
(around 5,000 users).

An earlier email recommended the following:

>mkpasswd -d MY_DOMAIN -u MY_USER_ID >> /etc/passwd

The problem with this example is if you specify the domain it will still 
enumerate all the user accounts even though a user name was 
specified.  This will still take 18 hours for some people.  According to 
the help, the actually domain name is not needed as it defaults to the 
current domain.

Another email suggested this syntax:

>mkpasswd -d MY_DOMAIN | grep MY_USER_ID >> /etc/passwd

This will still enumerate all the user accounts but only keeps the 
MY_USER_ID line.  Once again, the actual domain name is not needed and this 
will still take 18 hours.

Regards,

rotaiv.



--
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/

