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
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 is precisely meant to not
> decouple the console from t
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
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*
> leave a copy of the shel process hanging around.
>
I
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
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 process, which leaves the child java process still runni
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
>
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
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
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
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
11 matches
Mail list logo