Re: Can the admin command be disabled?

[Mark]

There are a couple of reasons. Nothing critical or major.

We only have one group for cvs. That group owns the repository and no one
except the CVS admin account and CVS pserver account is in that group. We have
setup pserver to run as a non-root acount. Preventing admin command access via
pserver  would be trivial, just have to pick any other group and put it into
options.h (since the pserver account is only in the repository group)

But there are other things we may like to do. Maybe CM wants to manage imports
of 3rd party sources, thus disabling the import command would help. Maybe we
want all tag operations in the history file, so we may want to diable tag
command usage and sue rtag. Maybe we decide that export isn't a command we want
developers using since CM does all builds and migrations and developers might
start editing exported checkouts and then asking for help putting changes in
CVS. Maybe we want to enforce readonly checkouts, so we set watch on the whole
project and don't want developers using the watch command to turn it off (yes I
know that would prevent individual watches and options, maybe we don't want or
need that functionality).

We could have between 30-80 individual separate projects using CVS in the next
2 years. just looking into help with management and consitancy amoung projects
for our sanity and easing of support. Just exploring options.

I know its a hack, I was hoping that being able to disable certain command line
options would be rather simple and low risk. Like I said, nothing critical or
major, it would just be nice to know how to hack cvs so it will no recognize a
command as a valid. If I remember correctly, I thought I was able to do this a
few years ago.

Thanks,

Mark

--- Larry Jones <larry.jones@sdrc.com> wrote:
> Mark writes:
> > 
> > Forget the admin command (should have seen that response comming) How can
> the
> > import command be disabled in pserver, so cvs does not recognize it as a
> valid
> > command?
> 
> There are no facilities for disabling individual commands.  If you
> inisist on doing so, you'll have to hack the code and you're on your
> own.  Perhaps if you explain *why* you want to disable certain commands
> we can come up with a better way to accomplish your goals.
> 
> -Larry Jones
> 
> Well of course the zipper's going to get stuck if everyone
> stands around WATCHING me! -- Calvin
> 
> _______________________________________________
> Bug-cvs mailing list
> Bug-cvs@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-cvs


__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail
http://personal.mail.yahoo.com/