Thanks for the clarification! > -----Original Message----- > From: Igor Pechtchanski [mailto:pechtcha@;cs.nyu.edu] > Sent: Wednesday, October 30, 2002 5:04 PM > To: Harig, Mark A. > Cc: Jason Dufair; [EMAIL PROTECTED] > Subject: RE: sshd install troubles > > > On Wed, 30 Oct 2002, Harig, Mark A. wrote: > > > > I set up the CYGWIN system environment var as "binmode tty > > > ntsec". I did a > > > mkpasswd -d -u mydomainlogin >> /etc/passwd > > > > For future reference: it has been found that the order > > of mkpasswd's '-d' and '-u' options is significant. > > On some systems/networks, it has been found that > > 'mkpasswd' runs much faster if '-u' precedes '-d'. > > No. The order of the *options* doesn't matter. The > confusion arises from > the fact that the domain name is *not* a parameter of the "-d" command > line option, but a stand-alone argument. Thus, putting the > domain *name* > after the "-d" option, but before the "-u domainuser" option > leads to the > "-u" option being ignored, and all users in the domain being > listed, which > can be quite time consuming. If the domain name is given as the last > argument, the order of "-d" and "-u domainuser" doesn't matter, i.e., > mkpasswd -d -u mydomainlogin mydomainname > and > mkpasswd -u mydomainlogin -d mydomainname > should be identical. > Again, if the domain name is specified before the "-u" option, i.e., > mkpasswd -d mydomainname -u mydomainlogin > the "-u" option is ignored, and all domain users are listed. > > This is counterintuitive, but that's the way mkpasswd and > mkgroup work. > Igor > -- > http://cs.nyu.edu/~pechtcha/ > |\ _,,,---,,_ [EMAIL PROTECTED] > ZZZzz /,`.-'`' -. ;-;;,_ [EMAIL PROTECTED] > |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski > '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! > > "Water molecules expand as they grow warmer" (C) Popular > Science, Oct'02, p.51 > >
-- 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/