[Bug 361214] [NEW] conduit stops with no error when illegal file name encountered

[John at vosslers.net]

Public bug reported:

Binary package hint: conduit

Conduit will simply stop at xx% synchronized and never make any progress
when attempting to sync a file to another system where the file name is
illegal.

In my case I had file names that contained a colon ":" and other special
characters.  While these file names are perfectly fine on Ubuntu and all
other forms of *nix that I use, they are illegal on the windows system a
colleague uses.

I think that the synchronization process should generate some type of
error indicating what file it stopped on and then the sync should fail.

I took several hours for me to narrow down the exact directory conduit
was stopping at and once I attempted to copy over the files manually I
understood the issue.  The file names were altered (they contained a
time stamp with a colon) and the sync worked correctly.

The sync was set up between my Ubuntu system and his "folder" that is
NFS mounted to my system.  It is NFS since the windows system is running
SFU (Services For Unix).

I am running Conduit 0.3.6 on Ubuntu 8.05 LTS

** Affects: conduit (Ubuntu)
     Importance: Undecided
         Status: New

-- 
conduit stops with no error when illegal file name encountered
https://bugs.launchpad.net/bugs/361214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs at lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs