Nick,
-----Original Message-----
From: Nick Levine [mailto:ndl at ravenbrook.com]
Sent: den 22 april 2004 09:40
To: perforce-user at perforce.com
Cc: ndl at ravenbrook.com
Subject: Re: [p4] preventing anonymous user from messing with
their password
Re:
What about tailing or grepping the journal file watching for any
password update for anonymous user. If you see any activity, then
you reset it to what you want via a superuser.
Thanks for the reply (also to those who replied privately).
All suggestions received were basically the same.
I guess I was hoping for a simpler solution, some flag buried
in the documentation which I might have overlooked. Given my
options, I think what I'll do is play King Log - probably a
whole load less work and certainly allows me to stay focussed
on greater priorities.
As I understand the Open Source license (after a cursory glance), you don't
_need_ to have a user named 'anonymous' - you can provide Perforce with a
special, password-protected, read-only user as long as you tell them about
it. Is there any other reason you need an anonymous user without password?
// Johan