Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
I double checked that my loginfo script does not hang. I have a loginfo file with a line that looks like this: DEFAULT $CVSROOT/CVSROOT/fix_loginfo.sh %s %V %v $CVSROOT and fix_loginfo.sh looks like this: #!/bin/bash (echo ""; id; echo $1 $2 $3; date) >> $4/CVSROOT/commitlog this essentially does the same thing as the old configuration (the one commented out in the default config that we used to use in 2.0.58d) and it works on the command line without fail. It also works when doing most cvs functions, logging to the commitlog and everything. It fails when I try to do a "cvs add" command on a folder. If I replace the loginfo file contents with something like: DEFAULT echo "test" I see the word "test" show up before a folder gets added. My questions are, what happens to %s %V and %v when a folder is added? Why is the loginfo script being called at all when folders aren't versioned? and lastly, can anyone post what they are using for their loginfo script so we can compare? Thanks! Brian "Bo Berglund" <Bo.Berglund at syst em3r.se> To <bwhicks at aep.com>, "Tony Hoyle" 10/12/2005 10:12 <tony.hoyle at march-hare.com> AM cc <cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook> Subject RE: Fw: [cvsnt] Re: CVSNT incompatibility with older servers -----Original Message----- From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org]On Behalf Of bwhicks at aep.com Sent: den 12 oktober 2005 14:41 To: Tony Hoyle Cc: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook Subject: Re: Fw: [cvsnt] Re: CVSNT incompatibility with older servers Anyone have any suggestions on this? Where should I start looking? Just to recap, if I put anything at all in the loginfo file, I can't do a cvs add of a directory. The add actually goes through the server properly, but the client hangs during the process (I used a couple of different clients and all exhibit the same behavior). This is no good from an end user standpoint. We have a fairly generic install, so I'm not sure where to begin with this. Help? Brian --------------------------------------- I checked the behaviour of cvs add in several different ways with or without embedded spaces in the directory and file names and I could not get it to show the symptoms you relay. I am now on 2115. Note that if you have a loginfo file thta contains nothing (everything is commented out) and it works, then you uncomment one line and it stops working, I would immediately suspect the uncommented line! You can be assured that the loginfo handling does work, but if the process that is started from loginfo hangs then so will cvs. /Bo