[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: loginfo log messages
From: |
Ludvig Borgne |
Subject: |
RE: loginfo log messages |
Date: |
Wed, 12 Mar 2003 09:47:40 +0100 |
Daniel,
Why do you need the & at the end of the loginfo line?
I did a simple test with
DEFAULT cat
and it works, i.e. the log message is displayed in the shell
where i do the commit, but
DEFAULT cat&
does not work, i.e. nothing is displayed in the shell.
/Ludde
------------------------------------------------------------------------
Ludvig Borgne, Prover Technology AB, address@hidden, www.prover.com
> -----Original Message-----
> From: Grisinger, Daniel (MAN-Golden) [mailto:address@hidden
> Sent: Wednesday, March 12, 2003 00:35
> To: 'Larry Jones'
> Cc: 'address@hidden'
> Subject: RE: loginfo log messages
>
>
> Larry Jones <address@hidden> writes:
>
> > "Grisinger, Daniel (MAN-Golden)" writes:
> > >
> > > Larry Jones <address@hidden> writes:
> > > >
> > > > I think you've confused info-cvs with a perl list.
> > >
> > > Well, no, I haven't. The perl is correct, it simply reads
> > from STDIN. The
> > > problem is unquestionably a cvs issue. But since that's
> > the attitude here's
> > > the
> > > shell code that also doesn't work.
> >
> > Are you *sure* the perl is correct?
>
> Yes. Running it outside of CVS results in STDIN being echoed
> back out.
>
> > Have you checked to see if your script is executing at all?
>
> It is. The script mails a summary of changes out to the
> other developers on
> my team. This summary is complete except for the logmsg
> field. I'm getting
> the rest of the params (repository directory, file changed,
> old rev, new
> rev)
> passed through in ARGV. There just isn't anything on STDIN
> to read from
> (which
> is where I expected to find the data, based on the CVS manual).
>
> > What is the exact content of your $CVSROOT/CVSROOT/loginfo file?
>
> DEFAULT
> (/home/cvsuser/cvs-scripts/cvs-mail-checkin-notifications %{sVv} >>
> /home/cvsuser/cvslogs/commit-mailer.log 2>&1)&
>
> I've also tried:
>
> DEFAULT (sleep 3;
> /home/cvsuser/cvs-scripts/cvs-mail-checkin-notifications
> %{sVv} >> /home/cvsuser/cvslogs/commit-mailer.log 2>&1)&
>
> I removed the call to sleep(1), because I thought that maybe it was
> eating STDIN before my script could get at it. The current
> script sleeps
> for a bit to give CVS time to clear locks (since it calls cvs
> internally).
>
> There are no other entries in the loginfo file besides the
> DEFAULT. (If
> my company's dumb windows mail client wrapped that line, be
> assured that
> it actually appears as a single line in the loginfo file.)
>
> > What is the exact command you used for the commit and what
> was the exact
> output?
>
> $ cvs commit -m 'test commit' scrubber.c
> Checking in scrubber.c;
> /home/cvsuser/repository/is_devel/src/scrubsys/scrubber.c,v
> <-- scrubber.c
> new revision: 1.17; previous revision: 1.16
> done
> $
>
> Nothing is coming on STDIN, which is what I expected. I
> could always call
> cvs log from within the script and parse the latest log
> message out of it,
> but the manual suggests that I should be seeing the log
> message coming in
> on my standard input.
>
> Thanks.
>
> daniel
>
>
>
- loginfo log messages, Grisinger, Daniel (MAN-Golden), 2003/03/11
- RE: loginfo log messages, Grisinger, Daniel (MAN-Golden), 2003/03/11
- RE: loginfo log messages, Grisinger, Daniel (MAN-Golden), 2003/03/11
- Re: loginfo log messages, Dan Peterson, 2003/03/12
- Re: loginfo log messages, Gagneet Singh, 2003/03/12
- RE: loginfo log messages,
Ludvig Borgne <=
- RE: loginfo log messages, Grisinger, Daniel (MAN-Golden), 2003/03/12