[cvsnt] Strange behaviour of cvs status on a VMWare server...
bo.berglund at telia.com
Thu Nov 2 06:05:29 GMT 2006
On Thu, 2 Nov 2006 07:22:21 +1100, "Brian Post" <bpost at 80-20.com>
>My point which I don't think you got, was I had no network problems running
>CVSNT on XP PRO SP2 with either VirtualPC or VMWARE. I was also pointing out
>that it may have been the transfer from real machine to VPC. We always build
>VMWare or VPC images using the CD.
>The reason we changed from VMWare to VPC was a company decision not mine.
>VMWare runs images faster than VPC on the same hardware IMHO.
>We also run 2003 server in Virtual PC, we also have 2003 VPC images running
>on a 2003 VPC server. I have never used CVSNT on 2003, only because the
>hardware I was running it on wasn't good enough (I.E Pentium III - 800 Mhz)
>Bo, It would be interresting to know if you put just CVSNT in a fresh
>installed 2003 server if it fixes your problems.
I asked the IT department for a freshly installed 2003 server in which
to install everything from the ground up. They have promised me this
ASAP. Let's see what happens after that.
If it fails I have to insist they return my old hardware.
Another thing I have not mentioned is that the CVSMailer system also
stopped working on this machine. It works properly up to the time it
is supposed to send the email out, then it gets a socket error 10054
(Connection reset by peer) after waiting for the socket timeout.
Strangely the IssueTracker we use (Roundup) is able to send emails so
I modified the CVSMailer configuration tool to include a mail test
button where it would use all of the CVSMailer email settings to send
a test message. There was no problem here either.
So my only explanation now is that somehow the CVSNT "problem" is
contagious also into an app that has been spawned by CVSNT like
CVSMailer, which runs off the loginfo call.
The plot thickens...
(Bo Berglund, developer in Sweden)
More information about the cvsnt