info-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: enabling log.pl


From: Parvinder Singh Arora
Subject: Re: enabling log.pl
Date: Fri, 11 Feb 2005 10:10:24 -0500

ALL (echo ""; date; cat) | \/usr/local/cvsroot/CVSROOT/log -u $USER -s
\-m address@hidden

I think what above stuff is doing is sending the date and the log
message (cat) to the log.pl perl script. Dont i need to add 'cat'
there to send the entire cvs message to log.pl ?

BTW i figured out what was wrong. I was not passing the the log file
using -f option which is why it use kick me saying could not open ():
no such file or directory. I think it is mandatory to pass the log
file using -f option

Thanks
~Parvinder



On Fri, 11 Feb 2005 09:30:04 -0500, Todd Denniston
<address@hidden> wrote:
> Parvinder Singh Arora wrote:
> >
> > This is what is the entry in my loginfo file
> >
> > ALL (echo ""; date; cat) | \
> > /usr/local/cvsroot/CVSROOT/log -u $USER -s \
> > -m address@hidden
> >
> 
> [ED. I broke the lines above with "\"s to make it clear this is expected to
> be one line in the file]
> 
> What is it you intended the `(echo ""; date; cat)` to do?
> I tried:
> (echo ""; date; cat) |less
> and found it annoying in an interactive environment, as cat does not exit.
> `(echo ""; date)` might be useful, though.
> 
> also I am assuming that in your loginfo, the line you sent is all on ONE
> line.
> 
> > And when i try to do some commit this is what i get :(
> >
> > address@hidden CVSROOT]$ cvs commit temp.txt
> > Checking in temp.txt;
> > /usr/local/cvsroot/CVSROOT/temp.txt,v  <--  temp.txt
> > new revision: 1.10; previous revision: 1.9
> > done
> > Could not open(): No such file or directory
> > sh: line 1: : command not found
> > cvs server: Rebuilding administrative file database
> >
> > ~Parvinder
> Is the /usr/local/cvsroot/CVSROOT/log script your own or one of the ones on
> the net? (a net one we might be able to look at the source and guess what is
> going wrong.)
> Just from the name difference in your subject and here, I would expect the
> problem might be that sh is trying to interpret a perl script and failing.
> You might check the first line of /usr/local/cvsroot/CVSROOT/log and verify
> the first line is of the type "#! /something/bin/perl", if it is then verify
> that /something/bin/perl will execute (or change it to point to the real
> perl on your system).
> 
> --
> Todd Denniston
> Crane Division, Naval Surface Warfare Center (NSWC Crane)
> Harnessing the Power of Technology for the Warfighter
> 


-- 
Thanks & Regards
~Parvinder




reply via email to

[Prev in Thread] Current Thread [Next in Thread]