arla-0.90 on linux-2.6.19 (debian)

[Niels Möller]

Tomas Olsson <tol at it.su.se> writes:

> Try running arlad with --tracefile=tracefile, the message trace is very
> helpful if it happens again.

Hmm, now I've edited the start script to use

  run_program $ARLABINDIR/arlad -z --tracefile=/home/arla/msg.trace
               
and I've made a couple of AFS accesses, but I get no file
/home/arla/msg.trace. Should I use a file name relative to the cache
root dir (where arlad chroots?), or how is this supposed to work?

Regards,
/Niels