On Wed, Feb 20, 2013 at 4:59 PM, Stephan Beal <[email protected]> wrote:
> On Wed, Feb 20, 2013 at 10:44 PM, Arnel Legaspi <[email protected]>wrote: > >> Error: not authorized to writet: 0 received: 0 >>> >> > The "not authorized to writet" does not come from fossil: > > stephan@tiny:~/cvs/fossil/fossil/src$ grep writet *.c > stephan@tiny:~/cvs/fossil/fossil/src$ grep 'not authorized' *.c > sqlite3.c: sqlite3ErrorMsg(pParse, "not authorized to use > function: %s", > sqlite3.c: sqlite3ErrorMsg(pParse, "not authorized"); > sqlite3.c: *pzErrMsg = sqlite3_mprintf("not authorized"); > xfer.c: /* Do not accept private files if not authorized */ > xfer.c: /* Do not accept private files if not authorized */ > > :-? > I thought so to. But in fact it does. It is just that the message is encoded: drh@tallis:~/fossil/m1/src$ grep 'not..authorized' * xfer.c: @ error not\sauthorized\sto\ssync\sprivate\scontent xfer.c: @ error not\sauthorized\sto\swrite xfer.c: @ error not\sauthorized\sto\swrite xfer.c: @ error not\sauthorized\sto\sread xfer.c: @ error not\sauthorized\sto\swrite xfer.c: @ message pull\sonly\s-\snot\sauthorized\sto\spush xfer.c: @ error not\sauthorized\sto\sclone xfer.c: @ error not\sauthorized\sto\spush\sconfiguration -- D. Richard Hipp [email protected]
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
