[Bug 120018] Re: vim can't open files under curlftpfs directory

[nils]

good ideas for testing. I just tried:

- Situation 1: create a directory (755), touch a file in it, then vi it, Result: E677, no backup file, no data in it.
- Situation 2: chmod the directory to 770, vi the file in the dir, E507, backup file exists, but no data in either file (the backup file being empty is OK since the orig file was empty)
- Situation 3,4: chmod the dir to 777 and try vi-ing the file and chmodding the file to 666 and trying the vi is the same as situation 2

a cp in that dir with 777 privs also gives the IO error, but the file is
created with the right content.

Anyone in the mood to write a perl or C test script that tries several
write-close-fsync combinations out to narrow down the problem? Funnily
enough kate writes the file but complains,and vi does not write and
complain... maybe a different order of when the backup is
created/written, or a bug in kate that writes the main file even if the
backup fails?

-- 
vim can't open files under curlftpfs directory
https://bugs.launchpad.net/bugs/120018
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