using PSexec to remotely run svnserver
Hello, I'm using Subversion in a windows shop. We have a FSFS repository that we're accessing via XP's filesharing (file: URLs with UNC paths). Company policy won't allow us to install ssh/sshd, or to run any new services such as apache or svnserver as a deamon. We have PSexec installed on our svn clients, and as we already trust our windows authentication & security setup, I was thinking we could use that as a sort-of "rsh" replacement. The thing is, every variation I try hangs. psexec prints a banner to STDERR which I can't turn off. I can redirect it to NUL. psexec also seems to buffer its output. I'm not sure about that. What I do know is that wrapping it up in a batch script fails. Here are some test runs: > psexec \\reposerve svnserve -t 2>NUL ( success ( 2 2 ( ) ( edit-pipeline svndiff1 absent-entries commit-revprops dept h log-revprops partial-replay ) ) ) that looks good! On the other hand a batch file that says: c:\DOCUME~1\ALLUSE~1\DOCUME~1\PStools\psexec.exe -e \\%* 2>NUL and setting %SVN_SSH% to point to the batch file- > svn list svn+ssh://reposerve/D/repository/trunk (hangs) - I would expect an error or success, instead it just hangs, psexec keeps running but no input/output If anyone has had success running subversion's server via PSexec, please share your recipe! thanks -y
Re: using PSexec to remotely run svnserver
>You should stop doing so immediately and set up a proper server. Any user >with direct file:-protocol access to the repository can access any part of it >(bypassing any path-based security you've put in place) and can even delete >the entire repository (accidentally or intentionally). What you are describing is considered a feature in our environment. Anyone with file system access on the server has utilmate trust. If you wish to lecture me, please mail me directly. If you wish to answer the original topic, then email the list.
Re: using PSexec to remotely run svnserver
>Additionally, the Subversion development team has announced file:// >protocol should not be considered for production environments. Reread OP then, I'm trying to get away from using a file:// URL, using PSexec to execute svnserver.
How to build with http/https: access via serf, and not neon?
Hello, I've retrieved the /subversion-1.6.11 tarball from http://subversion.tigris.org/downloads/subversion-1.6.11.tar.bz2 . I can configure and build it with serf- eg configure: serf library configuration checking serf.h usability... yes checking serf.h presence... yes checking for serf.h... yes checking for serf_context_create in -lserf-0... yes The build proceeds error-free, but after I install and run it, I don't have http access- $ svn ls http://anywhere.example.com svn: Unrecognized URL scheme for 'http://anywhere.example.com' $ svn --version svn, version 1.6.11 (r934486) compiled May 31 2010, 16:03:27 Copyright (C) 2000-2009 CollabNet. Subversion is open source software, see http://subversion.tigris.org/ This product includes software developed by CollabNet (http://www.Collab.Net/). The following repository access (RA) modules are available: * ra_svn : Module for accessing a repository using the svn network protocol. - handles 'svn' scheme * ra_local : Module for accessing a repository on local disk. - handles 'file' scheme Here's the config & sys info- $ uname -a OpenBSD pinky.yary.ack.org 3.9 GENERIC#617 i386 $ ./configure '--with-apr=/usr/local/apr/bin/apr-1-config' '--with-apr-util=/usr/local/apr/bin/apu-1-config' '--with-serf=/usr/local/serf' '--enable-runtime-module-search' '--with-apxs=/usr/local/apache2/bin/apxs' '--with-berkeley-db' '--without-neon' I have different apache2's installed, the apr, apu, and apxs listed are all from the same build. One thing that's a little odd, even with the "--without-neon" line, configure still complains: configure: checking neon library An appropriate version of neon could not be found, so libsvn_ra_neon will not be built. If you want to build libsvn_ra_neon, please either install neon 0.29.0 on this system or get neon 0.29.0 from: http://www.webdav.org/neon/neon-0.29.0.tar.gz unpack the archive using tar/gunzip and rename the resulting directory from ./neon-0.29.0/ to ./neon/ no suitable neon found -y
Re: How to build with http/https: access via serf, and not neon?
Neon is required? The INSTALL that comes with 1.6.11 says that either neon or serf will give http access: * libneon or libserf (OPTIONAL for client) The Neon and Serf libraries both allow the Subversion client to send HTTP requests. ... Your client can be compiled against either libneon or libserf (or both), as they offer competing implementations. -y
Re: How to build with http/https: access via serf, and not neon?
Hi Campbell, I can build a working binary as well, it's just that the client doesn't have the http: method when built with only serf and "--without-neon". It sounds like you're building it with neon in each cases, just not using the "--with-neon" flag; omitting the flag makes configure look for it in the default places. Have you tried building using "without-neon", if so can you verify that yours shows http when you run "svn --version"? I'm wondering if this is simply a documentation bug, that neon is always required in some respect. -y
Re: Perl API SVN::Ra::get_commit_editor2 causes TypeError
Just a stab in the dark, what version of Subversion do you have on that box? It looks like this perl module comes bundles with Subversion 1.4 and some users have complained that it doesn't first check to see if there is a subverison installed for it to use. It also looks like that module was last updated in 2007. So perhaps it isn't good for production use :-( If you really do need SVN::Core working, you might need to compile it from source and not use a distro. I haven't used that module myself though and am not even sure that is the issue. Depending on your needs, this may work- http://search.cpan.org/~karman/SVN-Class-0.16/lib/SVN/Class.pm SVN::Class uses your svn binary to reduce dependencies. It was last updated a couple months ago, and looks like it has a clean syntax. -y
