Just confirming latest DSM update seems to have removed it..
Will investigate once I return home later this week - see if it's just a new setting or something.
I updated over weekend - all okfletchb1 wrote: ↑Sun Jan 20, 2019 3:55 pm I have been redoing the rooms in my house a little at time for past 2.5 years and just now moved my networking equip from the temporary room back into the room we just finished (well 99%). And for a second I forgot that I did not have to manually log into putty anymore and restart the DVR like in the past. Yep your app is still working great!
A few days ago I got a message from synology to update my php. Just wanted to check first to make sure that is ok?
The new version is PHP 7.0.33-0028
Thanks again.
that's the latest package.
Thanks just wanted to verify before I let it update.demonrik wrote: ↑Sun Jan 20, 2019 4:17 pmI updated over weekend - all okfletchb1 wrote: ↑Sun Jan 20, 2019 3:55 pm I have been redoing the rooms in my house a little at time for past 2.5 years and just now moved my networking equip from the temporary room back into the room we just finished (well 99%). And for a second I forgot that I did not have to manually log into putty anymore and restart the DVR like in the past. Yep your app is still working great!
A few days ago I got a message from synology to update my php. Just wanted to check first to make sure that is ok?
The new version is PHP 7.0.33-0028
Thanks again.
demonrikToday at 12:27 PMdemonrik wrote: ↑Mon Oct 29, 2018 4:46 pmHere's something I have put together, but waiting for someone to verify before I add to the workarounds
On Synology they lock down a lot. so we have to add the right permissions to get things started.
So first things first.. disable the DVR (via UI or app center) and ssh to the NAS and login as your admin user.
I'm going to assume that everything on your NAS is located on /volume1/ - adjust to volume[1-9] as needed.
Now we need to add the admin access control list (ACL) withThis will now allow us to actually add it as a shareCode: Select all
sudo synoacltool -add /volume1/HDHomeRunDVR group:administrators:allow:rwxpdDaARWc--:fd—
So back to the DSM web interface, log in, and
- open Control Panel
- open Shared Folder
- select 'Create'
- enter the name of the folder, e.g. HDHomeRunDVR
- uncheck 'Restrict Access to administrators only'
- uncheck 'Enable Recycle Bin'
- click 'Next', then click 'Apply'
Now you should have the share in filestation and be able to access it from other PCs in your network.
The final thing we need to do, is just quickly ensure that the http user still has access for the engine.
So back to ssh and enterAll should be ok at this point - time to restart the DVR engine..Code: Select all
sudo synoacltool -add /volume1/HDHomeRunDVR group:http:allow:rwxpdDaARWc--:fd--
let me know if this works for you
New to the forum, I have tried all sorts of things to make the default record folder (HDHomeRundDVR) a share or move the recording path to a shared folder with no luck. Tried lots of different things from a symbolic link to synoactool. When I try to get into the engine UI I get error 500. I have moved the engine and all related programs from volume2 (SSD) to volume1 where the raid is but still no luck. Any ideas? I can record to the hidden folder and playback as normal.I wanted to modify the default record path to a new location, rather than modify the existing record path.
1) stop engine via engine UI -or- DSM
2) modify record path via engine UI
3) copy contents of old location into new location via SSH, using a CP command (if needed)
4) update sharing permission on new record path via SSH (engine uses HTTP as login)
5) start engine via UI
Voila. I originally got "DVR failure", until i completed step 4.
Stop current HDHR engine
The config file is hidden away with the installer.