Re: cvs commit as root

[EMAIL PROTECTED] (Larry Jones) writes: [...] > root is just another user as far as file ownership goes. If a file is > owned by joe and readable only by the owner, then no one other than joe > can read it (except for root) just like no one other than root can read > a root-owned file that is

Re: cvs commit as root

[ On Monday, December 10, 2001 at 08:19:47 (-0800), Harry Putnam wrote: ] > Subject: Re: cvs commit as root > > Some things I don't put in cvs. /etc/passwd /etc/shadow are amongst > them. Those are not config files in some sense. And not likely to > need version control. I

Re: cvs commit as root

[ On Sunday, December 9, 2001 at 23:38:40 (-0500), Ralph A. Mack wrote: ] > Subject: Re: cvs commit as root > > On one front I agree with you: most shell script looks a bit like line > noise. :-) However, it can be learned with surprisingly little effort. > The base rules are

Re: cvs commit as root

"Ralph A. Mack" <[EMAIL PROTECTED]> writes: [...] > Keeping a layer of makefile/script between your source control system > and your deployment areas gives you a greater control of file system > attributes of deployed files. If you are concerned about security you > may want this layer in place,

Re: cvs commit as root

Harry Putnam writes: > > I haven't tried this yet but it looks like the thing that has been > missing. But at risk of seeming to pound this to death. Just at first > blush it seems this would mean that the files in /usr/local/cvsroot > would have to belong to `joe' or a group `joe' is part of.

Re: cvs commit as root

> Let me clear something up here. First off, I'm not debating the value > of your technique. Like I said, it is well beyond my level of > operation. > > Only descibed my home grown technique as strictly amatuer hour. Just > filled in a little to show how it actualy works. > > > For exam

Re: cvs commit as root

> Let me clear something up here. First off, I'm not debating the value > of your technique. Like I said, it is well beyond my level of operation. > > Only descibed my home grown technique as strictly amatuer hour. Just > filled in a little to show how it actualy works. > > > For example how wo

Re: cvs commit as root

[EMAIL PROTECTED] (Larry Jones) writes: > Harry Putnam writes: >> >> No, this connection is over ssh using CVS_RSH set to ssh and the ext >> syntax. Like: >> >>cvs -d :ext:HOST:/usr/local/cvsroot >> >> I don't actually use that syntax on the command line. I think it just >> happens becaus

Re: cvs commit as root

Harry Putnam writes: > > No, this connection is over ssh using CVS_RSH set to ssh and the ext > syntax. Like: > >cvs -d :ext:HOST:/usr/local/cvsroot > > I don't actually use that syntax on the command line. I think it just > happens because I have $CVSROOT set to the machine with the cvsro

Re: cvs commit as root

[EMAIL PROTECTED] (Greg A. Woods) writes: > [ On Saturday, December 8, 2001 at 07:19:10 (-0800), Harry Putnam wrote: ] >> Subject: Re: cvs commit as root >> >> Well, its not really true that it `isn't much different'. The copying >> step is really a ma

Re: cvs commit as root

[EMAIL PROTECTED] (Larry Jones) writes: > Harry Putnam writes: >> >> But cvs commit still results in: >> "/tmp/cvsc_ayxh" 8 lines, 296 characters >> cvs [server aborted]: cannot commit files as 'root' >> cvs commit: saving log message in /tmp/cvsd_ayxh > > What connection method are you u

Re: cvs commit as root

[ On Saturday, December 8, 2001 at 07:19:10 (-0800), Harry Putnam wrote: ] > Subject: Re: cvs commit as root > > Well, its not really true that it `isn't much different'. The copying > step is really a major pain in the butt. And represents aboutt 50% of > the work ne

Re: cvs commit as root

[EMAIL PROTECTED] (Greg A. Woods) writes: > In the simplest case you could just blindly copy all the files from your > working directory (or exported release) and be done with it, which > really isn't much different than what you've been trying to do, except > that now you have to edit them in a

Re: cvs commit as root

Harry Putnam writes: > > But cvs commit still results in: > "/tmp/cvsc_ayxh" 8 lines, 296 characters > cvs [server aborted]: cannot commit files as 'root' > cvs commit: saving log message in /tmp/cvsd_ayxh What connection method are you using? If you're using :pserver:, not having a -f g

Re: cvs commit as root

Harry Putnam writes: > > But I'm curious what you mean by `anonymous' root commits. Not sure I > know what that means. Because root is usually a shared account, you don't know who actually did the commit if you allow root commits -- they're essentially anonymous. > Also what problems are likel

Re: cvs commit as root

Harry Putnam writes: > > Is there cvs access to the development version? Yes -- see . You want either the command line or WinCVS instructions on that page. > I still hit a snag even when using --without-gssapi. Failing to find > libdiff.a. Tha

Re: cvs commit as root

Harry Putnam <[EMAIL PROTECTED]> writes: > [EMAIL PROTECTED] (Larry Jones) writes: [...] >> Yes, that's a configuration problem. I recommend you fix that rather >> than changing options.h to allow anonymous root commits. > > That turned out to be not such a big deal (the config problems I > me

