public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Igor Pechtchanski <pechtcha@cs.nyu.edu>
To: cygwin@cygwin.com
Subject: RE: mkpasswd takes 18 hours to finish!
Date: Fri, 13 Sep 2002 12:23:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.44.0209131436280.19696-100000@slinky.cs.nyu.edu> (raw)
In-Reply-To: <5.1.0.14.2.20020913141745.027833e0@mail.biapo.com>

On Fri, 13 Sep 2002, rotaiv wrote:

> 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).

Yes, but the original poster's problem was that his username was not in
the default domain.  Thus, your solution won't work.

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

This is not true.

Specifying both the username and the domain name results in extracting
just that one user from the domain (as can be plainly seen from the source
of mkpasswd.c).

It may be that the order of arguments matters, and that the correct way to
specify the username and the domain would be
	mkpasswd -u MY_USER_ID -d MY_DOMAIN >> /etc/passwd
but the point remains the same.

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

The last point is true, but, as far as I could see, was not disputed by
anyone.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

It took the computational power of three Commodore 64s to fly to the moon.
It takes a 486 to run Windows 95.  Something is wrong here. -- SC sig file


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

  reply	other threads:[~2002-09-13 18:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-13  8:24 Harig, Mark A.
2002-09-13  8:37 ` Igor Pechtchanski
     [not found] ` <Pine.GSO.4.44.0209131122160.19696-100000@slinky.cs.nyu.edu >
2002-09-13 12:09   ` rotaiv
2002-09-13 12:23     ` Igor Pechtchanski [this message]
     [not found]     ` <Pine.GSO.4.44.0209131436280.19696-100000@slinky.cs.nyu.edu >
2002-09-13 13:39       ` rotaiv
2002-09-14 11:47         ` David MacMahon
  -- strict thread matches above, loose matches on Subject: below --
2002-09-16  2:22 Rick Hellicar (QMP)
2002-09-13 13:49 Harig, Mark A.
2002-09-13  7:17 Rick Hellicar (QMP)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.GSO.4.44.0209131436280.19696-100000@slinky.cs.nyu.edu \
    --to=pechtcha@cs.nyu.edu \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).