Generate the file /var/lib/kodi/.lircrc with the following content:Ĭonfig = pgrep kodi-standalone || /usr/bin/kodi-standalone -l /run/lirc/lircdĪdopt button to whatever button on the remote is to start Kodi. Also, the package kodi-standalone-service AUR has to be installed. See the corresponding LIRC article and create a functional setup with a remote. This can be useful on setups running 24/7 and having kodi up on demand. Users will need kodi-standalone-service AUR and lirc. Kodi can be configured to start via a key press. Start from remote control with LIRC / irexec # start when receiving an UDP datagram (Wakeup/WOL) # Start when receiving a TCP request on the http control port Depending on the setup, one can optionally change the ports in # This fails if the user does not have an X session.ĮxecStopPost=/usr/bin/systemctl -no-block start Unset There are no packaged and files, one must create them manually. Start listening by starting user.socket (replace user with the user running Kodi to be started as). Socket activation can be used to start Kodi when the user issues a Wakeup command from a remote control app like Kore, or makes a connection to Kodi's html control port. xinitrc file must be executable, so the kodi user's home must not be mounted with the noexec option. CLI: Use kodi-send provided by kodi-eventclients to send the ShutDown() or the Reboot command.Mobile device: The official Android/iOS apps can also perform these actions (assuming the corresponding options are enabled in Kodi).Kodi GUI: Selecting the corresponding option under power menu in the Kodi GUI.While it is possible to run Kodi in systemd's user.slice instead, doing so makes it difficult to use USB mounts within Kodi and to use pulseaudio for Kodi sessions. In principal this is no different than data loss occurring from a user doing work when a sysadmin issues a reboot command without prior warning. Failure to do so will result in an ungraceful exit of Kodi and the possible loss of GUI settings, Kodi uptime etc. In order to have Kodi exit gracefully, initiate system reboot/shutdown with the respective Kodi actions instead of using systemctl. Recommended methods to reboot/shutdown using kodi-standalone serviceīe aware that these services run Kodi in systemd's system.slice, not user.slice. Define these variables in /etc/conf.d/kodi-standalone and they will be passed along to the service.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |