[Box Backup-commit] #33: "Failed to setup location" problem

[boxbackup-dev@fluffy.co.uk]

#33: "Failed to setup location" problem
----------------------+-----------------------------------------------------
 Reporter:  petej     |       Owner:  ben 
     Type:  defect    |      Status:  new 
 Priority:  major     |   Milestone:      
Component:  bbackupd  |     Version:  0.10
 Keywords:            |  
----------------------+-----------------------------------------------------
 From thread:
 http://lists.warhead.org.uk/pipermail/boxbackup/2007-July/003668.html
 (Client chris_general_1692; we also tried 1662, and got similar errors,
 albeit with slightly different Windows Service crashing behavior.  We're
 not sure if there is something funky about the mapped shares [we don't
 think so, as we tried some very simple shares as well] or something with
 the Box Backup.)

 I think that with !ExtendedLogging = yes, Box Backup should report into
 the log the FULL PATH of each file or directory IMMEDIATELY BEFORE it
 works on it, to help diagnose problems when such files or directories
 cause failures.

 Exceptions/errors, such as OSFileError for example, should report which
 file or directory had the problem, and what the problem is, something like
 "Not writeable".

 (Should/Can "Failed to setup location" report why it failed, or at least
 report the current values of some relevant variables?)

 I'm setting this bug to major priority because it (needing the full path)
 is a recurring issue and would be so helpful as Box Backup works it's way
 from 0.10 to 1.0.

 Thanks,
 Pete

-- 
Ticket URL: <http://bbdev.fluffy.co.uk/trac/ticket/33>
Box Backup <http://www.fluffy.co.uk/boxbackup/>
An open source, completely automatic on-line backup system for UNIX.