From cf3cf6501b9530ac3b327002e8e661055321dfa2 Mon Sep 17 00:00:00 2001 From: Krasimir Nedelchev Date: Sun, 23 Feb 2020 15:54:51 +0000 Subject: [PATCH] Change README heading levels --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 0fd3478..b6b354b 100644 --- a/README.md +++ b/README.md @@ -2,15 +2,15 @@ This container runs a Time Machine server for remote backups of computers running macOS. -### Usage +## Usage 1. Create a `.env` file following the template provided in `.env.schema`. 2. Create a symbolic link called `data` pointing to your preferred backup location. Example command: `ln -s /media/TimeMachine data`. 3. Start the container with `docker-compose up -d`. -### Notes +## Notes -##### Auto discovery +#### Auto discovery To enable auto discovery you need to use Avahi daemon. On Ubuntu you can install it by running `sudo apt install avahi-daemon avahi-utils`. @@ -20,7 +20,7 @@ To configure Avahi to broadcast Time Machine you can follow these instructions ( > - Copy the service description file from docker-timemachine/avahi/afpd.service to /etc/avahi/services/afpd.service > - Restart Avahi's daemon: sudo /etc/init.d/avahi-daemon restart -##### Performance +#### Performance macOS throttles Time Machine services to keep the OS more responsive, which can result in slower backups. You can disable this behavior with `sudo sysctl debug.lowpri_throttle_enabled=0`. This can be useful during the first backup, since it can involve transferring hundreds of gigabytes. After executing the command you should immediately notice higher disk and CPU usage and increased network activity. Time Machine's remaining time should also decrease drastically.