From c9c4a45cb7ae029d1a74d8fc99c908115eba1d21 Mon Sep 17 00:00:00 2001 From: Donald Webster Date: Mon, 6 Mar 2017 15:39:51 -0800 Subject: [PATCH] Updated Common Problems (markdown) --- Common-Problems.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Common-Problems.md b/Common-Problems.md index c590c69..9d8206c 100644 --- a/Common-Problems.md +++ b/Common-Problems.md @@ -5,7 +5,7 @@ * Using mapped network drives generally doesn't work very well, especially when Radarr is configured to run as a service. The better way to set shares up is using UNC paths. So instead of `X:\Movies` use `\\Server\Movies\`. ### Permissions ### -* Radarr will need to movie files away from where the downloader puts them into the final location. This means that Radarr will need to be able to read and write from the source and to the destination. +* Radarr will need to move files away from where the downloader puts them into the final location, so this means that Radarr will need to read/write to both the source and the destination directory and files. * On Linux, where best practices have services running as their own user, this will probably mean using a shared group and setting folder permissions to `775` and files to `664` both in your downloader and Radarr. In umask notation, that would be `002`. ### Movie Files Not in Folders ###