Question: What is the correct way of making nmcli commands persistent?

For example: `nmcli device modify eth0 ipv4.method auto` works but if I reboot the machine this is lost.

I know about interactive `nmcli> save` but I do not want to use interactive mode and I was not able to find the param neded to save these.

What is the unattended version to perform this manual operations?

```
nmcli c e eth0
set  ipv4.method auto
set  ipv6.method auto
set  802-3-ethernet.mtu 9000
save persistent
quit

```

Answer: 
I work without venv on Debian 10.
I was searching for the misterious libplaidml.so and finally found it !
It's in `~/.local/lib/libplaidml.so`
Now we want plaidml to be able to find it's own library and local configuration files which lie in `~/.local/share/plaidml/config.json`.
It also can't find them. So it's kind of buggy or not synchronized with the way python3 handles local/per user installations.
Looking into source code of `~/.local/lib/python3.7/site-packages/plaidml/settings.py` we see this code:

```
 def _find_config(name):
        prefixes = [
            sys.prefix,
            os.path.join(sys.prefix, 'local'),
        ]
    ...

```

It gets sys.prefix which contains '/usr' instead of '~/.local' so it tries to load `/usr/share/plaidml/experimental.json` instead of '~/.local/share/plaidml/experimental.json`
> 
> OSError:
>  /home/e1326196/plaidml/lib/python3.5/site-packages/plaidml/libplaidml.so:
>  cannot open shared object file: No such file or directory
> 
> 
> 

I actually just ran into the same problem.
From my limited understanding, this means when building something, the linker cannot find the shared library it believes is located above.

In my case, I tried to uninstall the plaidml through pip3, then I saw the location of the library file actually was /usr/lib for some reason. So I move the library file (I should've copied) to the above address in the error, and it worked. (in a sense that it shows me another error, but that maybe specific to me).