[
https://issues.apache.org/jira/browse/GERONIMO-5997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13046946#comment-13046946
]
Kevan Miller commented on GERONIMO-5997:
----------------------------------------
Hi Leonardo, thanks for the info. So, your geronimo_old.sh file looks like it
was generated by the gserviceReg.sh command. See
https://cwiki.apache.org/GMOxDOC22/running-geronimo-as-a-linux-service.html for
more information. I assume you or someone else ran './gserviceReg add geronimo'
(or similar) to generate a geronimo service. The resulting service script file
would look like your geronimo_old.sh.
gserviceReg.sh was not designed to create a service script which supported the
'jpda' option. I suppose it could, but I'm not sure it's a common use case...
If somebody feels it would be valuable, speak up...
So, if you use the 'geronimo.sh' script that's included in a geronimo download,
I believe you have the function you're looking for.
> Missing commands for startup
> ----------------------------
>
> Key: GERONIMO-5997
> URL: https://issues.apache.org/jira/browse/GERONIMO-5997
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: commands, Jetty, startup/shutdown
> Affects Versions: 2.2
> Environment: Debian linux/squeeze
> Java 1.6 v19 sun
> Reporter: Leonardo Bueno Postacchini
> Attachments: geronimo.sh, geronimo_old.sh
>
>
> Documentations instructs launching geronimo with:
> geronimo jpda run
> or
> geronimo jpda start
> for remote debugging but attempting to do that result in message:
> Usage: geronimo {start|stop|restart|status}
> Edit: Change jpda -> jdpa
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
