Bug 316571 - Dirvish can't be used by non-root user
Dirvish can't be used by non-root user
Product: Fedora
Classification: Fedora
Component: dirvish (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Robert Marcano
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-10-03 05:39 EDT by Mads Kiilerich
Modified: 2008-05-14 17:44 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-05-14 17:00:54 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Mads Kiilerich 2007-10-03 05:39:12 EDT
Description of problem:
Dirvish is in /usr/bin and can be run by any user. Some options can however only
be specified in /etc/, making it unusable for normal users. IMHO solving that
qualifies as a bug more than a feature request.

The dirvish commands doesn't use options consistently:
* dirvish has --config option but requires /etc/dirvish/master.conf (may be
empty, not included in rpm)
* dirvish-runall has --config option which causes /etc/dirvish/master.conf to
NOT be read
* dirvish-expire has no --config option

* dirvish-expire has no --vault option, so only "all globally defined vaults"
can be expired, no detailed control possible.

Desired/suggested behaviour:
* dirvish should have a --runall option replacing dirvish-runall
* dirvish should have a --expire option replacing dirvish-expire

Version-Release number of selected component (if applicable):
dirvish-1.2.1-2.fc6 - which seems to be last release from a dead upstream :-(
Comment 1 Bug Zapper 2008-05-14 10:36:37 EDT
This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '7'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 7's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 7 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug. If you are unable to change the version, please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists.

Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs:

The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 2 Mads Kiilerich 2008-05-14 17:00:54 EDT
I realize that dirvish just isn't mature enough to be packaged properly.
Unfortunately development of dirvish seems to have stopped, and this feedback
won't help.

Comment 3 Robert Marcano 2008-05-14 17:44:08 EDT
As a user of dirvish I can tell you that it really requires root privileges to
work, for example to store file ownership since it saves the backups with the
same ownership of the original file, and if you are backing up remote machines
it is recommended to have a central user database (NIS, LDAP, etc) to make sure
the correct ownership is assigned to the backup files.

I do not think dirvish was designed to be used by normal users. Dirvish
development as you say is dead, there is a experimental release for years, but I
packaged the stable release since that is what I use on my servers and as a
backup tool I do not recommend using the experimental version

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