You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Felipe Leme (JIRA)" <ji...@codehaus.org> on 2006/04/12 15:35:48 UTC

[jira] Created: (CONTINUUM-655) Add chkconfig support to the starting script

Add chkconfig support to the starting script
--------------------------------------------

         Key: CONTINUUM-655
         URL: http://jira.codehaus.org/browse/CONTINUUM-655
     Project: Continuum
        Type: Improvement

  Components: Core system  
    Versions: 1.0.2    
 Environment: Fedora Core & any RedHat-based system
    Reporter: Felipe Leme


I'm using Fedora Core 4 and wanted to start Continuum on startup, so I followed the instructions below:

http://maven.apache.org/continuum/guides/mini/guide-linux-boot.html

FC (and any RH-based distro) doesn't have the update-rc.d script; instead, they have chkconfig. So, I created the link on /etc/rc.d and tried to enable continuum on chkconfig, but it failed:

[root@localhost init.d]# chkconfig --add continuum
service continuum does not support chkconfig

Looking at the shell script, it's missing the chkconfig commentaries, so I added them:

#! /bin/sh


# chkconfig: 345 20 80
# description: Maven Continuum server

Now everything is fine:

[root@localhost init.d]# chkconfig --add continuum

[root@localhost init.d]# chkconfig continuum on
[root@localhost init.d]# service continuum start
Starting continuum...


I could provide a patch, but I don't know how the script is generated. So, long story short, this issue requires 2 changes:

-  add the comment above in the run.sh script (or whatever generates it)
- update the documentation (URL above)



-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Commented: (CONTINUUM-655) Add chkconfig support to the starting script

Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/CONTINUUM-655?page=comments#action_63403 ] 

Emmanuel Venisse commented on CONTINUUM-655:
--------------------------------------------

you don't have JAVA_HOME in your path when the script start

> Add chkconfig support to the starting script
> --------------------------------------------
>
>          Key: CONTINUUM-655
>          URL: http://jira.codehaus.org/browse/CONTINUUM-655
>      Project: Continuum
>         Type: Improvement

>   Components: Core system
>     Versions: 1.0.2
>  Environment: Fedora Core & any RedHat-based system
>     Reporter: Felipe Leme

>
> Original Estimate: 15 minutes
>         Remaining: 15 minutes
>
> I'm using Fedora Core 4 and wanted to start Continuum on startup, so I followed the instructions below:
> http://maven.apache.org/continuum/guides/mini/guide-linux-boot.html
> FC (and any RH-based distro) doesn't have the update-rc.d script; instead, they have chkconfig. So, I created the link on /etc/rc.d and tried to enable continuum on chkconfig, but it failed:
> [root@localhost init.d]# chkconfig --add continuum
> service continuum does not support chkconfig
> Looking at the shell script, it's missing the chkconfig commentaries, so I added them:
> #! /bin/sh
> # chkconfig: 345 20 80
> # description: Maven Continuum server
> Now everything is fine:
> [root@localhost init.d]# chkconfig --add continuum
> [root@localhost init.d]# chkconfig continuum on
> [root@localhost init.d]# service continuum start
> Starting continuum...
> I could provide a patch, but I don't know how the script is generated. So, long story short, this issue requires 2 changes:
> -  add the comment above in the run.sh script (or whatever generates it)
> - update the documentation (URL above)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Updated: (CONTINUUM-655) Add chkconfig support to the starting script

Posted by "Felipe Leme (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/CONTINUUM-655?page=all ]

Felipe Leme updated CONTINUUM-655:
----------------------------------

    Attachment: chkconfig_install.sh

> Add chkconfig support to the starting script
> --------------------------------------------
>
>          Key: CONTINUUM-655
>          URL: http://jira.codehaus.org/browse/CONTINUUM-655
>      Project: Continuum
>         Type: Improvement

