From 4662627a4a197c1f08258c16ef60c0020765d5b2 Mon Sep 17 00:00:00 2001 From: deajan Date: Fri, 28 Nov 2014 13:20:21 +0100 Subject: [PATCH] Quick doc update --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index c3c753c..6d976cf 100644 --- a/README.md +++ b/README.md @@ -70,6 +70,8 @@ that's actually launched and it's result. One you're happy with a test run, you may run obackup as a cron task with the "--silent" parameter so output will not be written to stdout. All backup activity is logged to "/var/log/obackup_backupname.log" or current directory if /var/log is not writable. +You may mix "--silent" and "--verbose" parameters to output verbose input only in the log files. + ## Final words Backup tasks aren't always reliable, connectivity loss, insufficient disk space, hacked servers with tons of unusefull stuff to backup... Anything can happen.