Re: cvs commit as root

Harry Putnam <[EMAIL PROTECTED]> writes: > [EMAIL PROTECTED] (Larry Jones) writes: > >> Harry Putnam writes: >> > >>> server.c:31:21: krb5.h: No such file or directory >>> make[3]: *** [server.o] Error 1 >> >> That's a bug in the configure script that has been fixed in the current >> devel

Re: cvs commit as root

[EMAIL PROTECTED] (Larry Jones) writes: > Harry Putnam writes: > > >> server.c:31:21: krb5.h: No such file or directory >> make[3]: *** [server.o] Error 1 > > That's a bug in the configure script that has been fixed in the current > development version. Do "make distclean" to get rid of t

Re: cvs commit as root

[EMAIL PROTECTED] (Larry Jones) writes: > Harry Putnam writes: > > >> Yes, it works like you describe on my linux boxes. But on a solaris 8 >> (intel) I have problems with it. Probably more due to local config >> than anything else. Plain su root on the solaris box gives and root >> path is

Re: cvs commit as root

[ On Friday, December 7, 2001 at 11:13:14 (-0800), Harry Putnam wrote: ] > Subject: Re: cvs commit as root > > This sounds like a very smooth way to have it setup. However well > above my level of understanding of the needed proceedures. Definitely > something to look into... t

Re: cvs commit as root

Harry Putnam writes: > > Yes, it works like you describe on my linux boxes. But on a solaris 8 > (intel) I have problems with it. Probably more due to local config > than anything else. Plain su root on the solaris box gives and root > path is too short. Doesn't know about cvs binary. Yes,

Re: cvs commit as root

Harry Putnam writes: > > server.c:31:21: krb5.h: No such file or directory > make[3]: *** [server.o] Error 1 That's a bug in the configure script that has been fixed in the current development version. Do "make distclean" to get rid of the cached data and then run "configure --without-gss

Re: cvs commit as root

[EMAIL PROTECTED] (Greg A. Woods) writes: > [ On Thursday, December 6, 2001 at 22:17:21 (-0800), Harry Putnam wrote: ] > > Subject: cvs commit as root >> >> I'd like to override the taboo on committing as root. I imagine it is >> possible but not clear how to do

Re: cvs commit as root

[EMAIL PROTECTED] (Larry Jones) writes: > Harry Putnam writes: >> >> I'd like to override the taboo on committing as root. I imagine it is >> possible but not clear how to do it. > > You're only not allowed to commit as root if CVS can't figure out who

Re: cvs commit as root

[EMAIL PROTECTED] (Larry Jones) writes: > Harry Putnam writes: > > >> I'd like to override the taboo on committing as root. I imagine it is >> possible but not clear how to do it. > > You're only not allowed to commit as root if CVS can't figure out w

Re: cvs commit as root

[ On Thursday, December 6, 2001 at 22:17:21 (-0800), Harry Putnam wrote: ] > Subject: cvs commit as root > > I'd like to override the taboo on committing as root. I imagine it is > possible but not clear how to do it. It is possible, but you don't want to do it. > On my

Re: cvs commit as root

Harry Putnam writes: > > I'd like to override the taboo on committing as root. I imagine it is > possible but not clear how to do it. You're only not allowed to commit as root if CVS can't figure out who you really are. As long as you login as yourself and then su to r

cvs commit as root

inux. Only the actual files ownership/permissions. However, cvs doesn't want me to commit as root. So even when committing non root owned files (as user), I run into errors if any root owned files are scanned or need to be committed. Errors crop up in updating and committing. Maybe other

Re: commit as root.

> Hello everybody! > I have a question. I need to work as root in a specific project. (I would try to find another solution, frankly) > But, when I > try to commit the modified files, I get a message telling that commit cannot > be done as root. Are you using the :ext: protocol, or direct f

commit as root.

Hello everybody! I have a question. I need to work as root in a specific project. But, when I try to commit the modified files, I get a message telling that commit cannot be done as root. I am using the motor IDE. Does anybody know a way to commit the changes as root? Thanks very much. __

Re: answer to query regarding problems using commit as root

[ On Thursday, June 28, 2001 at 04:57:33 (-0700), pavan kumar korlepara wrote: ] > Subject: answer to query regarding problems using commit as root > > its there that cvs doesnot allow you to commit files > as root. but if u still want to do ur development work > as root, what

Re: answer to query regarding problems using commit as root

6:57 AM Subject: answer to query regarding problems using commit as root > its there that cvs doesnot allow you to commit files > as root. but if u still want to do ur development work > as root, whatever may be the reasons, i dont see any > problems, if its ok with the user. linux users are

answer to query regarding problems using commit as root

its there that cvs doesnot allow you to commit files as root. but if u still want to do ur development work as root, whatever may be the reasons, i dont see any problems, if its ok with the user. linux users are free to do whatever they want and however they like. thatz the beauty of it. so if u l

Re: Can't commit as root

