public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin's CVS - can it be a network server?
Date: Tue, 21 Aug 2001 23:02:00 -0000	[thread overview]
Message-ID: <20010822080244.F17561@cygbert.vinschen.de> (raw)
In-Reply-To: <8BFEC206D292D311921500508B0BCB8D0883DE9B@msgstl01.sbc.com>

On Tue, Aug 21, 2001 at 06:50:01PM -0500, ASH, JAMES (SBCSI) wrote:
> I believe I have answered my own question. The answer is, yes, it can run as
> a remote server.
> 
> I am running the cvs 1.11 from the cygwin distribution on an NT box and am
> able to access it from the AIX box I am using, as well as from other NT
> boxes with cygwin installed. I write this in case someone else can benefit
> from this.
> 
> I still have an issue. I am able to do this if:
> 1) I run the inetd on the server as 'Administrator'
> 2) I login from the remote cvs client to the cvs pserver as 'Administrator'.
> 
> This account is setup on the NT server as an NT user with no password via
> NT's User Manager.
> 
> The inetd is currently not running with ntsec.
> 
> If I try to connect as anything but 'Administrator', I get the message
> setuid failed:not owner. (I created a new NT account and attempted to
> connect using that account, having setup the appropriate pserver passwd,
> etc...)
> 
> In all cases, if the inetd is running under the same account as the cvs
> account I have created, all works fine.
> 
> My question is this: What is "setuid failed: Not owner" trying to tell me?
> Which process is trying to accomplish a setuid? Is it the inetd or the cvs
> pserver?

It's cvs. Inetd never changes user context. setuid failed since
you have to use ntsec and you have to care for your /etc/passwd
and /etc/group files to switch user context.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
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:[~2001-08-21 23:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-21 16:50 ASH, JAMES (SBCSI)
2001-08-21 23:02 ` Corinna Vinschen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-08-18 11:47 ASH, JAMES (SBCSI)
2001-08-18 13:08 ` Corinna Vinschen
2001-08-21  2:19   ` David Starks-Browning
2001-08-21  9:42     ` Warren Young
2001-08-21 10:16       ` Christopher Faylor
2001-08-21 12:48         ` Warren Young
2001-08-21 14:52           ` Robert Collins
     [not found] <997833795.4654.ezmlm@sources.redhat.com>
2001-08-15  4:55 ` Reini Urban
     [not found] <200108141640.MAA03457@smtpsrv1.isis.unc.edu>
2001-08-14 13:13 ` Jochen Küpper
2001-08-13 12:40 James L. Ash
2001-08-13 12:44 ` Charles Wilson
2001-08-14  7:39   ` T.Phan
2001-08-14  9:24     ` Charles Wilson
2001-08-14  9:37       ` Mark Paulus

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=20010822080244.F17561@cygbert.vinschen.de \
    --to=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).