[Top][All Lists]

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

RE: loginfo log messages

From: Grisinger, Daniel (MAN-Golden)
Subject: RE: loginfo log messages
Date: Wed, 12 Mar 2003 10:47:09 -0500

Dan Peterson writes:

> On Tue, 11 Mar 2003 address@hidden wrote:
> > On Tue, 11 Mar 2003 address@hidden wrote:
> >
> >> What is the exact content of your $CVSROOT/CVSROOT/loginfo file?
> >
> (/home/cvsuser/cvs-scripts/cvs-mail-checkin-notifications 
> %{sVv} >> /home/cvsuser/cvslogs/commit-mailer.log 2>&1)&
> I believe the reason you're not seeing anything on STDIN is 
> because you're
> putting the process in the background.  The data the CVS 
> server sends to
> STDIN is going to the parent of the background process, not 
> the background
> process itself.

That was it exactly.  The subshell was getting STDIN and not passing
it on to the script.  I took your suggestion for forking a child
and dissociating it from the parent and everything is good now.

> PPS. You should also be very cautious using the %{sVv} string 
> if any of your file/directory names contain spaces.

Oooooh, that hadn't occurred to me.  You're right, everything would break
I'm using spaces in the ARGV string as token seperators.  Fortunately, our
specs forbid files or dirs with embedded spaces, but it's still something to
pay attention to if the system barfs at some point in the future.

Thanks for your help (and thanks to everyone on the list who helped me
troubleshoot this, I appreciate it greatly).


reply via email to

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