10 More Discussions You Might Find Interesting
1. Proxy Server
Hi all,
We have been using Satellite to patch our RedHat servers for a while but up until recently these have only been virtual machines. Now we have a requirement to install a few physicals and I am trying to setup a sync a custom channel for the HP reository.
Our setup is that the... (2 Replies)
Discussion started by: wayned
2 Replies
2. Red Hat
Most of my commands are returning this error on RHEL 6 64 bit:
Also I tried installing many sofwtares, but it fails to correctly work. For example I treid installing dos2unix:
# rpm -ivh dos2unix-5.3.3-5.ram0.98.src.rpm
1:dos2unix warning: user mockbuild does not... (0 Replies)
Discussion started by: India_2014
0 Replies
3. Shell Programming and Scripting
Hi,
Below is my input file:
Long list of significant figure
1.757E-4
7.51E-3
5.634E-5
.
.
.
Desired output file:
0.0001757
0.00751
0.00005634
.
.
. (10 Replies)
Discussion started by: perl_beginner
10 Replies
4. Red Hat
Hi Friends,
I configured CVS Repository in RHEL 5.3 Server. But connecting the CVS Repository get the error like.
# cvs -d:pserver:cvs@localhost:/backup/cvs/cvsrep login
Logging in to :pserver:cvs@localhost:2401/backup/cvs/cvsrep
CVS password:
cvs : connect to :2401 failed: Connection... (0 Replies)
Discussion started by: srinivas814
0 Replies
5. UNIX for Dummies Questions & Answers
Hello,
Some of our application team uses Microsoft Team Foundation server (TFS) reposity tool for their .NET projects , I would like to access it form Unix/Linux machine. Please let me know how can access the TFS from unix.
Thanks (0 Replies)
Discussion started by: posix
0 Replies
6. Red Hat
Hello,
can someone please assist me userguide to setup simple Redhat yum Repository server with out using redhat satellite server. So all client will be pointing to this repository server to install rpm's.
Thanks, (3 Replies)
Discussion started by: bobby320
3 Replies
7. Programming
I have a coding project that I'm working on, and I'm tracking revisions using CVS. I'm working on a branch (branch1) at version 1.1.2.1.
Anyway, I created a new C file in the directory for the project, but I can't commit it. The tutorial I read on CVS said that version numbers will be assigned... (6 Replies)
Discussion started by: Ultrix
6 Replies
8. UNIX for Advanced & Expert Users
Hi all,
We have CVS server running for few years with absolutely no problems.
Because of conditions not depending on me, I'm forced to move some part of our repository to another server (SVN). I need to move ONLY one branch from CVS server to SVN server. The branch must be moved with all... (7 Replies)
Discussion started by: +Yan
7 Replies
9. Shell Programming and Scripting
Hi everyone..
Anybody having idea to get the latest file from CVS repository through schell scripts.
Thanks in advance.
Regards
shahid Bakshi (4 Replies)
Discussion started by: shahidbakshi
4 Replies
10. Solaris
dears
does any one know how can i take backup for reposirory in cvs ?? (9 Replies)
Discussion started by: murad.jaber
9 Replies
aecvsserver(1) aecvsserver(1)
NAME
aecvsserver - serve CVS client protocol against Aegis projects
SYNOPSIS
aecvsserver server
aecvsserver pserver
aecvsserver -VERSion
DESCRIPTION
The aecvsserver command is used to serve the CVS client protocol. The repository, of course, is stored within Aegis.
The server works by retrieving file contents from locations within Aegis change sets and repositories. When necessary, appropriate
aegis(1) commands are executed by the server to fulfill the requests.
This code is still experimental. At the present time only a limited number of CVS commands are understood. If you would like to extend
this code, contributions are welcome. The following commands are thought to work at this time: add, admin, checkout, commit, init,
remove, update.
server
To use the server, you will need to set the following environment variables:
CVSROOT=:ext:hostname/aegis
CVS_RSH=ssh
CVS_SERVER=aecvsserver
pserver
It is also possible to use aecvsserver as a cvs pserver, with all the usual caveats about how insecure this access method is, because it
transmits the password almost in the clear. The root and modules are as above.
MODULES
The CVS concept of modules is mapped onto Aegis concept of projects and changes. The special CVSROOT administrative module is simulated.
Projects as Modules
Each Aegis project appears to the CVS client as a module; the module's name is the same as the Aegis project's name. This type of module
isn't immediately useful except for the cvs export command, or to perform a read-only cvs checkout command.
You can't commit to a project-named module. This because Aegis requires all operations which would change the repository to be performed
through a change set.
It is theoretically possible to code aecvsserver to create a change (via aenc(1) and aedb(1) commands), then add the necessary files (via
aenf(1) and aecp(1) commands), then build (via the aeb(1) command), then test (via the aet(1) command), and finally to end development of
the change (via the aede(1) command). As the CVS protocol documentation says
"The protocol makes it possible for updates to be atomic with respect to checkins; that is, if someone commits changes to several
files in one cvs command, then an update by someone else would either get all the changes, or none of them. The current cvs
server can't do this, but that isn't the protocol's fault."
This code is yet to be written. Contributions welcome.
The protocol, however, doesn't make it particularly easy, either. The semantics of the Modify request change depending on whether it is
followed by the commit request or the update request.
Changes as Modules
Each Aegis change set also appears to the CVS client as a module; it's name is project.Cnumber. All cvs add commands, cvs remove com-
mands, cvs update commands and cvs commit commands are performed against the change set, not directly to the baseline. It is necessary
for the change set to already exist, and once you have run the cvs commit command, it will the be necessary to use the aede(1) command and
the rest of the usual Aegis process.
Once a change is no longer in the being developed state, it cannot be changed via aecvsserver(1) and you will need to create a new Aegis
change set, and then cvs checkout a new client-side work area.
Please note: if you are experimenting with the interface via cvs -d :fork:/aegis or similar, the work area you create must be outside the
Aegis change set's development directory.
CVSROOT
The CVSROOT module's contents are synthesized from Aegis meta-data. You can't add or modify files in this module; you need to administer
Aegis directly with aegis(1) commands.
EXIT STATUS
The aecvsserver command will exit with a status of 1 on any error. The aecvsserver command will only exit with a status of 0 if there are
no errors.
ENVIRONMENT VARIABLES
See aegis(1) for a list of environment variables which may affect this command. See aepconf(5) for the project configuration file's
project_specific field for how to set environment variables for all commands executed by Aegis.
COPYRIGHT
aecvsserver version 4.24.3.D001
Copyright (C) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010 Peter
Miller
The aecvsserver program comes with ABSOLUTELY NO WARRANTY; for details use the 'aecvsserver -VERSion License' command. This is free soft-
ware and you are welcome to redistribute it under certain conditions; for details use the 'aecvsserver -VERSion License' command.
AUTHOR
Peter Miller E-Mail: millerp@canb.auug.org.au
//* WWW: http://www.canb.auug.org.au/~millerp/
Reference Manual Aegis aecvsserver(1)