>   Components: Core system
>     Versions: 1.0.2
>  Environment: Fedora Core & any RedHat-based system
>     Reporter: Felipe Leme
>  Attachments: CONTINUUM-655.patch, chkconfig_install.sh
>
> Original Estimate: 15 minutes
>         Remaining: 15 minutes
>
> I'm using Fedora Core 4 and wanted to start Continuum on startup, so I followed the instructions below:
> http://maven.apache.org/continuum/guides/mini/guide-linux-boot.html
> FC (and any RH-based distro) doesn't have the update-rc.d script; instead, they have chkconfig. So, I created the link on /etc/rc.d and tried to enable continuum on chkconfig, but it failed:
> [root@localhost init.d]# chkconfig --add continuum
> service continuum does not support chkconfig
> Looking at the shell script, it's missing the chkconfig commentaries, so I added them:
> #! /bin/sh
> # chkconfig: 345 20 80
> # description: Maven Continuum server
> Now everything is fine:
> [root@localhost init.d]# chkconfig --add continuum
> [root@localhost init.d]# chkconfig continuum on
> [root@localhost init.d]# service continuum start
> Starting continuum...
> I could provide a patch, but I don't know how the script is generated. So, long story short, this issue requires 2 changes:
> -  add the comment above in the run.sh script (or whatever generates it)
> - update the documentation (URL above)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Updated: (CONTINUUM-655) Add chkconfig support to the starting script

Posted by "Felipe Leme (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/CONTINUUM-655?page=all ]

Felipe Leme updated CONTINUUM-655:
----------------------------------

    Attachment: chkconfig_install.sh

> Add chkconfig support to the starting script
> --------------------------------------------
>
>          Key: CONTINUUM-655
>          URL: http://jira.codehaus.org/browse/CONTINUUM-655
>      Project: Continuum
>         Type: Improvement

>   Components: Core system
>     Versions: 1.0.2
>  Environment: Fedora Core & any RedHat-based system
>     Reporter: Felipe Leme
>  Attachments: chkconfig_install.sh
>
> Original Estimate: 15 minutes
>         Remaining: 15 minutes
>
> I'm using Fedora Core 4 and wanted to start Continuum on startup, so I followed the instructions below:
> http://maven.apache.org/continuum/guides/mini/guide-linux-boot.html
> FC (and any RH-based distro) doesn't have the update-rc.d script; instead, they have chkconfig. So, I created the link on /etc/rc.d and tried to enable continuum on chkconfig, but it failed:
> [root@localhost init.d]# chkconfig --add continuum
> service continuum does not support chkconfig
> Looking at the shell script, it's missing the chkconfig commentaries, so I added them:
> #! /bin/sh
> # chkconfig: 345 20 80
> # description: Maven Continuum server
> Now everything is fine:
> [root@localhost init.d]# chkconfig --add continuum
> [root@localhost init.d]# chkconfig continuum on
> [root@localhost init.d]# service continuum start
> Starting continuum...
> I could provide a patch, but I don't know how the script is generated. So, long story short, this issue requires 2 changes:
> -  add the comment above in the run.sh script (or whatever generates it)
> - update the documentation (URL above)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Commented: (CONTINUUM-655) Add chkconfig support to the starting script

Posted by "Felipe Leme (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/CONTINUUM-655?page=comments#action_63388 ] 

Felipe Leme commented on CONTINUUM-655:
---------------------------------------

How "nice": Jira thinks # is a numbering system! Let me try again...

Line 1:
# chkconfig: 345 20 80

Line 2:
# description: Maven Continuum server





> Add chkconfig support to the starting script
> --------------------------------------------
>
>          Key: CONTINUUM-655
>          URL: http://jira.codehaus.org/browse/CONTINUUM-655
>      Project: Continuum
>         Type: Improvement

>   Components: Core system
>     Versions: 1.0.2
>  Environment: Fedora Core & any RedHat-based system
>     Reporter: Felipe Leme

