public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: <cygwin@kosowsky.org>
To: Mirko Vukovic <mirko.vukovic@gmail.com>
Cc: cygwin@cygwin.com
Subject: Re: Can't resolve "Your group is currently "mkpasswd"'
Date: Wed, 01 Aug 2012 17:38:00 -0000	[thread overview]
Message-ID: <20505.27002.935583.725604@consult.pretender> (raw)
In-Reply-To: <CAO73BAA6NJwVSeH+dg_yvKPGvjsGubmo55poXz6=ShZnmMxRiQ@mail.gmail.com>

Mirko Vukovic wrote at about 10:19:31 -0400 on Wednesday, August 1, 2012:
 > On Wed, Jul 18, 2012 at 10:35 PM, <...> wrote:
 > >
 > > I just tried to set up cygwin on my new corporate pc (I have admin
 > > privileges on the machine but not on the overall corporate network).
 > >
 > > I keep getting the infamous 'Your group is currently "mkpasswd"' every
 > > time I open a new terminal.
 > >
 > > Since this is a domain, I first tried "mpasswd -l -d >| /etc/passwd"
 > > but the domain lookup seemed to hang forever (after first generating
 > > the local group portion). Note that "mkgroup -l -d >| /etc/group
 > > worked but was slow.
 > 
 > 
 > In my case, mkpasswd -d is an exercise in patience (many minutes,
 > definitely less then 30), but it does eventually return a very long
 > list.  Let it run.
 > 

I did that... but I still get the same error message and the group is
still all mkpasswd.

My /etc/passwd and /etc/group files "seem" right so I don't know why
it isn't working. Frustrating!

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

      reply	other threads:[~2012-08-01 17:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-19  2:35 cygwin
2012-07-19  7:28 ` Corinna Vinschen
2012-08-01 14:19 ` Mirko Vukovic
2012-08-01 17:38   ` cygwin [this message]

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=20505.27002.935583.725604@consult.pretender \
    --to=cygwin@kosowsky.org \
    --cc=cygwin@cygwin.com \
    --cc=mirko.vukovic@gmail.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).