On Friday 14 September 2007 14:16:56 [EMAIL PROTECTED] wrote:
> in fact, you can do things with the server data even if the server
> process can not start. Look (in the archives?) for examples of "norton"
> usage.
# dir
total 73824
4 drwxr-xr-x 3 root root 4096 Sep 3 16:14 .
4 drwxr-xr-x 5 root root 4096 Sep 3 16:10 ..
65604 -rw-r--r-- 1 root root 67108864 Sep 13 21:22 data
8208 -rw-r--r-- 1 root root 8390144 Sep 14 00:00 log
4 drwxr-xr-x 3 root root 4096 Sep 3 17:20 vicepa
# norton log data 67108864
About to call RVM_INIT
open_log failed.
do_rvm_options failed
rvm_init failed RVM_EIO
Guess I'm totally out of luck here?
> Some important things for using Coda in production are:
>
> - to find out what kind of activities is incompatible with Coda
> (both because of fundamental limitations like write-sharing
> and also to avoid touching yet-buggy codepaths)
> - tolerant users who also can learn "donts" for the above reasons
That's what the test setup is for. At the moment I try to keep my address book
(KDE kontact) and bookmarks.xml (KDE konqueror) synchronised between 2
laptops that most of the time are simultaneously online. Under normal
circumstances this works flawless (thumbs up!), except when I forget to
authenticate on 1 on of them (reintegration issues that I am still not able
to repair) and now this (accidental) server crash.
Thx for your input!
M.
--
If 'but' was any useful, there would be a logic operator.