>
> Original Estimate: 15 minutes
>         Remaining: 15 minutes
>
> I'm using Fedora Core 4 and wanted to start Continuum on startup, so I followed the instructions below:
> http://maven.apache.org/continuum/guides/mini/guide-linux-boot.html
> FC (and any RH-based distro) doesn't have the update-rc.d script; instead, they have chkconfig. So, I created the link on /etc/rc.d and tried to enable continuum on chkconfig, but it failed:
> [root@localhost init.d]# chkconfig --add continuum
> service continuum does not support chkconfig
> Looking at the shell script, it's missing the chkconfig commentaries, so I added them:
> #! /bin/sh
> # chkconfig: 345 20 80
> # description: Maven Continuum server
> Now everything is fine:
> [root@localhost init.d]# chkconfig --add continuum
> [root@localhost init.d]# chkconfig continuum on
> [root@localhost init.d]# service continuum start
> Starting continuum...
> I could provide a patch, but I don't know how the script is generated. So, long story short, this issue requires 2 changes:
> -  add the comment above in the run.sh script (or whatever generates it)
> - update the documentation (URL above)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Updated: (CONTINUUM-655) Add chkconfig support to the starting script

Posted by "Felipe Leme (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/CONTINUUM-655?page=all ]

Felipe Leme updated CONTINUUM-655:
----------------------------------

    Attachment:     (was: chkconfig_install.sh)

> Add chkconfig support to the starting script
> --------------------------------------------
>
>          Key: CONTINUUM-655
>          URL: http://jira.codehaus.org/browse/CONTINUUM-655
>      Project: Continuum
>         Type: Improvement

>   Components: Core system
>     Versions: 1.0.2
>  Environment: Fedora Core & any RedHat-based system
>     Reporter: Felipe Leme
>  Attachments: CONTINUUM-655.patch
>
> Original Estimate: 15 minutes
>         Remaining: 15 minutes
>
> I'm using Fedora Core 4 and wanted to start Continuum on startup, so I followed the instructions below:
> http://maven.apache.org/continuum/guides/mini/guide-linux-boot.html
> FC (and any RH-based distro) doesn't have the update-rc.d script; instead, they have chkconfig. So, I created the link on /etc/rc.d and tried to enable continuum on chkconfig, but it failed:
> [root@localhost init.d]# chkconfig --add continuum
> service continuum does not support chkconfig
> Looking at the shell script, it's missing the chkconfig commentaries, so I added them:
> #! /bin/sh
> # chkconfig: 345 20 80
> # description: Maven Continuum server
> Now everything is fine:
> [root@localhost init.d]# chkconfig --add continuum
> [root@localhost init.d]# chkconfig continuum on
> [root@localhost init.d]# service continuum start
> Starting continuum...
> I could provide a patch, but I don't know how the script is generated. So, long story short, this issue requires 2 changes:
> -  add the comment above in the run.sh script (or whatever generates it)
> - update the documentation (URL above)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Commented: (CONTINUUM-655) Add chkconfig support to the starting script

Posted by "Felipe Leme (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/CONTINUUM-655?page=comments#action_63402 ] 

Felipe Leme commented on CONTINUUM-655:
---------------------------------------

Got the problem: my system didn't have JAVA_HOME properly set for the service scripts. So, the proposed change should be enough (I will try to fix my system to confirm though...)

> Add chkconfig support to the starting script
> --------------------------------------------
>
>          Key: CONTINUUM-655
>          URL: http://jira.codehaus.org/browse/CONTINUUM-655
>      Project: Continuum
>         Type: Improvement

>   Components: Core system
>     Versions: 1.0.2
>  Environment: Fedora Core & any RedHat-based system
>     Reporter: Felipe Leme

