This will help troubleshooting, as the future sysadmins will connect to
the machine, run `journalctl -f ` to see what's wrong with the machine,
and in about 30 seconds they will see:

  Error fetching machine configuration!
  Error fetching machine info!
  If this is a new machine, did you add it into labmanager-admin?

So they will know what's wrong, and how to correct it.

These are not debug messages, they should be always on to see what's happening
on the machine.

Solo il software è su paperboy2 / birthdaygirl.

Nota: questo file di configurazione viene scaricato solo quando sulla
macchina non è presente. Se il file esiste, lo script non lo sovrascrive,
per non perdere le modifiche locali fatte dall'amministratore di sistema.

Git should be able to record the file modes now.

They could contain local modification made by the admin,
so we will just create them when they are not present,
and leave them as they are if they are already on the machine.

It is optional, but it is easier if it's already there, ready to be
modified.

Added a new multi-user target for targets esame*, so we can avoid to start NFS services if not needed

The first commit (the one that was reverted) contained a spurious,
unrelated change.

This reverts commit 2ed8cbd1.

The bta-no-usbpen was a link to /bin/sleep.

Passaggio ai target secondari (esame e graphical) attraverso comando 'start' invece di 'isolate' (NetworkManager non ripartiva più dopo il passaggio di target)

Forgot to add esame-get-config.timer to esameshow.target and the target itself in the install script.

New feature (fix for someone...): don't erase user's home if the computer crashes or reboots during the exam.
The user's home is erased (if required) only when the exam mode starts the first time.