[jboss-jira] [JBoss JIRA] (WFCORE-1388) jboss_init_redhat.sh needs to be more robust

Tomaz Cerar (JIRA) issues at jboss.org
Tue Feb 16 09:25:03 EST 2016


     [ https://issues.jboss.org/browse/WFCORE-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tomaz Cerar moved WFLY-1157 to WFCORE-1388:
-------------------------------------------

        Project: WildFly Core  (was: WildFly)
            Key: WFCORE-1388  (was: WFLY-1157)
    Component/s: Scripts
                     (was: Scripts)


> jboss_init_redhat.sh needs to be more robust
> --------------------------------------------
>
>                 Key: WFCORE-1388
>                 URL: https://issues.jboss.org/browse/WFCORE-1388
>             Project: WildFly Core
>          Issue Type: Feature Request
>          Components: Scripts
>            Reporter: Henrik Aronsen
>         Attachments: etc_default_jboss.txt, etc_init.d_jboss.txt
>
>
> I have tried to address the shortcomings of the current JBoss init script for RHEL5: 
> - Uses PID file 
> - Supports chkconfig 
> - Supports start, stop, force-stop, reload, force-reload, status 
> - Supports custom user and password on shutdown 
> - Supports custom jndi host/port on shutdown 
> - Does not allow second instance to start when one is already running 
> - Does not rely on other files such as run.sh and run.conf 
> - Verifies successful startup 
> - The init script does not have to be edited, use the standard location for configuration (/etc/default/jboss) instead 
> - Runs out of the box when no configuration is provided 
> - Should support most Linuces 
> All feedback is welcome -- I'm sure I forgot something in the provided script
> The init script is currently maintained at http://code.google.com/p/jboss-rpm/source/browse/#svn/trunk/src/main/etc
> (This issue was copied from JBPAPP-3194 as suggested by Fernando Nasser)



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


More information about the jboss-jira mailing list