>
> Original Estimate: 15 minutes
>         Remaining: 15 minutes
>
> I'm using Fedora Core 4 and wanted to start Continuum on startup, so I followed the instructions below:
> http://maven.apache.org/continuum/guides/mini/guide-linux-boot.html
> FC (and any RH-based distro) doesn't have the update-rc.d script; instead, they have chkconfig. So, I created the link on /etc/rc.d and tried to enable continuum on chkconfig, but it failed:
> [root@localhost init.d]# chkconfig --add continuum
> service continuum does not support chkconfig
> Looking at the shell script, it's missing the chkconfig commentaries, so I added them:
> #! /bin/sh
> # chkconfig: 345 20 80
> # description: Maven Continuum server
> Now everything is fine:
> [root@localhost init.d]# chkconfig --add continuum
> [root@localhost init.d]# chkconfig continuum on
> [root@localhost init.d]# service continuum start
> Starting continuum...
> I could provide a patch, but I don't know how the script is generated. So, long story short, this issue requires 2 changes:
> -  add the comment above in the run.sh script (or whatever generates it)
> - update the documentation (URL above)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Updated: (CONTINUUM-655) Add chkconfig support to the starting script

Posted by "Felipe Leme (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/CONTINUUM-655?page=all ]

Felipe Leme updated CONTINUUM-655:
----------------------------------

    Attachment: chkconfig_install.sh

> Add chkconfig support to the starting script
> --------------------------------------------
>
>          Key: CONTINUUM-655
>          URL: http://jira.codehaus.org/browse/CONTINUUM-655
>      Project: Continuum
>         Type: Improvement

>   Components: Core system
>     Versions: 1.0.2
>  Environment: Fedora Core & any RedHat-based system
>     Reporter: Felipe Leme
>  Attachments: chkconfig_install.sh
>
> Original Estimate: 15 minutes
>         Remaining: 15 minutes
>
> I'm using Fedora Core 4 and wanted to start Continuum on startup, so I followed the instructions below:
> http://maven.apache.org/continuum/guides/mini/guide-linux-boot.html
> FC (and any RH-based distro) doesn't have the update-rc.d script; instead, they have chkconfig. So, I created the link on /etc/rc.d and tried to enable continuum on chkconfig, but it failed:
> [root@localhost init.d]# chkconfig --add continuum
> service continuum does not support chkconfig
> Looking at the shell script, it's missing the chkconfig commentaries, so I added them:
> #! /bin/sh
> # chkconfig: 345 20 80
> # description: Maven Continuum server
> Now everything is fine:
> [root@localhost init.d]# chkconfig --add continuum
> [root@localhost init.d]# chkconfig continuum on
> [root@localhost init.d]# service continuum start
> Starting continuum...
> I could provide a patch, but I don't know how the script is generated. So, long story short, this issue requires 2 changes:
> -  add the comment above in the run.sh script (or whatever generates it)
> - update the documentation (URL above)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Closed: (CONTINUUM-655) Add chkconfig support to the starting script

Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/CONTINUUM-655?page=all ]
     
Emmanuel Venisse closed CONTINUUM-655:
--------------------------------------

      Assign To: Emmanuel Venisse
     Resolution: Fixed
    Fix Version: 1.0.3

Applied. Thanks

> Add chkconfig support to the starting script
> --------------------------------------------
>
>          Key: CONTINUUM-655
>          URL: http://jira.codehaus.org/browse/CONTINUUM-655
>      Project: Continuum
>         Type: Improvement

>   Components: Core system
>     Versions: 1.0.2
>  Environment: Fedora Core & any RedHat-based system
>     Reporter: Felipe Leme
>     Assignee: Emmanuel Venisse
>      Fix For: 1.0.3
>  Attachments: CONTINUUM-655.patch, chkconfig_install.sh
>
> Original Estimate: 15 minutes
>         Remaining: 15 minutes
>
> I'm using Fedora Core 4 and wanted to start Continuum on startup, so I followed the instructions below:
> http://maven.apache.org/continuum/guides/mini/guide-linux-boot.html
> FC (and any RH-based distro) doesn't have the update-rc.d script; instead, they have chkconfig. So, I created the link on /etc/rc.d and tried to enable continuum on chkconfig, but it failed:
> [root@localhost init.d]# chkconfig --add continuum
> service continuum does not support chkconfig
> Looking at the shell script, it's missing the chkconfig commentaries, so I added them:
> #! /bin/sh
> # chkconfig: 345 20 80
> # description: Maven Continuum server
> Now everything is fine:
> [root@localhost init.d]# chkconfig --add continuum
> [root@localhost init.d]# chkconfig continuum on
> [root@localhost init.d]# service continuum start
> Starting continuum...
> I could provide a patch, but I don't know how the script is generated. So, long story short, this issue requires 2 changes:
> -  add the comment above in the run.sh script (or whatever generates it)
> - update the documentation (URL above)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Commented: (CONTINUUM-655) Add chkconfig support to the starting script

Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/CONTINUUM-655?page=comments#action_63391 ] 

