public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Harig, Mark A." <maharig@idirect.net>
To: "Rick Hellicar (QMP)" <Rick.Hellicar@eml.ericsson.se>,
	<cygwin@cygwin.com>
Subject: RE: mkpasswd takes 18 hours to finish!
Date: Fri, 13 Sep 2002 08:24:00 -0000	[thread overview]
Message-ID: <BADF3C947A1BD54FBA75C70C241B0B9E762F0E@ex02.idirect.net> (raw)

Normally you would use:

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

Of course, now that you have your passwd entry,
you should edit /etc/passwd and extract your
entry from the file, save it to a separate
file, discard /etc/passwd, regenerate it
using 'mkpasswd -l > /etc/passwd', and
add your entry to the new, smaller file.

> -----Original Message-----
> From: Rick Hellicar (QMP) [mailto:Rick.Hellicar@eml.ericsson.se]
> Sent: Friday, September 13, 2002 9:34 AM
> To: 'cygwin@cygwin.com'
> Subject: mkpasswd takes 18 hours to finish!
> 
> 
> Hi people,
> 
> I've been attempting to set up ssh, because, er..., it seems 
> to be what everyone else is doing!
> 
> Got to the "mkpasswd -d" stage, which listed a bunch of 
> people that didn't include me, so I was explicit about the domain:
> 
> mkpasswd -d MY_DOMAIN >> /etc/passwd
> 
> And it proceeded to list 22,795 of my colleagues and the time 
> it took was...
> real    1118m45.573s
> user    2m4.187s
> sys     2m23.515s
> 
> Yep - over 18 hours for the command to finish!
> Can anyone beat that?
> 
> Rick
> 
> 
> 
> --
> 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/
> 
> 

--
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 15:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-13  8:24 Harig, Mark A. [this message]
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
     [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=BADF3C947A1BD54FBA75C70C241B0B9E762F0E@ex02.idirect.net \
    --to=maharig@idirect.net \
    --cc=Rick.Hellicar@eml.ericsson.se \
    --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).