[p4] Re: perforce-user digest, Vol 1 #354 - 1 msg

[Anton Rang]

>From: Matthew Rice <matt at starnix.com>
>Subject: Re: [p4] Server creating users?
>Date: Sat, 14 Oct 2000 09:25:18 -0400 (EDT)
>
>> Yet we are getting new users created without superuser intervention.
>
>A user doesn't need superuser priviledges to create a user for himself.
>They get created automagically when a new P4USER (or their login name)
>starts using Perforce.  Until you run out of licenses, at least :)

It's worth noting that you can disable this behavior using 'p4 protect'...
see page 30 of the system administrator's guide.  Handy if you've got a
limited license pool.

-- Anton

--
This is an unauthorized communication.  "The statements and opinions
expressed herein are my own and do not necessarily represent those of
Adaptec."



Received: from MAILSERVER2.chennai.tcs.co.in ([203.197.158.132])
	by frankenrouter.perforce.com (8.9.3/8.9.1) with SMTP id WAA38154
	for <perforce-user at perforce.com>; Fri, 13 Oct 2000 22:45:39 -0700 (PDT)
Received: by MAILSERVER2.chennai.tcs.co.in(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256978.001F7F5B ; Sat, 14 Oct 2000 11:14:02 +0530
X-Lotus-FromDomain: TCSCHENNAI
From: "Shruti Dutta" <"shruti_dutta"@chennai.tcs.co.in>
To: perforce-user at perforce.com
Message-ID: <65256978.001F7EA9.00 at MAILSERVER2.chennai.tcs.co.in>
Date: Sat, 14 Oct 2000 11:16:45 +0530
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Subject: [p4] Configuration management
Sender: perforce-user-admin at perforce.com
Errors-To: perforce-user-admin at perforce.com
X-BeenThere: perforce-user at perforce.com
X-Mailman-Version: 2.0beta2
Precedence: bulk
List-Id: Discuss Perforce with other users <perforce-user.perforce.com>


Hi

I must pick an SCM tool in a short amount of time, and have
heard lot about versioning tools and less about configuration tools.

In our project we are generating source code and creating object
files at OMVS UNIX and creating load modules at MVS.
There will be three (build/test/production) environments which we will need to
confgure.

I would like to know does Perforce's tools support both versioning and
configurtion
management on MVS/OMVS and Solaris.

Regards
Shruti



Received: from starship.beopen.com (IDENT:qmailr at starship.python.net [208.185.174.112])
	by frankenrouter.perforce.com (8.9.3/8.9.1) with SMTP id LAA46325
	for <perforce-user at perforce.com>; Sun, 15 Oct 2000 11:30:02 -0700 (PDT)
Received: (qmail 23199 invoked by uid 1253); 15 Oct 2000 18:30:11 -0000
Received: from localhost (sendmail-bs at 127.0.0.1)
  by localhost with SMTP; 15 Oct 2000 18:30:11 -0000
Date: Sun, 15 Oct 2000 11:30:11 -0700 (PDT)
From: Tom Bryan <tbryan at starship.beopen.com>
To: "Schaible, Joerg" <Joerg.Schaible at gft.de>
cc: Slootweg Paul <Paul.Slootweg at barclaycard.co.uk>,
        "'Perforce User (E-mail)'" <perforce-user at perforce.com>
Subject: RE: [p4] Server creating users?
In-Reply-To: <C2D7D58DBFE9D111B0480060086E96350266D5B3 at mail.gft.de>
Message-ID: <Pine.LNX.4.21.0010151125100.23166-100000 at starship.beopen.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: perforce-user-admin at perforce.com
Errors-To: perforce-user-admin at perforce.com
X-BeenThere: perforce-user at perforce.com
X-Mailman-Version: 2.0beta2
Precedence: bulk
List-Id: Discuss Perforce with other users <perforce-user.perforce.com>

On Fri, 13 Oct 2000, Schaible, Joerg wrote:

> > Our server appears to create users of it's own accord (or 
> > prhaps it's an
> > application using the SCC DLL).
> > 
> > We have P4 protections set - only one superuser.
> > 
> > Yet we are getting new users created without superuser intervention.
> 
> the P4Win client tries to create a user if it is not already registered. It
> succeeds if your normal users are able to write at "//...". To supress this
> nobody should be able to write to this location except the administrators.
> We've setup an administrator group using protections like:
> 
> read group company * //...
> write group project1 * //project1/...
> write group project2 * //project2/...
> super group admins * //...
> 
> Since a new user is not member of the admins group, the P4Win client is not
> able to create one.

Note that this prevents P4Win from creating a user, but P4Win will still
sometimes try to use SmithJ as the P4USER and fail.  You may want to
explicitly "Set default user" or edit the user's environment (or is it the
Registry?) to make sure that it always uses smithj.  

The protections advice above will prevent the user creation from
succeeding.  Explicitly setting the default user in the user's environment
will prevent the user from ever having problems with the new policy.

---Tom