Emmanuel Venisse commented on CONTINUUM-655:
--------------------------------------------

The shell script is generated by plexus-runtime-builder, but i don't want to modify it now because all generated run.sh will have the same chkconfig/description
But you can provide a patch for the documentation.

> Add chkconfig support to the starting script
> --------------------------------------------
>
>          Key: CONTINUUM-655
>          URL: http://jira.codehaus.org/browse/CONTINUUM-655
>      Project: Continuum
>         Type: Improvement

>   Components: Core system
>     Versions: 1.0.2
>  Environment: Fedora Core & any RedHat-based system
>     Reporter: Felipe Leme

>
> Original Estimate: 15 minutes
>         Remaining: 15 minutes
>
> I'm using Fedora Core 4 and wanted to start Continuum on startup, so I followed the instructions below:
> http://maven.apache.org/continuum/guides/mini/guide-linux-boot.html
> FC (and any RH-based distro) doesn't have the update-rc.d script; instead, they have chkconfig. So, I created the link on /etc/rc.d and tried to enable continuum on chkconfig, but it failed:
> [root@localhost init.d]# chkconfig --add continuum
> service continuum does not support chkconfig
> Looking at the shell script, it's missing the chkconfig commentaries, so I added them:
> #! /bin/sh
> # chkconfig: 345 20 80
> # description: Maven Continuum server
> Now everything is fine:
> [root@localhost init.d]# chkconfig --add continuum
> [root@localhost init.d]# chkconfig continuum on
> [root@localhost init.d]# service continuum start
> Starting continuum...
> I could provide a patch, but I don't know how the script is generated. So, long story short, this issue requires 2 changes:
> -  add the comment above in the run.sh script (or whatever generates it)
> - update the documentation (URL above)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Commented: (CONTINUUM-655) Add chkconfig support to the starting script

Posted by "Felipe Leme (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/CONTINUUM-655?page=comments#action_63397 ] 

Felipe Leme commented on CONTINUUM-655:
---------------------------------------

