On 16/05/18 15:15, Dennis Lee Bieber wrote:
> On Wed, 16 May 2018 11:43:41 +0100, RobH  declaimed the
> following:
>
>
>> Traceback (most recent call last)
>>   File "intruder_recmotion.py",  line 37, in 
>>    shutil.copyfile(RAMname, NASname)
>>   File "/usr/lib/python 2.7/shutil.py", line 83, in copyfile with
>> open(dst, 'wb') as fdst:
>> IOError: [Errno 2] No such file or directory:
>> '/192.168.0.22/mnt/CCTV/PiZero/2018-16-16_11.25.36.h264'
>>
>> I have checked the path to the PiZero folder or dataset on my FreeNAS
>> box and it is correct.
>>
>
>  On the R-PI, show us the result of
>
> ls -a /
>
> {The following is a Debian install in a VirtualBox instance, not an actual
> R-PI}
>
> wulfraed@stretch:~$ ls -a /
> .     dev         initrd.img.old  libx32      opt   sbin  usr
> ..    etc         lib             lost+found  proc  srv   var
> bin   home        lib32           media       root  sys   vmlinuz
> boot  initrd.img  lib64           mnt         run   tmp   vmlinuz.old
> wulfraed@stretch:~$
>
>  According to the error message, you are looking to have a directory
> named 192.168.0.22 in the root of your R-PI filesystem.
>
>  Or (given your phrasing) you've actually mounted the R-PI on the NAS,
> and not the NAS on the R-PI. Whatever the path is, it has to be valid ON
> THE R-PI -- logging into the NAS via some administration interface doesn't
> validate anything other than that you created subdirectories on it.
>
> https://www.htpcguides.com/mounting-storage-drives-in-debian-linux/
>
>
ls -a /
.  bin dev home lost+found media opt root sbin sys usr
.. boot etc lib man       mnt   proc  run srv tmp var

--- SoupGate-Win32 v1.05