[checkmk-commits] Check_MK Git: check_mk: FIX: setup.sh: fix optical output of summary

Module: check_mk Branch: master Commit: 975b8dd0705611ca7d14cec7d34ceec3137a7f15 URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=975b8dd0705611… Author: Mathias Kettner <mk(a)mathias-kettner.de> Date: Thu Mar 10 17:33:09 2011 +0100 FIX: setup.sh: fix optical output of summary --- scripts/setup.sh | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/scripts/setup.sh b/scripts/setup.sh index c1600f5..fb93c21 100755 --- a/scripts/setup.sh +++ b/scripts/setup.sh @@ -285,19 +285,19 @@ files here (currently only the logwatch extension needs a configuration file)" ask_title "Integration with Nagios" -ask_dir -d nagiosuser nagios $(id -un) $OMD_SITE "Name of Nagios user" \ +ask_dir -d nagiosuser nagios $(id -un) "$OMD_SITE" "Name of Nagios user" \ "The working directory for check_mk contains several subdirectories that need to be writable by the Nagios user (which is running check_mk in check mode). Please specify the user that should own those directories" -ask_dir -d wwwuser www-data www-data $OMD_SITE "User of Apache process" \ +ask_dir -d wwwuser www-data www-data "$OMD_SITE" "User of Apache process" \ "Check_MK WATO (Web Administration Tool) needs a sudo configuration, such that Apache can run certain commands as $(id -un). If you specify the correct user of the apache process here, then we can create a valid sudo configuration for you later:" -ask_dir -d wwwgroup nagios $(id -un) $OMD_SITE "Common group of Nagios+Apache" \ +ask_dir -d wwwgroup nagios $(id -un) "$OMD_SITE" "Common group of Nagios+Apache" \ "Check_mk creates files and directories while running as $nagiosuser. Some of those need to be writable by the user that is running the webserver. Therefore a group is needed in which both Nagios and the webserver are