Bug 875 – cvs ci does not always work on other then server

Bug 875 - cvs ci does not always work on other then server

Summary:	cvs ci does not always work on other then server

Status:	CLOSED WORKSFORME

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	cvs (Show other bugs)
Sub Component:
Version:	5.2
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	David Lawrence
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-01-19 00:54 EST by andrew.simmonds
Modified:	2008-05-01 11:37 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	1999-01-19 10:28:40 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description andrew.simmonds 1999-01-19 00:54:42 EST

We have a number of linux system and the cvs directories
are mounted from a server running linux.
If a checkin is done on a remote m/c sometimes it dosen't
work. I think it might have something to do with system
time but I'm not sure.

Comment 1 Jeff Johnson 1999-01-19 10:28:59 EST

FWIW, Red Hat routinely uses cvs to access remote repositories
using :pserver: or :ext: access without problems.

You should check:
1) both the client and server are running the same version of cvs.
2) the times between the client and server should be kept in sync
3) you should *not* try to access the remote cvs server using NFS.
The linux nfs server has some issues. Use :pserver: or :ext: access
instead -- both of theses types of remote access are faster.
4) I've also seen cvs have some difficulties checking out into
a nfs directory.

Please reopen this bug with more complete information on how to
reproduce your problem if the above suggestions do not help.

Note You need to log in before you can comment on or make changes to this bug.