; [EMAIL PROTECTED]
Subject: Re: Lock files in version 1.11.11
Zanabria, Moises writes:
I built the binary in Linux 2.4.18 using gcc version 2.96 2731 (Red
Hat
Linux 7.1 2.96-98) and also I compiled the source using SETXID_SUPPORT.
As far as I know, no one ever tests SETXID_SUPPORT. I
.
-- Mark
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 14, 2004 4:35 PM
To: Zanabria, Moises
Cc: [EMAIL PROTECTED]; Zanabria, Moises; [EMAIL PROTECTED]
Subject: Re: Lock files in version 1.11.11
Zanabria, Moises writes:
I
Zanabria, Moises writes:
I got several directories on /tmp/cvs-serv
Do I need to look for something in specific?
Files with core in their names. The most likely possibilities are
core, cvs.core, and core.cvs. Then you need to use a debugger
(e.g., gdb) to analyze the core file(s)
PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: Lock files in version 1.11.11
Zanabria, Moises writes:
I got several directories on /tmp/cvs-serv
Do I need to look for something in specific?
Files with core in their names. The most likely possibilities
I had the same issue with 1.11.11 (and 1.11.10). Please see links
to previous posts that is attached.
Thanks,
Mark
--- Mark D. Baushke [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Zanabria, Moises [EMAIL PROTECTED] writes:
Guys,
I'm trying to figure out
/bin/cvs
Did you notice if /tmp/cvsnwyJm4 was populated at all?
not at all, I've the file.
Thanks.
Moises.
-Original Message-
From: Mark D. Baushke [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 14, 2004 1:51 AM
To: Zanabria, Moises
Cc: '[EMAIL PROTECTED]'
Subject: Re: Lock files
PROTECTED]'
Subject: RE: Lock files in version 1.11.11
I build the binary in Linux 2.4.18 using gcc version 2.96 2731 (Red Hat
Linux 7.1 2.96-98) and also I compiled the source using SETXID_SUPPORT.
top/Makefile
CC = gcc -DSETXID_SUPPORT
top/src/Makefile
CC = gcc -DSETXID_SUPPORT
-rwxr-sr-x1
Zanabria, Moises writes:
I've just searched in all system and there is not a core file..
When running client/server, the core file will be in the server's temp
directory (usually /tmp/cvs-servn).
-Larry Jones
What a stupid world. -- Calvin
Zanabria, Moises writes:
I build the binary in Linux 2.4.18 using gcc version 2.96 2731 (Red Hat
Linux 7.1 2.96-98) and also I compiled the source using SETXID_SUPPORT.
As far as I know, no one ever tests SETXID_SUPPORT. I wonder if that's
the root of the problem?
-Larry Jones
From now
:35 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: Lock files in version 1.11.11
Zanabria, Moises writes:
I build the binary in Linux 2.4.18 using gcc version 2.96 2731 (Red
Hat
Linux 7.1 2.96-98) and also I compiled the source using
]'
Subject: RE: Lock files in version 1.11.11
I build the binary in Linux 2.4.18 using gcc version 2.96 2731 (Red Hat
Linux 7.1 2.96-98) and also I compiled the source using SETXID_SUPPORT.
top/Makefile
CC = gcc -DSETXID_SUPPORT
top/src/Makefile
CC = gcc -DSETXID_SUPPORT
-rwxr-sr
]
Subject: Re: Lock files in version 1.11.11
Zanabria, Moises writes:
I've just searched in all system and there is not a core file..
When running client/server, the core file will be in the server's temp
directory (usually /tmp/cvs-servn).
-Larry Jones
What a stupid world. -- Calvin
Guys,
I'm trying to figure out what's what my problem is, since I upgraded my cvs
binary I'm getting a bunch of cvs lock files and those are leaving in the
repository.
My last cvs server version was 1.11.5 and I've just upgrade to the latest,
in the past I was working with CVS 1.11.5 in the
13 matches
Mail list logo
