Hello,
PyRPF shouldn't need you to have write access to the project directory,
but I wonder if this is the auto-backup kicking in?? If that is the
problem, then it should just print error messages on the console rather
than anything else. Or is it causing a more serious problem? I just
tried running PyRPF as another user and once I had managed to make my
project directory readable (!) it worked ok. (I had auto-backup off.)
Wayne
On Mon, 17 Dec 2012, Justin Lecher wrote:
> Hi,
>
> numerous modules in ccpn require write access to the project directory.
> When checking students projects I often don't have that right and run
> into errors (lately using pyrpf).
>
> Could you check before starting actions like e.g. PyRPF that the user
> has write access to the project directory?
>
> Thanks,
> Justin
>
>
> --
> Justin Lecher
> Institute of Complex Systems
> ICS-6 Structural Biochemistry
> Research Centre Juelich
> 52425 Juelich, Germany
> phone: +49 2461 61 2117
>
>
>
|