What do you mean by not accessible?TBlankenheim wrote: ↑Wed Feb 14, 2018 12:25 pmI may have found a hiccup in the installation of HDHomeRunDVR-0.4.2-20180213.spk. After the installation, HDHomeRunDVR share was no longer accessible. I checked the permissions on /volume1/HDHomeRunDVR/ and they were set to 770 (if I recall correctly). Did a chmod -R 777 "/volume1/HDHomeRunDVR/" (probably overkill) and all was good. Not sure if this is the proper solution to this problem, but it worked for me.- update to the 20180213beta1 engine
- startup script (from restart or appcenter) logs to /tmp/hdhr_arch_choice to log the arch detected to help debug.
- now modifies newly created directory for recordpath to be accessible by default by http
FWIW - my package does not create a share - just a subfolder (i.e. it's not shared out beyond the NAS)
Here is the code in the installation package
Code: Select all
RECORDING_PATH="$SYNOPKG_PKGDEST_VOL/$SYNOPKG_PKGNAME" if [ ! -d $RECORDING_PATH ] ; then mkdir $RECORDING_PATH fi sed -i "s!\(RecordPath\s*=\).*!\1$RECORDING_PATH!" $hdhr_etc_path/$hdhr_conf chown -R http:http $RECORDING_PATH chmod -R u+w $RECORDING_PATH
this is different from the SD created share /volume1/HDHomeRun
It checks if the path exists - otherwise it creates it.
Then updates the RecordPath in the config file appropriately.
(there is a missing feature to not do this if upgrading)
then sets the owner of the RecordPath to the http user
and then adds write permissions
The fact that you had to change from 770 to 777 indicates that the http user doesn't have write permissions to the folder for some reason?!