[p4] Restrict use of p4 user command

[Ines Heinz]

Yep!  I sent the messages shortly before receiving the next
messages that referred me to the tech notes.  I hadn't noticed
that behaviour until it was pointed out to me.  I then looked
and noted that the behaviour works for us.  We evidently have
had it in place for quite a while.  

Do you know of a way to prevent users from deleting branch
specifications?

Ines

Robert Cowham wrote:
> 
> Hack not necessary to delete unknown users - see other messages and Tech Note!
> 
> Robert
> 
> > -----Original Message-----
> > From: perforce-user-admin at perforce.com
> > [mailto:perforce-user-admin at perforce.com]On Behalf Of Ines Heinz
> > Sent: 27 January 2000 16:24
> > To: Steve Cook
> > Cc: 'perforce-user at perforce.com'
> > Subject: Re: [p4] Restrict use of p4 user command
> >
> >
> > While this wouldn't prevent users from adding new users, you
> > could write a script that would delete all unknown users from
> > the database.  The demon would wake up every so often, query
> > p4 for a list of users, and delete any users not on the
> > accepted list.  The other way to do it is to add fake usernames
> > so that you are "using" all your licenses.  Then p4 will tell
> > the person trying to add a user that all user licenses are
> > in use and they can't access the db.
> >
> > Yeah, they're hacks, but there isn't any good way via perforce
> > to do it.  The other annoyance I have is that any user can
> > delete a branch specification.  Granted, this doesn't delete
> > the branch.  However, it causes problems for my users when
> > they try to integrate using the -b option.
> >
> > Ines
> >
> > Steve Cook wrote:
> > >
> > > Is there any way to prevent users from adding new users?  Although I have
> > > defined all the users already, occasionally a user will run p4win in NT with
> > > a slightly different userid and somehow end up creating a new user.  As a
> > > result the same person is listed more than once as a user with slight
> > > variations in spelling or capitalization in user name.
> > >
> > > It would be nice to be able to use p4 protect to restrict a group's access
> > > to a specific command.
> > >
> > > Any ideas?
> > >
> > > Stephen A. Cook
> > > Release Engineering
> > >
> > > CyberGuard Corporation
> > > scook at cyberguard.com
> > > Office: (954) 958-3900 x3238
> > > Cell phone: (561) 901-3070
> > >
> > > _______________________________________________
> > > perforce-user mailing list  -  perforce-user at perforce.com
> > > http://maillist.perforce.com/mailman/listinfo/perforce-user
> >
> >
> > _______________________________________________
> > perforce-user mailing list  -  perforce-user at perforce.com
> > http://maillist.perforce.com/mailman/listinfo/perforce-user