----

  . Activate the nesting feature:

  +

  sudo modprobe kvm_amd nested=1

  ----    

  . Nested virtualization is enabled until the host is rebooted. To enable it permanently, add the following line to the `/etc/modprobe.d/kvm.conf` file:                        

  +

  options kvm_amd nested=1

  ----

  owner of each machine to decide whether automatic updates are desirable

  or not for that machine. One of the things which makes one a good system

  administrator is the ability to evaluate the facts and other people's

  A general rule that applies in most cases is as follows:

  example, you could create your own DNF repository on a local server,

  and only put in tested or trusted updates. Then use the automatic

  updates from only your own repository. Such setups, while perhaps more

  otherwise inherent in automatic updates.

  [[how-are-automatic-updates-done]]

  [[install-and-settings-of-dnf-automatic]]

  === Install and settings of dnf-automatic

  [source,bash]

  ----

  The main advantage of automating the updates is that machines are likely

  to get updated more quickly, more often, and more uniformly than if they

  internet which would have been safe if the latest updates where

  installed in a timely way.

  * You do not have any irreplaceable data on the machine, or have proper

    backups of such data.

  apply, then you will need to weigh the risks and decide for yourself if

  automatic updates are the best way to proceed.

    unscheduled downtime.

  * You installed custom software, compiled software from source, or use

    third party software that has strict package version requirements.

  * Your environment requires meticulous change-control procedures.

  There are also some other reasons why installing automatic updates

  without testing may be a bad idea. A few such reasons are:

    file which is not flagged as a configuration file, then you might lose

    your configuration changes. Or an update may have a different format of

    configuration file, requiring a manual reconfiguration. It is often best

    packages such as mail, web, or database server packages.

  * Unwanted side effects. Some packages can create annoying side effects,

    particularly ones which have cron jobs. Updates to base packages like

    openssl, openldap, sql servers, etc. can have an effect on many other

    seemingly unrelated packages.

  * Bugs. Many packages contain buggy software or installation scripts.

  [[best-practices-when-using-automatic-updates]]

  email_host = localhost

  ----

  change will mean that after dnf-automatic runs, it will email you

  information you about available updates, or log about downloaded

  packages, or installed updates according to settings in `automatic.conf`.

  Another common problem is having automatic updates run when it isn't

  desired (holidays, weekends, vacations, etc). If there are times that no

  may be best to avoid doing updates on those days.

  This problem can be fixed by modification of the timer of dnf-automatic

  any attacks that might occur before updates are in place. This might

  include an external firewall, a host-based firewall (like iptables,

  ipchains, and/or tcp wrappers), not performing dangerous tasks on the

  authentication or login monitoring, etc).

  The following is needed:

  . Our program's source in a publicly available git repository somewhere. This tutorial uses a simple example program - hellocopr - to demonstrate the process.

  +

  ```

  user@host ~/copr-tito-quickdoc % ls

  Explanation of the above:

  * `directory mask = 0770`: as before, but for directories.

  Restart Samba for the changes to take effect:

  Some things to check if you cannot access the share.

  +

  Find `maria` in the Samba database:

  +

  +

  In this case, the user should be in the `myfamily` group.

  +

  ....

  [family]

  [[trouble_with_writing_in_the_share]]

  === Trouble with writing in the share

  +

  ....

  [family]