tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rainer Jung <>
Subject Re: Using eval vs. exec in shell scripts
Date Sun, 26 Jun 2011 08:58:37 GMT
On 26.06.2011 01:45, bradleymccrorey wrote:
> I'll be watching this quite closely. We run thousands of TC6 instances onsite
> here, and are a daemontools shop. This change breaks daemontools, as the
> "svc" command will attempt to stop the tomcat service by sending a TERM to
> the process, which leaves the child java process still running.
> For one customer who insists on TC7, I've had to take the measure of
> changing the script to use the old method for now. This is not
> maintainable, however. Should there be a bug filed somewhere for this?
> Cheers,
> Bradley McCrorey

Did you follow the later messages in this discusison thread?

I made an error in not including all quotes use din in my
simpl test script. So when using the correct scripts, the eval did *not*
leave a copy of the shel process hanging around.

If you think there is a problem, you can discuss the technical details
here, and if the list doesn't find a solution for you, you can open a bug.



> Rainer Jung-3 wrote:
>> Since Mladens change r918873 in March 2010 we use eval instead of exec
>> in the shell scripts. The svn log says:
>> "Use eval instead direct call or exec command so that arguments with
>> spaces are properly handled"
>> Eval leaves a copy of the shell process hanging around until Tomcat
>> shutdown. I want to experiment with different solutions, but have no
>> idea, what kind of whitespace use the switch from exec to eval was
>> supposed to change.
>> Mladen or whoever else understood this: can you give an example which
>> didn't work with the exec based scripts?
>> Regards,
>> Rainer

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message