Re: Using eval vs. exec in shell scripts

On 26.06.2011 17:59, bradleymccrorey wrote: > > > Rainer Jung-3 wrote: >> >>> >>> You can clearly see here that there are two processes: one for the shell >>> script, and one for the actual java process. Is this not what I should be >>> seeing? >> >> You should, bot only when using "run", which i

Re: Using eval vs. exec in shell scripts

I'm trying to achieve? Sorry if I'm being thick-headed, and thanks very much for your consideration. -- View this message in context: http://old.nabble.com/Using-eval-vs.-exec-in-shell-scripts-tp31884910p31931669.html Sent from the Tomcat - Dev mailing list archive at Nabble.co

Re: Using eval vs. exec in shell scripts

On 26.06.2011 17:35, bradleymccrorey wrote: > > > Rainer Jung-3 wrote: >> >> >> Did you follow the later messages in this discusison thread? >> >> I made an error in not including all quotes use din catalina.sh in my >> simpl test script. So when using the correct scripts, the eval did *not* >> l

Re: Using eval vs. exec in shell scripts

643 0.0 0.2 4000 660 pts/0S+ 10:50 0:00 grep > catalina > You can clearly see here that there are two processes: one for the shell script, and one for the actual java process. Is this not what I should be seein

Re: Using eval vs. exec in shell scripts

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 catalina.sh pr

Re: Using eval vs. exec in shell scripts

> didn't work with the exec based scripts? > > Regards, > > Rainer > > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > > > -- V

Re: Using eval vs. exec in shell scripts

On 20.06.2011 15:59, Mladen Turk wrote: > On 06/20/2011 03:12 PM, Rainer Jung wrote: >> >>> ... and >>> We eval for start/stop so we can get the pid. >> >> And this is broken now. We used $! with exec and we still use it with >> eval. But with eval $! returns the pid of a child shell and the java >

Re: Using eval vs. exec in shell scripts

On 06/20/2011 03:12 PM, Rainer Jung wrote: ... and We eval for start/stop so we can get the pid. And this is broken now. We used $! with exec and we still use it with eval. But with eval $! returns the pid of a child shell and the java process id a child of that pid. Are you sure? cat

Re: Using eval vs. exec in shell scripts

On 20.06.2011 14:52, Mladen Turk wrote: > On 06/20/2011 01:39 PM, Rainer Jung 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

Re: Using eval vs. exec in shell scripts

On 06/20/2011 01:39 PM, Rainer Jung 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" Mladen or whoever else understood this: can

Re: Using eval vs. exec in shell scripts

Which script ? Could you send us the svn link ? 2011/6/20 Rainer Jung : > 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" > > Ev

Using eval vs. exec in shell scripts

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