Request #403
Request to clarifiy the explanation for k flag in shell.sh
| Status: | Closed | Start date: | 11/09/2010 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Daniel Molina | % Done: | 100% | |
| Category: | - | |||
| Target version: | Release 2.0.1 | |||
| Pull request: |
Description
In shell.sh, the explanation for k flag is as follows: "-k: keep current configuration files, useful when upgrading". This explanation may confuse users whether the flag can be set when installing OpenNebula for the first time or useful only when upgrading to newer version of OpenNebula. Setting this flag for fresh OpenNebula install will avoid all the etc files being copied from the installation directory to respective target directories, which is undesirable.
install.sh 65 while true ; do
66 case "$1" in
67 -h) usage; exit 0;;
68 -k) INSTALL_ETC="no" ; shift ;;
69 -r) UNINSTALL="yes" ; shift ;;
My suggestion is to clarify the explanation by explicitly mentioning that this flag should not be set when installing OpenNebula for the first time.
-k: keep configuration files of existing OpenNebula installation, useful when upgrading. this flag should not be set when installing OpenNebula for the first time
Associated revisions
feature #403: Clarify the explanation for -k flag in install.sh
feature #403: Clarify the explanation for -k flag in install.sh
(cherry picked from commit fc56158f815b69c093c7f1f14e9d4394d1337489)
History
#1
Updated by Mikael Fernandus Simalango over 10 years ago
I meant in install.sh
#2
Updated by Ruben S. Montero over 10 years ago
- Assignee set to Daniel Molina
- Target version set to Release 2.0.1
#3
Updated by Daniel Molina over 10 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
Hi Mikael,
Patch applied, thanks for your feedback