=?ISO-8859-2?Q?Ziegler_G=E1bor?= writes:
>
> cvs checkout -P 31um (in directory D:\POPO)
> cvs server: cannot open /root/.cvsignore: Permission denied
> cvs [server aborted]: can't chdir(/root): Permission denied
This is probably the most frequently asked question here -- at least
three times in the last week. The short summary is that you need to add
a -f global option to the command in inetd.conf if it isn't there
already, and you may have to work around a bug in the Linux version of
inetd that causes $HOME to be set. Please see the mailing list archives
at ftp://ftp-mailing-list-archives.gnu.org/ or http://www.egroups.com/
for more details.
> Anyway, my repository is owned by 'cvsuser', I plan to enforce a
> policy to use this username for cvs for all participants in my
> project, so can I run the server as 'cvsuser' instead of root? I have
> tried it, but in this case the server has not even allowed me to log
> in:
> cvs [login aborted]: authorization failed: server <host> rejected
> access
This is a very bad idea -- having everyone use the same username means
that you won't be able to tell who did what! I strongly suggest giving
each user a unique username and then using CVSROOT/passwd to map them
all to the same system user (cvsuser) if that's what you want to do. In
either case, you can indeed run the server as cvsuser.
> I do not have CVSROOT/config, should I? If so, where it is
> documented? I have neither found such admin-file described in the
> Cederqvist manual, nor in the manpage.
If you've set up your repository correctly (i.e., by running cvs init),
you'd have a CVSROOT/config, but it would just contain comments. You
don't need one, but not having one makes me wonder how you set up your
repository and what other administrative files you may be missing. It's
documented in the Cederqvist manual in the section titled (strangely
enough) "The CVSROOT/config configuration file".
> > > cvspserver 2401/udp # CVS client/server operations
> > CVS doesn't use UDP, so you should probably remove that line.
> I did'nt make that, it was inserted by someone else, probably by the
> Debian cvs package's config script. OK, I has disabled, it didn't
> help.
It won't cause any problems, but it's not necessary and there's no point
in cluttering up /etc/services with bogus entries.
-Larry Jones
In a minute, you and I are going to settle this out of doors. -- Calvin
