-
Disable and stop the systemd-resolved service:
sudo systemctl disable systemd-resolved.service sudo systemctl stop systemd-resolved -
Then put the following line in the
[main]section of your/etc/NetworkManager/NetworkManager.conf:
Vagrant libvirt allows the user to customize the virtual machines to add features and use QEMU options that are not exposed via the plugin itself. For this it uses the libvirt's custom QEMU arguments options which appends the args at the very end of the command line. This allows you to not only add new arguments, it allows you to also override the plugin constructed defaults.
In the snippet below the
- machine and memory default plugin arguments are over-ridden
- an additional NVDIMM device is created and added to the machine
Create the directory structure:
touch docker-compose.yml
mkdir -p volumes/{config,file,logs}
Populate the vault config vault.json:
Latest Update 2021-03-06 : New image showing the new "Services" in Home Assistant and got some tips from the comments below.
Credits and thanks: Home Assistant Forum users & Github users: @ocso, @wiphye, @teachingbirds, @tboyce1, @simbesh, @JeffLIrion @ff12 @rebmemer @siaox @DiederikvandenB @Thebuz @clapbr @Finsterclown
Starts Youtube App
entity_id: media_player.shield
command: >-
Create file /etc/systemd/system/docker-compose@.service. SystemD calling binaries using an absolute path. In my case is prefixed by /usr/local/bin, you should use paths specific for your environment.
[Unit]
Description=%i service with docker compose
PartOf=docker.service
After=docker.serviceTuning Intel Skylake and beyond for optimal performance and feature level support on Linux:
Note that on Skylake, Kabylake (and the now cancelled "Broxton") SKUs, functionality such as power saving, GPU scheduling and HDMI audio have been moved onto binary-only firmware, and as such, the GuC and the HuC blobs must be loaded at run-time to access this functionality.
Enabling GuC and HuC on Skylake and above requires a few extra parameters be passed to the kernel before boot.
Instructions provided for both Fedora and Ubuntu (including Debian):
Note that the firmware for these GPUs is often packaged by your distributor, and as such, you can confirm the firmware blob's availability by running:
Quickly check for supported NVENC and NPP hardware acceleration capabilities in FFmpeg on your platform:
Depending on how you built ffmpeg, you may want to check the supported NVENC-based hardware acceleration capabilities in ffmpeg by running:
$ for i in encoders decoders filters; do
echo $i:; ffmpeg -hide_banner -${i} | egrep -i "npp|cuvid|nvenc|cuda|nvdec"
done
Sample output (as on my testbed):
| image: node:latest | |
| cache: | |
| paths: | |
| - node_modules/ | |
| - app/bower_components | |
| deploy_production: | |
| stage: deploy | |
| environment: Production |
| #! /usr/bin/env python3 | |
| """Fixing bluetooth stereo headphone/headset problem in debian distros. | |
| Workaround for bug: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1577197 | |
| Run it with python3.5 or higher after pairing/connecting the bluetooth stereo headphone. | |
| This will be only fixes the bluez5 problem mentioned above . | |
| Licence: Freeware |
| #!/bin/bash | |
| # Bash Script by https://gist.github.com/mitchellkrogza | |
| # ************************************************************ | |
| # This script clears the log file and database of Fail2Ban | |
| # This resets Fail2Ban to a completely clean state | |
| # Useful to use after you have finished testing all your jails | |
| # and completed your initial setup of Fail2Ban and are now | |
| # putting the server into LIVE mode | |
| # ************************************************************ |
