Jean-Claude,
This is fixed now; update to get this change:
2000-02-18 Karl Fogel <[EMAIL PROTECTED]>
* history.c (history_write): don't die if history file not
writable, just warn (unless `really_quiet') and skip out.
* main.c (main): don't bother checking if history file is
writable.
* server.c (serve_root): same.
Jean-Claude NOIRAUD <[EMAIL PROTECTED]> writes:
> Karl Fogel wrote:
>
> > Turns out it may be more complex than just checking `logoff' in
> > main.c, as I'm not sure the server would have gotten that option by
> > then, but I haven't yet looked enough to be sure...
>
> I did it but only tested it on direct access. I don't know how to install
> CVS in server mode.
>
> > [EMAIL PROTECTED] (Larry Jones) writes:
> > > I think so. Note that you could also allow anyone to write to just the
> > > history file (you don't have to allow them to write the whole tree),
>
> I don't think it's a good solution. I think only (Unix) group should have
> write access on it.
>
> > > ... or
> > > you could simply remove the history file entirely (CVS is happy with no
> > > history file, it just isn't happy with having one that isn't writable).
>
> Is it really a good solution ? Doesn't CVS use this file for 'history'
> command ?
