From: Alberto Cortes <alcortes@coitt.es>
To: 9fans <9fans@cse.psu.edu>
Subject: [9fans] losing files with ftpfs(4)
Date: Tue, 7 Sep 2004 23:11:08 +0200 [thread overview]
Message-ID: <20040907211108.GA1687@shire> (raw)
I have an ftp server (no plan9 host), it serve some files and
directories.
When a client connects to my ftp server it shows a write protected
directory containing some readable files and some writable
directories.
If i ftpfs to it and try to "mv" a file to the mount point (write
protected) this happens:
term% ftpfs -m /usr/glenda/ftp -a xxxx@yyyyy.com 172.26.0.4
220 ProFTPD 1.2.5rc1 Server (Debian) [shire]
331 Anonymous login ok, send your complete email address as your password.
230 Anonymous access granted, restrictions apply.
215 UNIX Type: L8
257 "/" is current directory.
term% mv foo ftp/
226-Transfer complete.
ftpfs: couldn't create file
Which is quite annoying as i find myself with no "foo" file on the ftp
server (that's OK) AND no "foo" file on my plan9 side (which is
certainly not OK).
Is this the expected behaviour of ftpfs ?
Could it be that "ftpfs" isn't checking for permission before saying
"mv": "i can handle this, just finish your work" ?
sorry for not tracking the problem much more but i am not very
experienced with this things.
--
http://montoya.aig.uc3m.es/~acortes/index.html
next reply other threads:[~2004-09-07 21:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-07 21:11 Alberto Cortes [this message]
2004-09-07 21:41 ` Russ Cox
2004-09-07 22:03 ` boyd, rounin
2004-09-07 23:07 ` jmk
2004-09-07 23:09 ` boyd, rounin
2004-09-08 1:53 ` Joseph Holsten
2004-09-08 2:32 ` Russ Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040907211108.GA1687@shire \
--to=alcortes@coitt.es \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).