Bug 508561 - rdiff-backup log file empty
rdiff-backup log file empty
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: rdiff-backup (Show other bugs)
10
i386 Linux
low Severity medium
: ---
: ---
Assigned To: Kevin Fenzi
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-06-28 11:43 EDT by Robert Kochis
Modified: 2009-06-28 12:52 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-06-28 12:52:50 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
screenshot of directory (102.68 KB, image/png)
2009-06-28 11:44 EDT, Robert Kochis
no flags Details

  None (edit)
Description Robert Kochis 2009-06-28 11:43:10 EDT
Description of problem:
Log file for rdiff-backup is blank, although man page specifies that verbosity defaults to a value of 3.  This is a local-local drive backup

Version-Release number of selected component (if applicable):
Name       : rdiff-backup
Arch       : i386
Version    : 1.2.8
Release    : 1.fc10
Size       : 1.6 M
Repo       : installed


How reproducible:
Easy - 100% of the time

Steps to Reproduce:
1.login as user 
2.rdiff-backup /home/bkochis /media/disk/bkochis-home
3.
  
Actual results:


Expected results:
Some form of output noted in log

Additional info:
Linux localhost.localdomain 2.6.27.25-170.2.72.fc10.i686 #1 SMP Sun Jun 21 19:03:24 EDT 2009 i686 athlon i386 GNU/Linux
Comment 1 Robert Kochis 2009-06-28 11:44:03 EDT
Created attachment 349706 [details]
screenshot of directory
Comment 2 Robert Kochis 2009-06-28 12:08:05 EDT
Sorry, please cancel this bug.  The log file, at verbosity=3, only will have errors written to it.  My log file just had a couple of errors posted when root created files in my homedir but did not give access to the files.

I was suspicious that the log file was not being written to at all when the file was empty.
Thank you anyway, Bob
Comment 3 Kevin Fenzi 2009-06-28 12:52:50 EDT
No worries. ;) 

Feel free to reopen or file a new one if you spot anything further.

Note You need to log in before you can comment on or make changes to this bug.