On 2018-05-16 18:58, RobH wrote:
> On 16/05/18 14:56, Björn Lundin wrote:
>> On 2018-05-16 12:43, RobH wrote:
>>
>>> '/192.168.0.22/mnt/CCTV/PiZero/2018-16-16_11.25.36.h264'
>>
>> do you REALLY have a local directory called 192.168.0.22 ??
> No, that is the IP address of path or part of it anyway

That is the reason the error message say that it does not find the
directory. look again. the first part od the file

>>> '/192.168.0.22/mnt/CCTV/PiZero/2018-16-16_11.25.36.h264'
     ^^^^^^^^^^^^^

So as I said:

>> you should MOUNT the NAS (which may be at 192.168.0.22) on a local
>> directory.
> Where on what device, on the Pi Zero or on my NAS server

mount (in this context) means 'bringing the filesystem of the NAS
looking like a part od the filesystem of the PI


So again : on the PI do

>> #mount -t cifs -o username=USERNAME,password=PASSWD
>> //192.168.1.88/shares /mnt/share
>>
>> on one line. as root or sudo

here I guess I need to clarify that you should exchange
 * USERNAME to the username used to log on to the NAS
 * PASSWORD to the password of above user on the NAS
 * //192.168.1.88/shares to the ipaddres of the NAS +
    the name of the share
 * /mnt/share to a local directory. /mnt/nas is not to bad

if /mnt/nas does not exist - create it :
sudo mkdir /mnt/nas
sudo chown -R pi:pi /mnt/nas

to fix permissions

Now - after this manouver you have linked
the Pi's /mnt/nas with the NAS's /shares directory

whatever you write - on the PI - to /mnt/nas end up on the NAS.
NOT on the PI. which is the whole point


>> and save the file to
>> '/mnt/nas/2018-16-16_11.25.36.h264'
>
> As a separate file on the Pi Zero??

no - as above - it will save it on the NAS.
NOT on the PI since the mount command links the filesystem with each other.


(and as a comment to other error you had with bash error messages)
make bash run python which run the python file.

like

$python3 your_python_file.py


--
--
Björn

--- SoupGate-Win32 v1.05