SABnzbd Forums

I'm not sure which program is doing it (SABNZBD or Couch Potato) but the movies I download using SABNZBD alone AND the movies I download through SABNZBD with couch potato both show up with a lock on the file and don't show up on my network connected XBMC media pc. When I try to play them on my media pc connected via local network, the folders show up but the files do not. I believe it has something to do with permissions. I've tried changing permissions to share with everyone on the network and share with the XBMC box I have in the other room but nothing changes. Older movie files downloaded through other means (rapidshare/fileserve) and TV shows downloaded with SABNZBD with sickbeard or manually added nzbs, work fine. Movies are the issue, whether I'm initiating the downloading through couch potato or adding a nzb manually, they are locked and can't see them over a network. Does anyone know what would be causing this automatic permission setting???

Windows 7 on drive that has the files/storage
XBMC Live on my media pc connected via home network

Bump. Anyone? No one has ever heard of this?

It's not clear to me on which system SABnzbd and the others run.

The movies/tvshows and sabnzbd/couch poatato are all on the win 7 machine streaming to the linux/XBMC.

SABnzbd doesn't bother with access rights on Windows.
It just assumes that the rights of the base folder are inherited by everything created in it.
That's the normal situation on Windows.
Where is the final destination disk of the files? The Windows box or the XBMC box?

The destination is on the windows machine. I have couch potato doing the post processing.

The folders, with the files with padlocks on them, do not have padlocks on them.

Like I said: SABnzbd doesn't do anything with permissions.
So there are roughly two potential causes:
- Your folder rights inheritance is incorrect
- CouchPotato messes up.

I don't know anything about CouchPotato.

Ah, ok. I'm assuming it's couch potato. I'll go over there and try to figure it out. thanks

Could it be something with the unpacking program automatically setting the permissions?

steigede wrote:Could it be something with the unpacking program automatically setting the permissions?

No, we tell unrar to ignore any access rights and ownership info stored in the RAR files.

Hrm.... ok. So maybe it has something to do with the couch potato script that processes the files. I'll keep trying to figure it out. Thanks for the responses!