public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Len Giambrone <Leonard.Giambrone@intersystems.com>
To: <cygwin@cygwin.com>
Subject: Re: cygrunsrv no longer allows domain user
Date: Tue, 31 Mar 2015 18:06:00 -0000	[thread overview]
Message-ID: <551AE0AE.5030701@intersystems.com> (raw)
In-Reply-To: <20150331100453.GD32403@calimero.vinschen.de>


On 03/31/2015 06:04 AM, Corinna Vinschen wrote:
> On Mar 30 14:07, Len Giambrone wrote:
>> This used to work (before Corinna's db work):
>>
>> $ cygrunsrv -I myservice -d 'myservice' -u 'ISCINTERNAL\build' -w donotuseme
>> -p /cygdrive/f/tut/install.sh
>> cygrunsrv: Error installing a service: CreateService:  Win32 error 1057:
>> The account name is invalid or does not exist, or the password is invalid
>> for the account name specified.
>>
>> Using + doesn't help either:
>>
>> $ cygrunsrv -I myservice -d 'myservice' -u 'ISCINTERNAL+build' -w donotuseme
>> -p /cygdrive/f/tut/install.sh
>> cygrunsrv: Error installing a service: CreateService:  Win32 error 1057:
>> The account name is invalid or does not exist, or the password is invalid
>> for the account name specified.
>>
>> Is there an incantation that will work?
> Uhm, not with Cygwin 1.7.35, unless your domain is the primary domain of
> your machine, in which case you just omit the leading domain:
>
>    cygrunsrv [...] -u 'build'
>
> This is a bug in Cygwin.  Cygrunsrv calls getpwnam("ISCINTERNAL\\build")
> and the underlying code fails to recognize this as invalid Cygwin user
> name.  Instead, it constructs a user entry for a user
> ISCINTERNAL+ISCINTERNAL\build and carries on.

Ok, so reading your patch, you just don't allow fully qualified 
usernames and return an error.  What if I have two users foo, one local 
to the machine, and one that is in the domain the machine is a member of?
How do I make the distinction?  Right now -u foo (by empirical evidence) 
translates to DOMAIN\foo; how to I specify LOCALMACHINE\foo?

> I fixed that in the repo and uploaded new developer snapshots 2015-03-31
> with this patch to https://cygwin.com/snapshots/.  Please give them a try.
>
>
> Thanks,
> Corinna
>

-- 
-Len

--
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:[~2015-03-31 18:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-30 18:20 Len Giambrone
2015-03-31 10:15 ` Corinna Vinschen
2015-03-31 18:06   ` Len Giambrone [this message]
2015-03-31 18:08     ` Len Giambrone

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=551AE0AE.5030701@intersystems.com \
    --to=leonard.giambrone@intersystems.com \
    --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).