04-24-2008
I'm not too familiar with tcpwrappers. I suggest you to start with the tcpd manpage, and look into the files /etc/hosts.allow and /etc/hosts.deny.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I am trying to write a Perl script to cover a few CVS commands (setup specifically), however the VI screen that pops up and requests a comment, what is the best way of entering the text automatically (will be a variable name) and then saving that cvs notification from my Perl program?
Help is... (2 Replies)
Discussion started by: Shakey21
2 Replies
2. UNIX for Advanced & Expert Users
Hi
As a System Admin, I have to handle synchronzing 2 CVS.
But I'm new to CVS & hardly have any knowledge of such tools.
Please help me, is there any way, that can automatize the
process for synchronizing the 2 remotely residing CVS database
with out manual intervension.
Ex:- CVA... (1 Reply)
Discussion started by: S.Vishwanath
1 Replies
3. UNIX for Dummies Questions & Answers
Hey guys,
I am trying to setup CVS to run with an SSH connection, but am hitting a brick wall. I seem to be getting CVS to login correctly, but when I attempt to check out a module I am getting the following error:
ksh: cvs: not found
This is kinda implying to me that its not loading... (2 Replies)
Discussion started by: LiquidChild
2 Replies
4. UNIX for Advanced & Expert Users
I've experienced a problem with CVS when I've checked out sh script.
When new build was created sources were checked out from CVS under Windows. Later this build was deployed under Linux und I recieved error from shell becouse of CR-LF EOL in file. I've tryed command dos2unix and become script... (7 Replies)
Discussion started by: Hitori
7 Replies
5. Solaris
dear all
I'm one of the CVS administrators here at my company
and i have this cvs error in the messages
Sep 18 07:20:37 dev cvs: Dying gasps received from client.
can any one help me about this error .............
thanks
murad jaber (1 Reply)
Discussion started by: murad.jaber
1 Replies
6. Debian
Hi everyone...
Could one of you kind Linux experts please let me know what CVS is
In return I will kindly give you a thumbs up :b: a good trade I feel!! (1 Reply)
Discussion started by: TonyChapman
1 Replies
7. Red Hat
Hello,
I have read a great deal of documentation on CVS and I hope I have not overlooked what I need but I have certain issues with CVS that I cannnot resolve.
The setup for the /etx/xinetd.d file I have is as follows:
# default: off
# description: The CVS service can record the history... (2 Replies)
Discussion started by: mojoman
2 Replies
8. AIX
Hello. I am using CVS on my AIX 6.1 box. I have gotten the repository setup and everything is working from command line. Now I want to use CVS on my Windows 7 machine using the remote repository on my AIX box. Has anyone else tried this? Why can't I get this to work?
I have tried using... (3 Replies)
Discussion started by: hpodhrad
3 Replies
9. UNIX for Advanced & Expert Users
Hi,
I am having a text file with the following contents
###########
File1
###########
some
page1.txt
text
page.txt
When I sort this file on Red Hat 5, then I get the following output
###########
File1
###########
page1.txt
page.txt
some (3 Replies)
Discussion started by: sarbjit
3 Replies
10. UNIX for Advanced & Expert Users
Hi,
I am having a strange issue with CVS. The output shows that there is not enough space for the .cvspass.
the .cvspass is in the users home dir, which has 4GB available.
Error Message:
cvs status: cannot read /home/<user>/.cvspass: Not enough space
cvs status: authorization... (6 Replies)
Discussion started by: techy1
6 Replies
LEARN ABOUT DEBIAN
cvssuck
CVSSUCK(1) General Commands Manual CVSSUCK(1)
NAME
cvssuck - inefficient cvs repository grabber using cvs command
SYNOPSIS
cvssuck [-h] [-b] [-s] [-v] [-D debug-option,...] cvsroot [-o output-directory|-O output-base] [-l lock-directory|-L lock-base] module ...
DESCRIPTION
CVSsuck is a mirroring tool for cvs repositories. Unlike other tools such as CVSup or rsync, it uses cvs command to access the repository.
So, it works well with remote repositories without a special server or shell account. However it is inefficient and not perfect because
cvs client/server protocol is not designed for mirroring. If a server provides special way to grab a repository, you shouldn't use CVS-
suck.
OPTIONS
-h prints help message.
-b makes CVSsuck to traverse directories in breadth first. CVSsuck traverses directory in depth first by default.
-s specifies skeleton mode. In this mode, CVSsuck grabs only first revision of the trunk, 1.1, branchpoints, head of branches and
tagged revisions. Note that first two (first revision of the trunk and 1.1) is identical in usual case.
-v makes CVSsuck verbosely. This is same as `-D command,attic,leavetmp'.
-D debug-option,...
specifies debug options. Available debug options are listed by `cvssuck -h'.
-o output-directory
specifies the directory to store grabbed repository. A remote RCS file module/dir/file,v in cvsroot will be stored in output-direc-
tory/dir/file,v.
-O output-base
specifies the base directory to store grabbed repository. A remote RCS file module/dir/file,v in cvsroot will be stored in output-
base/module/dir/file,v. -o and -O is exclusive. The last specified before module is effective. By default, CVSsuck behaves as
that current directory is specified with -O.
-l lock-directory
specifies the directory of CVS style lock.
-L lock-base
specifies the base directory of CVS style lock. -l and -L is exclusive. A lock directory should be specified after an output
directory. The last specified before module after an output directory is effective. By default, CVSsuck assumes a lock directory
is same as output directory.
EXAMPLES
% cvssuck :pserver:anonymous@cvs.m17n.org:/cvs/cvs cvssuck
grabs the module cvssuck in the repository :pserver:anonymous@cvs.m17n.org:/cvs/cvs into the directory cvssuck.
% cvssuck :pserver:anonymous@cvs.m17n.org:/cvs/cvs cvssuck cvs-info
grabs the modules cvssuck and cvs-info.
% cvssuck :pserver:anonymous@cvs.m17n.org:/cvs/cvs -O $HOME/.cvsroot cvssuck
grabs the module cvssuck into $HOME/.cvsroot/cvssuck.
% cvssuck :pserver:anonymous@cvs.m17n.org:/cvs/cvs -O $HOME/.cvsroot -L $HOME/.cvslock cvssuck
grabs the module cvssuck into $HOME/.cvsroot/cvssuck with the lock directory $HOME/.cvslock/cvssuck.
% cvssuck :pserver:anonymous@cvs.m17n.org:/cvs/cvs -o $HOME/.cvsroot/cvs/suck cvssuck
grabs the module cvssuck into $HOME/.cvsroot/cvs/suck.
% cvssuck -s :pserver:anonymous@cvs.m17n.org:/cvs/cvs cvssuck
grabs needy revisions (skeleton) of the module cvssuck.
SEE ALSO
http://cvs.m17n.org/~akr/cvssuck/
cvs(1), rcs(1), cvsup(1), rsync(1)
AUTHORS
Tanaka Akira <akr@m17n.org>.
BUGS
It's inefficient.
It's not perfect because revisions stated as `dead' cannot be retrieved. However it is not observable until the state is changed by `cvs
admin -s'.
25 September 2000 CVSSUCK(1)