instead of immediately backgrounding, have the client background after initial messages.
Similar for later "controlling" wuala instances, don't exit or background until the command completes (or fails) or all output has been sent (in case of logins if that is handled as a non-terminating command)
Linux version should notice that the arguments are commands and ALWAYS try to connect to previous instance. If no such instance exists it should give an error such as "Wuala is not currently running."
The current behavior is to try to start another instance. This causes problems if you are using nogui and nomount and basepath to start wuala, If wuala isn't running it tries to start and fails.
follow wuala install instructions for linux, then when starting the client, do:
./wualacmd
(wuala starts, updates to current revision)
./wualacmd help
(wuala connects to running instance which displays help output)
./wualacmd login username password
(ofcourse use real user name and real password)
(Does just return to command line)
ps auwxf
(shows 2 java processes with wuala, one with the login command line, one without)
this state doesn't change for several minutes unless TERM signal sent to java process.
if wuala is not terminated every other command results in "socket already in use"
see also "Configuring wuala on headless linux server impossible"
I'm using wualacmd under CentOS and I'm having problems accessing a file on this host (it seems to work fine from others).
When I try to cat the file from the NFS mount I get error "Input/output error" and in the client a few seconds later it gives "Wuala>Problem: java.io.FileNotFoundException: /home/wuala_mnt/wuala/wuala/Data/Local2/Large/979CAC0490BD16645B30A41ADA4671554AF0FF6C"
Hmm. Mir ist die letzten drei Tage etwas aufgefallen, dass ein Bug sein köe..
Wuala scheint nach einem restart nur einige Stunden lang Daten in den Fragment2 Ordner zu laden. Lasse ich wuala durchlaufen, zeigt die aktuellste Datei irgendwann eine Changetime so zwischen 6 und 12 Stunden nach den Neustart von Wuala an. Danach werden augenscheinlich keine weiteren Daten mehr geladen.
Gleichzeitig bleibt die Onlinezeit "still stehen". Das Teil lät auf nem rootserv und ist daher immer an, wenn es nicht abstü:) Es ist 2 Tage nach meinem Heimsystem installiert worden. Auf dem linux-System sind nun (seit ca. 3 Tagen in denen ich darauf achte gleichbleibend) 54%. Mein Heimsystem ist bereits bei 68%...
Da stimmt was nicht..
Ich hab mal heute stopTrading/Start Trading eingegeben (ein Tipp aus einem anderen Thread). Mal schaun, ob das etwas bringt. Aber habt bitte mal ein Auge von der Entwicklerseite her darauf.
So I am an active linux developer who has spotted some very cool possibilities for Wuala. Right now, the problem is, I can't access any of the awesome! While I understand fully that preping an API for the public is a lengthy process, could you just offer a simple dbus/com service. An undocumented client library would rock too. Or even just making the mounted filesystem support 'query directories' etc. I'm not picky, I just want to harness a universally available and decentralized file store for some collaborative apps (non-realtime of course) . Specifically any DRCS (or even subversion to a degree) would love this.
When I double-click on an image or video, the download starts right away, but when the download is done sometimes the file isn't opened. I have to double-click again (or select open from the context menu) to open the file. Sometimes it works on the first try. I'm using KDE.
Loading Profile...
