Re: Two svn/apache servers accessing one database

[Ulrich Eckhardt]

On Saturday 05 June 2010, Richard England wrote:
> Are there any possible repercussions of having two server both running
> Apache/SVN (same version)  accessing the same database files?  This is
> using FSFS.
>
> Is this likely to cause data corruption or anything nasty?

You can easily have multiple concurrent accesses even without running two 
Apaches, e.g. concurrent file accesses by different users on the same 
machine, different svn+ssh sessions, multiple svnserve instances spawned by 
[x]inetd etc.

In other words, it works.

Uli

-- 
ML: http://subversion.tigris.org/mailing-list-guidelines.html
FAQ: http://subversion.tigris.org/faq.html
Docs: http://svnbook.red-bean.com/

Sator Laser GmbH, Fangdieckstraße 75a, 22547 Hamburg, Deutschland
Geschäftsführer: Thorsten Föcking, Amtsgericht Hamburg HR B62 932

**
Sator Laser GmbH, Fangdieckstraße 75a, 22547 Hamburg, Deutschland
Geschäftsführer: Thorsten Föcking, Amtsgericht Hamburg HR B62 932
**
   Visit our website at 
**
Diese E-Mail einschließlich sämtlicher Anhänge ist nur für den Adressaten 
bestimmt und kann vertrauliche Informationen enthalten. Bitte benachrichtigen 
Sie den Absender umgehend, falls Sie nicht der beabsichtigte Empfänger sein 
sollten. Die E-Mail ist in diesem Fall zu löschen und darf weder gelesen, 
weitergeleitet, veröffentlicht oder anderweitig benutzt werden.
E-Mails können durch Dritte gelesen werden und Viren sowie nichtautorisierte 
Änderungen enthalten. Sator Laser GmbH ist für diese Folgen nicht 
verantwortlich.
**

Locking a repository

[Ulrich Eckhardt]

Hi!

I have a BDB repository where the nightly backup threw up a "fatal region 
error". In order to resolve that, I wanted to try to recover the database.

First thing I noticed, and which already confused me in the paths, was that 
the error tells you to "run database recovery" but "svnadmin recover" is (I 
believe) not the right tool but "db4.6_recover" from the BDB tools is. At 
least "svnadmin recover" runs without any issues, but "svnadmin verify" still 
produces errors.

The next thing I wondered was how I can lock the whole repository while 
running db4.6_recover on the database. "svnadmin" does it, e.g. the "recover" 
function bails if there is a hung "svnserve" process keeping it from an 
exclusive lock, but how can I do so manually?

Also, do I actually have to lock the database at all or can I just run 
db4.6_recover on it without?

Thanks!

Uli

-- 
ML: http://subversion.tigris.org/mailing-list-guidelines.html
FAQ: http://subversion.tigris.org/faq.html
Docs: http://svnbook.red-bean.com/

Sator Laser GmbH, Fangdieckstraße 75a, 22547 Hamburg, Deutschland
Geschäftsführer: Thorsten Föcking, Amtsgericht Hamburg HR B62 932

**
Sator Laser GmbH, Fangdieckstraße 75a, 22547 Hamburg, Deutschland
Geschäftsführer: Thorsten Föcking, Amtsgericht Hamburg HR B62 932
**
   Visit our website at 
**
Diese E-Mail einschließlich sämtlicher Anhänge ist nur für den Adressaten 
bestimmt und kann vertrauliche Informationen enthalten. Bitte benachrichtigen 
Sie den Absender umgehend, falls Sie nicht der beabsichtigte Empfänger sein 
sollten. Die E-Mail ist in diesem Fall zu löschen und darf weder gelesen, 
weitergeleitet, veröffentlicht oder anderweitig benutzt werden.
E-Mails können durch Dritte gelesen werden und Viren sowie nichtautorisierte 
Änderungen enthalten. Sator Laser GmbH ist für diese Folgen nicht 
verantwortlich.
**

Client side security

[Owen, Sean]

Is there anyway, y'all know of, to secure the client side of an SVN check out?

Sean Owen
Senior Lab Manager- FAE America
AMD Austin
Mail stop B300.1A.021
Office - 512.602.7593 or X57593
Mobile - 830.743.9697
sean.o...@amd.com

Re: Client side security

[Pat Farrell]

On 06/08/2010 11:55 AM, Owen, Sean wrote:

Is there anyway, y'all know of, to secure the client side of an SVN
check out?


Do you mean like running OS-X or Linux rather than Windows?

Or do you mean more like removing the keyboard so that the user 
operating the client can't do insecure things?



--
Pat Farrell
http://www.pfarrell.com/

RE: Client side security

[Owen, Sean]

No I'm look for software that runs on windows that provides encryption for and 
SVN folder without too much overhead.

Sean

-Original Message-
From: Pat Farrell [mailto:pfarr...@pfarrell.com] 
Sent: Tuesday, June 08, 2010 11:09 AM
To: users@subversion.apache.org
Subject: Re: Client side security

On 06/08/2010 11:55 AM, Owen, Sean wrote:
> Is there anyway, y'all know of, to secure the client side of an SVN
> check out?

Do you mean like running OS-X or Linux rather than Windows?

Or do you mean more like removing the keyboard so that the user 
operating the client can't do insecure things?


-- 
Pat Farrell
http://www.pfarrell.com/

Re: Client side security

[Andy Levy]

On Tue, Jun 8, 2010 at 12:16, Owen, Sean  wrote:
> No I'm look for software that runs on windows that provides encryption for 
> and SVN folder without too much overhead.

There is nothing special WRT Subversion here aside from the fact that
you'll need to encrypt the whole folder, without the ability to
encrypt individual files. Use whatever you would use for any other
kinds of files - a TrueCrypt volume, full disk encryption, Windows
Crypto, etc.

> -Original Message-
> From: Pat Farrell [mailto:pfarr...@pfarrell.com]
> Sent: Tuesday, June 08, 2010 11:09 AM
> To: users@subversion.apache.org
> Subject: Re: Client side security
>
> On 06/08/2010 11:55 AM, Owen, Sean wrote:
>> Is there anyway, y'all know of, to secure the client side of an SVN
>> check out?
>
> Do you mean like running OS-X or Linux rather than Windows?
>
> Or do you mean more like removing the keyboard so that the user
> operating the client can't do insecure things?
>
>
> --
> Pat Farrell
> http://www.pfarrell.com/
>
>
>
>

Re: Two svn/apache servers accessing one database

[Andy Levy]

On Fri, Jun 4, 2010 at 19:41, Richard England
 wrote:
> Are there any possible repercussions of having two server both running
> Apache/SVN (same version)  accessing the same database files?  This is using
> FSFS.

What are your reasons for wanting to do so?

> Is this likely to cause data corruption or anything nasty?

It's not supposed to, but weird things are always possible. Plus, both
servers will need to be identical in other ways so that your hook
scripts can run properly.

RE: svnserve Windows Service and iSCSI disk does not start after reboot

[Keith Moore]

> -Original Message-
> From: Keith Moore 
> Sent: Monday, 7 June 2010 3:47 PM
> To: users@subversion.apache.org
> Subject: svnserve Windows Service and iSCSI disk does not start after reboot
>
> Hello,
>
> I have a physical (not virtual) Windows Server 2003 box set up with 
> svnserve.exe running as an auto start windows service.  svnserve starts with 
> the following command line.
>
> "\svnserve.exe" --service -r "D:\Repositories" --listen-port "3690" 
> --log-file "C:\Logs\svnserve.log"
>
> The repositories are on a SAN (that is D: drive is on the SAN) that the box 
> links to using iSCSI.  When the [Windows] server is restarted the svnserve 
> service attempts to start but fails with an error "The Subversion Server 
> service failed to start due to the following error: The service did not 
> respond to the start or control request in a timely fashion."
>
> However, if I wait for windows to boot fully and then manually start the 
> service it works.
>
> If I change the repository root to the C: drive, which is a physical disk on 
> the server, the service starts normally on a reboot.  I'm guessing that I 
> need to make the svnserve service dependent on some other service/device but 
> I can't work out which one.
>
>
> Does anyone have any experience with this type of setup and/or can anyone 
> offer suggestions as to how I can ensure that the svnserve service starts 
> normally when the server is rebooted?
>
> Thanks.
> Keith Moore.

If anyone is interested, the way to solve this on windows is to make the iSCSI 
drive a "bound volume".  It is a configuration option for the iSCSI driver.  If 
you make a drive a bound volume then the operating system (iSCSI driver) will 
not continue until the drive/volume is fully initialized.

After this the svnserve.exe service started normally after a reboot.

Keith.

#
Attention:
The information contained in this message and or attachments is intended
only for the person or entity to which it is addressed and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination or other use of, or taking of any action in reliance upon,
this information by persons or entities other than the intended recipient
is prohibited. If you received this in error, please contact the sender and
delete the material from any system and destroy any copies.
#