Arch Linux: FSI is not working because portmap is replaced by rpcbind
Hey,
I switched to Arch Linux for a few days and wuala works fine unless the filesystemintegration is not working.
By doing some research in GS it is a problem causing by rpcbind instead of portmap.
While you could solve it easily in opensuse by removing rpcbind an installing portmap, in Arch Linux portmap is replaced by rpcbind and new nfs-utils. That means portmap is no longer available.
http://www.archlinux.org/news/452/
I get the typical log:
Debug log initialized
Starting server Mount ...
Starting server NFS ...
Is there a workaround for this?
I switched to Arch Linux for a few days and wuala works fine unless the filesystemintegration is not working.
By doing some research in GS it is a problem causing by rpcbind instead of portmap.
While you could solve it easily in opensuse by removing rpcbind an installing portmap, in Arch Linux portmap is replaced by rpcbind and new nfs-utils. That means portmap is no longer available.
http://www.archlinux.org/news/452/
I get the typical log:
Debug log initialized
Starting server Mount ...
Starting server NFS ...
Is there a workaround for this?
2
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Hey posativ,
I ́m helpless too. As far as I know, there is no workaround for that except try to use the -noportmapregistration that is described in the faq.
"If there is already another NFS server running on your computer, you can avoid conflicts by starting Wuala with the option -noportmapregistration that lets Wuala skip registering its server with the portmapper. In that case, you need to add additional mount parameters in the /etc/fstab entry:
nfsvers=3,mountvers=3,port=26184,mountport=26183"
s
I’m hope it is working
2 people say
this solves the problem
-
Inappropriate?Hi bagelcat,
thanks for your reply. Did try the same the yesterday.
But it was my fault it was not working:
I had edit the wrong wuala start script...
You can untar wuala somewhere and start in from that location. But it will nevertheless install automatically to /home/$USER/wuala.
So editing the script in e.g. /home/MyApplications/wuala has no effect. -
Inappropriate?I got around this problem by modifying my "/etc/rc.d/rpcbind" script; it now supplies the '-i' argument to 'rpcbind'.
I’m confident
Loading Profile...




EMPLOYEE
