be more defensive in rm -rf

This commit is contained in:
Praveen Arimbrathodiyil 2017-03-23 17:16:26 +05:30
parent f92b012a7a
commit 33eb420ac6

19
debian/postrm vendored
View file

@ -48,16 +48,15 @@ case "$1" in
# Check if we should remove data?
db_get gitlab/purge
if [ "${RET}" = "true" ]; then
rm -rf ${gitlab_data_dir}/shared
rm -rf ${gitlab_data_dir}/public
rm -rf ${gitlab_data_dir}/db
rm -rf ${gitlab_data_dir}/repositories
rm -rf ${gitlab_data_dir}/secrets.yml
rm -rf ${gitlab_data_dir}/Gemfile.lock
rm -rf ${gitlab_log_dir}
rm -rf ${gitlab_cache_path}
rm -rf ${gitlab_pid_path}
rm -rf ${gitlab_data_dir}
if [ -d ${gitlab_data_dir} ]; then
for i in shared public db repositories secrets.yml Gemfile.lock; do
test -e ${gitlab_data_dir}/$i && rm -rf ${gitlab_data_dir}/$i
done
fi
test -e ${gitlab_log_dir} && rm -rf ${gitlab_log_dir}
test -e ${gitlab_cache_path} && rm -rf ${gitlab_cache_path}
test -e ${gitlab_pid_path} && rm -rf ${gitlab_pid_path}
test -e ${gitlab_data_dir} && rm -rf ${gitlab_data_dir}
if [ ! -z "${gitlab_user}" ]; then
# Do only if gitlab_user is set
if command -v dropdb >/dev/null; then