In cases where multiple clients might map to the same fid you can also
freeze in a buffer file contents when the offset if zero, and serve from there
for further reads. Using 9p (and no cache in the client) means that you can use
the fid to mux the clients, and assign also a buffer per client, and
You mean that -A causes that panic, but -APW does not?
Otherwise it might be just that the fossil srv file mentioned in
/lib/ndb/vols is not
the one served by your fossil.
PS: Most of Spain is like that. We use to prefer the night, but don't
ask us to wake
up too early :)
On 8/8/07, Charles Fors
Hmm, I don't think so.
My laptop fossil runs -A, but not WP.
You can boot from the install CD, then you can
bind -b '#S' /dev
so you see your local disk,
and fossil/fossil -f /dev/sdC0/fossil (or your partition)
to mount your local fossil.
There are some fs check commands in the fossil conf. man page that
might help.
Did you overwrite the fossil conf you
Someone is using your mouse.
run ns to see what you got bound to /dev/mouse.
Also, see fd for your procs after cpu, that might tell you which one has it
open.
On 8/3/07, Sergio de Mingo <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I have a problem when I try to connect drawterm with a cpu server. Drawte
