Confluence - When to use start-confluence.sh vs startup.sh

[Andrew Khoury]

I'm attempting to install the latest version of Confluence (5.4.3) via the unpackage method in linux.

I'm looking to find or write my own init script so I can start the service using the command "service start confluence".

I'm a little confused about if I should be using start-confluence.sh or startup.sh within my init script.

start-confluence.sh # executes either catalina.sh or startup.sh

startup.sh # executes catalina.sh

catalina.sh # doe the real work, also reads in data from setenv.sh & setclasspath.sh

This article suggests startup.sh:
https://confluence.atlassian.com/display/DOC/Start+Confluence+Automatically+on+Linux

This article asks a simliar question but no answer:
https://jira.atlassian.com/browse/JRA-23953

This article suggest "start-confluence.sh" is the new script and should be used:
https://confluence.atlassian.com/pages/viewpage.action?pageId=261752746

The information I have so far appears to be conflicing, can anyone give me any insights into this?

[Patrice Rompas]

Hi Andrew

All the articles you mentioned has a valid information.
For additional information, running startup.sh will execute the application using the current user. But start-confluence.sh will execute the application using the user mentioned in user.sh. If the user.sh doesn't specify any user, it will execute the application using the current user.
This affects the directory/file permission when running Confluence.

Regards,
Samuel