Skip to content

Commit

Permalink
Make sure to re-apply SMB settings to cover scenario where `CRASHPLAN…
Browse files Browse the repository at this point in the history
…_SERVER_ADDRESS` was not set to `SMB` during the initial launch of the container.
  • Loading branch information
jlesage committed Dec 16, 2023
1 parent d01f3eb commit 3df3f67
Showing 1 changed file with 6 additions and 0 deletions.
6 changes: 6 additions & 0 deletions rootfs/etc/cont-init.d/55-crashplan-pro.sh
Original file line number Diff line number Diff line change
Expand Up @@ -86,6 +86,12 @@ if [ "$FIRST_INSTALL" -eq 1 ] || [ "$UPGRADE" -eq 1 ]; then
elif [ -n "${CRASHPLAN_SERVER_ADDRESS:-}" ]; then
sed-patch 's|<authority .*|<authority address="'$CRASHPLAN_SERVER_ADDRESS'" hideAddress="true" lockAddress="false" />|' /config/conf/default.service.xml
fi
elif [ "${CRASHPLAN_SERVER_ADDRESS:-}" = "SMB" ]; then
# Make sure to re-apply changes related to the SMB version. Some people
# might not have set the `CRASHPLAN_SERVER_ADDRESS` to `SMB` during the
# first launch.
sed -i 's|<orgType>ENTERPRISE</orgType>|<orgType>BUSINESS</orgType>|' /config/conf/default.service.xml
sed -i 's|<authority .*|<authority address="central.crashplanpro.com:4287" hideAddress="true" lockAddress="true" />|' /config/conf/default.service.xml
fi

# run.conf was used before CrashPlan 7.0.0.
Expand Down

0 comments on commit 3df3f67

Please sign in to comment.