[Cvsnt] Anyone using cvsntupd?

[Edward Gemar]

	The problem was that the CVS folder hadn't been correctly added
to the system PATH so it couldn't find the cvs executable.  I was able
to debug the problem by piping standard error to a log.  To do this in
DOS, you use the following syntax c:\>(Your Command) 2>mylogfile.txt
Note the '2' to pipe standard error.
	Once I solved my problem I noticed a few limitations with
CVSNTUpd as it stands.  If you create and commit a directory and pass
the module name to CVSNTUpd in loginfo, this will fail because it will
attempt to CD to the new directory which doesn't exist yet (the perl
script shipped with CVSNTUpd handles the correctly however).  Also,
directories with spaces can also cause problems.  Lastly, both CVSNTUpd
and the update_websites create a long concatenated command line to be
run by the scheduler.  If this command exceeds 259 characters (which it
easily can with a reasonable deep directory path) the task will fail.
	I found that easiest thing to do was use a modified version of
the update_websites script that has an added check for spaces in the
module name and just schedules a call to another script file (that
actually does the CD and calls CVS)  This solves the problem of creating
a command line that's too long.
	Thanks to John Peacock for writing this because being new to CVS
I wouldn't have a clue as what to do and now our intranet is perfectly
synced with cvs.  Way cool!
	BTW, if anyone is interested in the tweaks I made let me know.

	Edward

Edward Gemar
ForwardVue Technologies, Inc.
Austin, TX
Vox: 512-482-5126
Fax: 512-651-3209


-----Original Message-----
From: cvsnt-admin at cvsnt.org [mailto:cvsnt-admin at cvsnt.org] On Behalf Of
Jens Scheidtmann
Sent: Wednesday, January 30, 2002 2:09 AM
To: cvsnt at cvsnt.org
Subject: Re: [Cvsnt] Anyone using cvsntupd?



Edward Gemar wrote:
>
> John,
>         Thanks for the help.  I think it may be a permission problem.
> I've tried both cvsntupd.exe and update_websites.pl with the same
> results.  The commands that cvsntupd and the perl script generate are
> correct and run fine when I enter them from the command line, but when
> run via cvsntupd or the perl script all I get is an empty log file and
> the task finishes with an errorlevel of 1.  Is there any good way to
> debug a scheduled task?  It would be nice to see the output of the
> command interpreter to get a better idea of what could be going wrong
> here.  Piping to a log won't catch that.  Any ideas?

You can try to use www.sysinternals.com's "DebugView". It captures
various output to windows output functions. I am not sure wether it will
capture output from a scheduled task, but you might want to give it a
try.

Jens Scheidtmann

--
Universität des Saarlandes
Technische Chemie
Jens Scheidtmann
Am Markt Zeile 3
66125 Saarbrücken-Dudweiler
Tel.: + 49 681 302 64139
Fax.: + 49 681 302 2343
_______________________________________________
Cvsnt mailing list
Cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt

_______________________________________________
Cvsnt mailing list
Cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt