From c0c56f6572d283a00fe634bf603c106899a24c28 Mon Sep 17 00:00:00 2001 From: David Runge Date: Thu, 26 Mar 2015 04:08:36 +0100 Subject: README.md: Fixing code blocks (again) --- README.md | 8 -------- 1 file changed, 8 deletions(-) diff --git a/README.md b/README.md index c38f679..737088c 100644 --- a/README.md +++ b/README.md @@ -48,23 +48,19 @@ This timer unit has the same name as its service. /usr/lib/systemd/system/backup-bitlbee.service /usr/lib/systemd/system/backup-bitlbee.timer - Using *systemctl* one can easily start and stop timer units belonging to a service. As root: systemctl start backup-bitlbee.timer systemctl stop backup-bitlbee.timer - To make the system boot with this timer started, enable it. Again, as root: systemctl enable backup-bitlbee.timer systemctl disable backup-bitlbee.timer - When the timer's conditions are met, the service *backup-bitlbee.service* is started automatically. Much like cron. Unlike cron, you can also start and stop the service separately: systemctl start backup-bitlbee.service systemctl stop backup-bitlbee.service - **Note:** *Due to systemd's architecture you can copy/paste and modify the given timer from **/usr/lib/systemd/system/** and put it to **/etc/systemd/system**. The latter will always have precedence over the former. Same counts for services!* ### Example 2: Activating a user backup with the help of a timer @@ -73,23 +69,19 @@ The user service and timer units reside in a different location: /usr/lib/systemd/user/backup-firefox.service /usr/lib/systemd/user/backup-firefox.timer - Using *systemctl* one can easily start and stop timer units belonging to a service. This time, as your user: systemctl --user start backup-firefox.timer systemctl --user stop backup-firefox.timer - To make your user environment start with this timer started, enable it. Again, as your user: systemctl --user enable backup-firefox.timer systemctl --user disable backup-firefox.timer - When the timer's conditions are met, the service *backup-firefox.service* is started (as your user) automatically. This service can of course also just be started and stopped separately from the timer: systemctl --user start backup-firefox.service systemctl --user stop backup-firefox.service - **Note:** *Due to systemd's architecture you can copy/paste and modify the given timer from **/usr/lib/systemd/user/** and put it to **/etc/systemd/user**. The latter will always have precedence over the former. Same counts for services!* **Note:** *To minimize the size of your backups, you might want to consider using tools like [profile-cleaner](https://github.com/graysky2/profile-cleaner) to shrink the size of your program profiles.* -- cgit v1.2.3-70-g09d2