cvs will not let you commit as root. If you would like to change this you will need to compile cvs with CVS_BADROOT not defined( in options.h). donald On Tue, May 29, 2001 at 01:56:36PM +0200, Dominik Vogt wrote: > I want to manage the config files on our server in CVS. The CVS > ser

Re: Can't commit as root

Dominik Vogt wrote: > When I try to commit anything into > cvs as the root user, I simply get this message: > > cvs [server aborted]: cannot commit files as 'root' > > What can I do about this (yes, the root user is in the cvs group)? > cvs won't let yo

Can't commit as root

I want to manage the config files on our server in CVS. The CVS server is already up and running (access rights are given by putting users in the 'cvs' group). Everything works fine except that I can't use CVS as root. When I try to commit anything into cvs as the root user, I simply get this m

Re: how do i commit as root

[EMAIL PROTECTED] wrote: > I want to put all our dns files in cvs. however when i try to commit > as root i get the error. > > cvs [commit aborted]: cannot commit files as 'root' > > this is somewhat irritating since the commit is part of a larger > script t

how do i commit as root

I want to put all our dns files in cvs. however when i try to commit as root i get the error. cvs [commit aborted]: cannot commit files as 'root' this is somewhat irritating since the commit is part of a larger script that does dns integrity checking, automatic updating of the

Re: Why can commit as root ?

[EMAIL PROTECTED] writes: > > cvs [server aborted]: cannot commit files as 'root' See src/options.h: /* * When committing a permanent change, CVS and RCS make a log entry of * who committed the change. If you are committing the change logged * in as "root" (not under "su" or other root-priv

Why can commit as root ?

Dear friend: cvs commit -m ¥[¤J¥Ó¸Ë¬yµ{ªí®æmodule descriptions (in directory D:\nmweb\CVSROOT\) cvs [server aborted]: cannot commit files as 'root' *CVS exited normally with code 1* and the file permission is : -rwxrwxr-- 1 root other101 Sep 18 13:44 descriptions So why

Re: Cannot commit as root

[ On Saturday, April 8, 2000 at 12:48:59 (+0200), Eivind Eklund wrote: ] > Subject: Re: Cannot commit as root > > Seriously: There are cases where using CVS as root makes very good > sense. For instance, at my employer, there are basically four roles > we have for machines wh

Re: Cannot commit as root

On Sat, Apr 08, 2000 at 12:48 +0200, Eivind Eklund wrote: > On Mon, Apr 03, 2000 at 07:13:44PM +0200, Gerhard Sittig wrote: > > [ ... cvs refuses to act on root's behalf ... ] > > There's something wrong in your enterprise. Go and read some > > basic doc about how to deal with priviledges! And

Re: Cannot commit as root

commit then changes to the server? If I am a normal > > > user ... no problem, but if I'm root => error: cannot commit as > > > root. > > > > There's something wrong in your enterprise. Go and read some > > basic doc about how to deal wit

Re: Cannot commit as root

ver? If I am a normal > > user ... no problem, but if I'm root => error: cannot commit as > > root. This is a bug in older versions of CVS (pre 1.10, I think, but I'm not really sure when the patch for it was integrated. It lingered a while after I submitted it.

Re: Cannot commit as root

>I think there might be a legitimate reason to commit files as root. I'm >in the middle of attempting to put my system configuration files (this >/etc/*) into CVS. These files are owned by root, managed by root, etc. >but I'd still like to have a root-only repository that will allow me to >make ch

Re: Cannot commit as root

Derek Scherger wrote: > I think there might be a legitimate reason to commit files as root. I'm > in the middle of attempting to put my system configuration files (this > /etc/*) into CVS. These files are owned by root, managed by root, etc. > but I'd still like to have a root-only repository tha

Re: Cannot commit as root

On Wednesday, April 5, Derek Scherger wrote: > > I think there might be a legitimate reason to commit files as root. I'm > in the middle of attempting to put my system configuration files (this > /etc/*) into CVS. These files are owned by root, managed by root, etc. > but I'd still like to have a

Re: Cannot commit as root

ser ... no problem, but if I'm root => error: cannot commit as > > root. > > There's something wrong in your enterprise. Go and read some > basic doc about how to deal with priviledges! And don't tell > your other team members to ask the same question, pl

Re: Cannot commit as root

On Tue, Apr 04, 2000 at 13:50 +0300, Marius Oancea wrote: > Hello cvs expoerts, > If I want to use cvs from my workstation ( and here I am root ) > how can I commit then changes to the server? If I am a normal > user ... no problem, but if I'm root => err

Re: Cannot commit as root

On Tuesday 4 April 2000, at 13 h 50, the keyboard of Marius Oancea <[EMAIL PROTECTED]> wrote: [Why two identical requests from sec.sibnet.ro?] > If I want to use cvs from my workstation ( and here I am root ) You shouldn't.

Cannot commit as root

Hello cvs expoerts, If I want to use cvs from my workstation ( and here I am root ) how can I commit then changes to the server? If I am a normal user ... no problem, but if I'm root => error: cannot commit as root. -- Best regards,