Actually, it's not so simple; just now I realized it doesn't work :-(

It does call the script, but the wrapper fails:

STATUS | wrapper  | 2006/04/12 12:36:25 | --> Wrapper Started as Daemon
STATUS | wrapper  | 2006/04/12 12:36:25 | Launching a JVM...
ERROR  | wrapper  | 2006/04/12 12:36:25 | Unable to start JVM: No such file or directory (2)ERROR  | wrapper  | 2006/04/12 12:36:25 | Critical error: wait for JVM process failed (No child processes)
ERROR  | wrapper  | 2006/04/12 12:36:25 | Unable to start a JVM
STATUS | wrapper  | 2006/04/12 12:36:25 | <-- Wrapper Stopped

I will investigate why...


> Add chkconfig support to the starting script
> --------------------------------------------
>
>          Key: CONTINUUM-655
>          URL: http://jira.codehaus.org/browse/CONTINUUM-655
>      Project: Continuum
>         Type: Improvement

>   Components: Core system
>     Versions: 1.0.2
>  Environment: Fedora Core & any RedHat-based system
>     Reporter: Felipe Leme

>
> Original Estimate: 15 minutes
>         Remaining: 15 minutes
>
> I'm using Fedora Core 4 and wanted to start Continuum on startup, so I followed the instructions below:
> http://maven.apache.org/continuum/guides/mini/guide-linux-boot.html
> FC (and any RH-based distro) doesn't have the update-rc.d script; instead, they have chkconfig. So, I created the link on /etc/rc.d and tried to enable continuum on chkconfig, but it failed:
> [root@localhost init.d]# chkconfig --add continuum
> service continuum does not support chkconfig
> Looking at the shell script, it's missing the chkconfig commentaries, so I added them:
> #! /bin/sh
> # chkconfig: 345 20 80
> # description: Maven Continuum server
> Now everything is fine:
> [root@localhost init.d]# chkconfig --add continuum
> [root@localhost init.d]# chkconfig continuum on
> [root@localhost init.d]# service continuum start
> Starting continuum...
> I could provide a patch, but I don't know how the script is generated. So, long story short, this issue requires 2 changes:
> -  add the comment above in the run.sh script (or whatever generates it)
> - update the documentation (URL above)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Updated: (CONTINUUM-655) Add chkconfig support to the starting script

Posted by "Felipe Leme (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/CONTINUUM-655?page=all ]

Felipe Leme updated CONTINUUM-655:
----------------------------------

    Attachment:     (was: chkconfig_install.sh)

> Add chkconfig support to the starting script
> --------------------------------------------
>
>          Key: CONTINUUM-655
>          URL: http://jira.codehaus.org/browse/CONTINUUM-655
>      Project: Continuum
>         Type: Improvement

>   Components: Core system
>     Versions: 1.0.2
>  Environment: Fedora Core & any RedHat-based system
>     Reporter: Felipe Leme

>
> Original Estimate: 15 minutes
>         Remaining: 15 minutes
>
> I'm using Fedora Core 4 and wanted to start Continuum on startup, so I followed the instructions below:
> http://maven.apache.org/continuum/guides/mini/guide-linux-boot.html
> FC (and any RH-based distro) doesn't have the update-rc.d script; instead, they have chkconfig. So, I created the link on /etc/rc.d and tried to enable continuum on chkconfig, but it failed:
> [root@localhost init.d]# chkconfig --add continuum
> service continuum does not support chkconfig
> Looking at the shell script, it's missing the chkconfig commentaries, so I added them:
> #! /bin/sh
> # chkconfig: 345 20 80
> # description: Maven Continuum server
> Now everything is fine:
> [root@localhost init.d]# chkconfig --add continuum
> [root@localhost init.d]# chkconfig continuum on
> [root@localhost init.d]# service continuum start
> Starting continuum...
> I could provide a patch, but I don't know how the script is generated. So, long story short, this issue requires 2 changes:
> -  add the comment above in the run.sh script (or whatever generates it)
> - update the documentation (URL above)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Updated: (CONTINUUM-655) Add chkconfig support to the starting script

Posted by "Felipe Leme (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/CONTINUUM-655?page=all ]

Felipe Leme updated CONTINUUM-655:
----------------------------------

    Attachment: CONTINUUM-655.patch

> Add chkconfig support to the starting script
> --------------------------------------------
>
>          Key: CONTINUUM-655
>          URL: http://jira.codehaus.org/browse/CONTINUUM-655
>      Project: Continuum
>         Type: Improvement

>   Components: Core system
>     Versions: 1.0.2
>  Environment: Fedora Core & any RedHat-based system
>     Reporter: Felipe Leme
>  Attachments: CONTINUUM-655.patch, chkconfig_install.sh
>
> Original Estimate: 15 minutes
>         Remaining: 15 minutes
>
> I'm using Fedora Core 4 and wanted to start Continuum on startup, so I followed the instructions below:
> http://maven.apache.org/continuum/guides/mini/guide-linux-boot.html
> FC (and any RH-based distro) doesn't have the update-rc.d script; instead, they have chkconfig. So, I created the link on /etc/rc.d and tried to enable continuum on chkconfig, but it failed:
> [root@localhost init.d]# chkconfig --add continuum
> service continuum does not support chkconfig
> Looking at the shell script, it's missing the chkconfig commentaries, so I added them:
> #! /bin/sh
> # chkconfig: 345 20 80
> # description: Maven Continuum server
> Now everything is fine:
> [root@localhost init.d]# chkconfig --add continuum
> [root@localhost init.d]# chkconfig continuum on
> [root@localhost init.d]# service continuum start
> Starting continuum...
> I could provide a patch, but I don't know how the script is generated. So, long story short, this issue requires 2 changes:
> -  add the comment above in the run.sh script (or whatever generates it)
> - update the documentation (URL above)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Commented: (CONTINUUM-655) Add chkconfig support to the starting script

Posted by "Felipe Leme (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/CONTINUUM-655?page=comments#action_63387 ] 

Felipe Leme commented on CONTINUUM-655:
---------------------------------------

OBS: the 1. an 2. above are actually comments (#); I don't know why they were converted while generating this Jira. Anyway, let me try again:

#  chkconfig: 345 20 80
# description: Maven Continuum server



> Add chkconfig support to the starting script
> --------------------------------------------
>
>          Key: CONTINUUM-655
>          URL: http://jira.codehaus.org/browse/CONTINUUM-655
>      Project: Continuum
>         Type: Improvement

>   Components: Core system
>     Versions: 1.0.2
>  Environment: Fedora Core & any RedHat-based system
>     Reporter: Felipe Leme

>
> Original Estimate: 15 minutes
>         Remaining: 15 minutes
>
> I'm using Fedora Core 4 and wanted to start Continuum on startup, so I followed the instructions below:
> http://maven.apache.org/continuum/guides/mini/guide-linux-boot.html
> FC (and any RH-based distro) doesn't have the update-rc.d script; instead, they have chkconfig. So, I created the link on /etc/rc.d and tried to enable continuum on chkconfig, but it failed:
> [root@localhost init.d]# chkconfig --add continuum
> service continuum does not support chkconfig
> Looking at the shell script, it's missing the chkconfig commentaries, so I added them:
> #! /bin/sh
> # chkconfig: 345 20 80
> # description: Maven Continuum server
> Now everything is fine:
> [root@localhost init.d]# chkconfig --add continuum
> [root@localhost init.d]# chkconfig continuum on
> [root@localhost init.d]# service continuum start
> Starting continuum...
> I could provide a patch, but I don't know how the script is generated. So, long story short, this issue requires 2 changes:
> -  add the comment above in the run.sh script (or whatever generates it)
> - update the documentation (URL above)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Commented: (CONTINUUM-655) Add chkconfig support to the starting script

Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/CONTINUUM-655?page=comments#action_63434 ] 

Emmanuel Venisse commented on CONTINUUM-655:
--------------------------------------------

Can you provide a patch for documentation about your script?

> Add chkconfig support to the starting script
> --------------------------------------------
>
>          Key: CONTINUUM-655
>          URL: http://jira.codehaus.org/browse/CONTINUUM-655
>      Project: Continuum
>         Type: Improvement

>   Components: Core system
>     Versions: 1.0.2
>  Environment: Fedora Core & any RedHat-based system
>     Reporter: Felipe Leme
>  Attachments: chkconfig_install.sh
>
> Original Estimate: 15 minutes
>         Remaining: 15 minutes
>
> I'm using Fedora Core 4 and wanted to start Continuum on startup, so I followed the instructions below:
> http://maven.apache.org/continuum/guides/mini/guide-linux-boot.html
> FC (and any RH-based distro) doesn't have the update-rc.d script; instead, they have chkconfig. So, I created the link on /etc/rc.d and tried to enable continuum on chkconfig, but it failed:
> [root@localhost init.d]# chkconfig --add continuum
> service continuum does not support chkconfig
> Looking at the shell script, it's missing the chkconfig commentaries, so I added them:
> #! /bin/sh
> # chkconfig: 345 20 80
> # description: Maven Continuum server
> Now everything is fine:
> [root@localhost init.d]# chkconfig --add continuum
> [root@localhost init.d]# chkconfig continuum on
> [root@localhost init.d]# service continuum start
> Starting continuum...
> I could provide a patch, but I don't know how the script is generated. So, long story short, this issue requires 2 changes:
> -  add the comment above in the run.sh script (or whatever generates it)
> - update the documentation (URL above)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira