On Tue, Mar 4, 2008 at 12:17 PM, Geoffrey <lists_at_serioustechnology.com> wrote:
> John Peacock wrote:
> > Geoffrey wrote:
> >>> Just wondering, but what do you need that info for?
> >>
> >> Just trying to figure out who the guilty party is. ;)
> >
> > If you weren't using shared working copies, you would know who the
> > guilty party was based solely on the output from 'svn log'.
>
> We are not using shared working copies. There are two folks who are
> permitted to update the production environment. To control this, they
> are in a unique group, thus updating the files can only be done if
> you're in this group. Each individual has their own working copies in
> their own development environment.
>
>
> > If you
> > simply must use a shared working copy (which is a bad idea from the get
> > go, but useful in certain limited circumstances), then you should make
> > the following changes:
> >
> > 1) remove all files from the directory ~/.subversion/auth/svn.simple on
> > the box that has the shared WC (I don't off the top of my head know
> > where that might be located on a Windows box);
> >
> > 2) edit the file ~/.subversion/config (ditto on location), and in the
> > section labeled [auth], uncomment this line (remove the # sign):
> >
> > store-passwords = no
> >
> > Now, every time someone commits, they will be forced to type their
> > username and password.
>
> It's not the committing of code were are trying to track. We know who
> committed the code. We are trying to figure out who executed the 'svn
> update' on the production machine.
Have you checked the system logs to see who was logged onto the server
when the update happened?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-03-04 18:22:50 CET