I'm having trouble mounting using the fstab/.netrc combination. If I use the normal command line interface it works fine:
$ curlftpfs ftp://user:pass@server mountpoint
I'm not sure where I have to keep my .netrc, but it doesn't work in the user home nor in the root home (I put the same file in both for testing). And I double-checked that the server/user/password settings are the same in the CLI parameters and .netrc/fstab. Any pointers on this are greatly appreciated!
$ ls -l ~/.netrc
-rw------- 1 torf torf 59 Jul 1 14:23 /home/torf/.netrc
$ cat ~/.netrc
$ su -c "ls -l /root/.netrc"
-rw------- 1 root root 59 Jul 1 14:25 /root/.netrc
(Content of /root/.netrc is the same as in ~)
$ grep curlftpfs /etc/fstab
curlftpfs#server mountpoint fuse rw,uid=500,user,noauto 0 0
$ su -c "lsmod | grep fuse"
fuse 39188 2
$ mount mountpoint
Error connecting to ftp: Access denied: 530
If you set it to noauto and don't mind typing your password every time, you can use "user=youruser":
curlftpfs#server mountpoint fuse rw,uid=500,user,noauto,user=youruser 0 0
It will ask for your password. Be aware that if try to mount it during boot, it will hang waiting for you to enter the password.
Using user=ftpusername in fstab works. I'd still prefer using .netrc, though. Is there a way to enable logging/verbose output when using fstab? Or do you got any other ideas on how to search for the error?
$ curlftpfs -V
curlftpfs 0.9.1 libcurl/7.16.3 fuse/2.5
The problem is that the mount script changes the user to your user but looks for the .netrc in $HOME, which still points to /root. I can add a parameter to curlftpfs to specify the .netrc, but you'd have to pointer to a specific directory, not a user dependent one.
>>The problem is that the mount script changes the user to your user but looks for the .netrc in $HOME, which still points to /root.
Isn't that considered a bug? Are fuse devs aware of this feature/bug?
Log in to post a comment.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.