[jboss-jira] [JBoss JIRA] (AS7-4015) init.d script, +$JBOSS_OPTIONS, jboss-as/bin/init.d/jboss-as-standalone.sh tests for *executable* /etc/rc.d/init.d/functions

[Brian Stansberry (JIRA)]

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

Brian Stansberry updated AS7-4015:
----------------------------------

      Fix Version/s: 7.1.2.Final
                         (was: 7.1.1.Final)
    Forum Reference: https://community.jboss.org/thread/176251, https://community.jboss.org/wiki/StartJBossOnBootWithLinux  (was: https://community.jboss.org/thread/176251, https://community.jboss.org/wiki/StartJBossOnBootWithLinux)

    
> init.d script, +$JBOSS_OPTIONS, jboss-as/bin/init.d/jboss-as-standalone.sh  tests for *executable* /etc/rc.d/init.d/functions
> -----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AS7-4015
>                 URL: https://issues.jboss.org/browse/AS7-4015
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Documentation, Scripts
>    Affects Versions: 7.1.0.Final
>         Environment: CentOS 6.2 (netinstall, all default)
>            Reporter: Leo Breuss
>            Assignee: Brian Stansberry
>              Labels: script, startup
>             Fix For: 7.1.2.Final
>
>
> 1. The supplied jboss init script shall accept options for jboss. Proposal: $JBOSS_OPTIONS. This is usefull to hand over the binding. (My JBoss is in a VM on DHCP and I don't want to/can't bind to 0.0.0.0).
> 2. Bug: On CentOS 6 (and maybe other Distros too), the /etc/rc.d/init.d/functions has no executable flag set. The jboss init.d script itself sources it with  ". /etc/rc.d/init.d/functions"
> {code}
> ll /etc/rc.d/init.d/functions
> -rw-r--r--. 1 root root 18171 Oct  7 16:01 /etc/rc.d/init.d/functions
> {code}
> Proposed patch:
> {code:title=patch for $JBOSS_HOME/bin/init.d/jboss-as-standalone.sh|borderStyle=solid}
> # diff  /opt/jboss-as/bin/init.d/jboss-as-standalone.sh /etc/init.d/jboss
> 60c60
> <   if [ -x /etc/rc.d/init.d/functions ]; then
> ---
> >   if [ -r /etc/rc.d/init.d/functions ]; then
> 89,90c89,90
> <     if [ -x /etc/rc.d/init.d/functions ]; then
> <       daemon --user $JBOSS_USER LAUNCH_JBOSS_IN_BACKGROUND=1 JBOSS_PIDFILE=$JBOSS_PIDFILE $JBOSS_SCRIPT -c $JBOSS_CONFIG 2>&1 > $JBOSS_CONSOLE_LOG &
> ---
> >     if [ -r /etc/rc.d/init.d/functions ]; then
> >       daemon --user $JBOSS_USER LAUNCH_JBOSS_IN_BACKGROUND=1 JBOSS_PIDFILE=$JBOSS_PIDFILE $JBOSS_SCRIPT $JBOSS_OPTIONS -c $JBOSS_CONFIG 2>&1 > $JBOSS_CONSOLE_LOG &
> 92c92
> <       su - $JBOSS_USER -c "LAUNCH_JBOSS_IN_BACKGROUND=1 JBOSS_PIDFILE=$JBOSS_PIDFILE $JBOSS_SCRIPT -c $JBOSS_CONFIG" 2>&1 > $JBOSS_CONSOLE_LOG &
> ---
> >       su - $JBOSS_USER -c "LAUNCH_JBOSS_IN_BACKGROUND=1 JBOSS_PIDFILE=$JBOSS_PIDFILE $JBOSS_SCRIPT $JBOSS_OPTIONS -c $JBOSS_CONFIG" 2>&1 > $JBOSS_CONSOLE_LOG &
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira