That was my fear 
The only other way i thought is a script on the primary pi to copy regulary the texture.db and thumbnail and paste to all other
Posts by psycho-kila
-
-
Hi everyone,
i installed libreelec 9.2.3and i have a mariaDB DB on external server.
After installation of new pi, a lot of movie / actor pictures are broken, i fix that with import of texture13.db and thumbnail folder from my old pi 3.
i would like centralize the texture13.db and cache Thumbnail, for the second i understand that was by advancedsetting.xml and pathsubstitute but for the first just pathsubstitute for this little db seems dangerous to me, do you know if it's the only way or it's possible to use insert this texture db in a real DB like mariaDB ?
Thx by advance
regards,
benjamin
-
Man, you are a genius, it's ok now
Thx
-
Hi everyone,
I installed LE 9.2.3 on my new pi4 and configured all service with success except the cifs auto mount, when i start him manually it's ok but impossible to start him on boot.
I tried all option i think (vers=1.0, 2.1, 3.0, rw) but always same.
LE is configured to wait network on boot 30s.
In journalctl the only strange row is this (at the end of start) :
Apr 11 18:28:49 noferatu connmand[291]: ntp: adjust (jump): +38853537.328936 sec
Don't know if the problem comes from that but it's really possible, I tried to modify the required/after to connman.service without success and the sync of ntp is always after
, it's possible to launch the mount script after the sync of ntp ?my storage-videos.mount :
Code
Display More[Unit] # The description should be used to explain what this servicefile is for Description=video cifs mount script # if we do network mounts like here we *require* 'network-online.service' # which checks if the network is online Requires=network-online.service #Requires=connman.service # our scripts must start *after* 'network-online.service', on timeout and if # 'network-online.service' fails we can not mount and this scripts fails too After=network-online.service #After=connman.service # usually we mount networks shares because we want they avaible *before* XBMC starts. # so XBMC has access to this mounts from beginning. Note: this slows down the boot! Before=kodi.service [Mount] # The share we want mount What=//192.168.1.50/videos # Where we want mount this share Where=/storage/videos # Any options you usually use with the "-o" parameter in the mount command Options=username=kodi,password=kodi,ro,noauto # filesystem type Type=cifs [Install] # The target is used by 'systemctl enable <name_of_this_file.mount>' to link # this service to a runlevel for starting on boot. usually 'multi-user.target' # is ok here. WantedBy=multi-user.targetsystemctl status storage-videos.mount just after the boot :
Code
Display More● storage-videos.mount - video cifs mount script Loaded: loaded (/storage/.config/system.d/storage-videos.mount; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Thu 2019-04-11 18:28:47 CEST; 1 years 2 months ago Where: /storage/videos What: //192.168.1.50/videos Apr 11 18:28:43 noferatu systemd[1]: Mounting video cifs mount script... Apr 11 18:28:47 noferatu mount[535]: mount: mounting //192.168.1.50/videos on /storage/videos failed: Connection refused Apr 11 18:28:47 noferatu systemd[1]: storage-videos.mount: Mount process exited, code=exited, status=255/EXCEPTION Apr 11 18:28:47 noferatu systemd[1]: storage-videos.mount: Failed with result 'exit-code'. Apr 11 18:28:47 noferatu systemd[1]: Failed to mount video cifs mount script.Thx by advance
Regards,
Benjamin