[03:56] <calc> anyone around that remembers how to put gvfsd into debug mode?
[03:56]  * calc needs to debug gvfs fuse ftp
[03:56] <calc> it seems that gvfsd doesn't tell you which arg does it when running --help
[04:35] <JanC> calc: maybe the commandline tools give more info?
[04:35] <calc> JanC: i think i got it to debug ok
[04:36] <JanC> e.g. gvfs-mount
[04:36] <calc> JanC: i found that vsftpd appears to be buggy as well
[04:36] <JanC> ah , okay
[04:36] <calc> which is causing OOo not to save to it either
[04:36] <JanC> ow?
[04:36] <calc> when OOo writes a file to gvfs fuse connected to vsftpd it does not return ftp code 150 after STOR
[04:36] <calc> eg
[04:36] <calc> --> STOR /home/ccheney/Desktop/.~lock.test-ftp.odt#
[04:36] <calc> <-- 150 Ok to send data.
[04:36] <calc> --> NOOP
[04:36] <calc> <-- 200 NOOP ok.
[04:37] <calc> if i touch a file in the dir it does though, so it seems very odd
[04:37] <calc> i'll have to beat on it a bit with a test program to see if i can find out why its sometimes not returning 150
[04:38] <JanC> sounds like something you could debug using a packet sniffer anyway
[04:38] <JanC> yay, for FTP being unsecure  :P
[04:39] <calc> yea, the gvfsd -r works i just didn't restart the share properly before it seems
[05:42] <calc> gah
[05:42] <calc> gvfs ftp backend is stupid
[05:42] <calc> it doesn't seem to even understand the ftp spec
[05:43] <calc> i'm surprised saving to ftp works at all