> You can also run the svnserve daemon on demand (via launchd) which > consumes less resources if you're accessing the repository > infrequently. Sorry I don't have answers for the rest of the > problem... > - Quinn > That is correct I use exactly that a launchd process for on demand usage of svnserve. Some of my repos (my personal projects) are located on a machine with tiger server running on it.
I can post the launchd file as an attachment here if that helps? Also the setup of the launchd can be finicky so i have found the Lingon is a great tool (seperate versions for tiger and leopard) for managing user launchd processes. There is a slightly different launchd for leopard as there is a svnuser or similar user builtin to leopard now whereas there wasnt in tiger. Google is very helpful with finding this variant. one last thing unless you setup your hosts file you will have to login to the machine with the repository via its local IP Regards Kieren > On May 19, 2009, at 6:15 PM, Kez wrote: > >> >> Im not sure if this will help.... >> >> I had a similar issue when committing to a repos on my local network >> shared via AFP, As you said I could checkout and view but not commit. >> it would seem to be something in the way that svn is translated over >> the afp link in my case >> >> I worked around this by setting up a svnserve daemon to run at >> startup >> on the repository machine which fixed the problem. >> >> hth >> >> Kieren >> >> On 20/05/2009, at 2:32 AM, Thinsoldier wrote: >> >>> >>> I'm having the same thing happen on my network. I emailed versions >>> support but they just pointed me here :( >>> >>> On May 7, 10:06 am, Heiko Weber <he...@wecos.de> wrote: >>>> Hi Richard, >>>> >>>> I get this error too, but it isn't related to Version, if I use svn >>>> in >>>> a shell, like "svn commit", I'll get it too. >>>> >>>> Heiko >>>> >>>> On May 6, 10:31 pm, Richard Testani <sand...@gmail.com> wrote: >>>> >>>>> I'm getting an error when I try and commit. >>>> >>>>> I checked out a working copy from a repository on a local network >>>>> (another Mac) >>>>> In my first session, I was able to commit perfectly fine. >>>> >>>>> In my second session, I am getting an error when I commit to this >>>>> volume: >>>> >>>>> Commit failed (details follow): >>>>> Can't get exclusive lock onfile'/Volumes/Macintosh HD-1/Users/ >>>>> Shared/ >>>>> svn/svn_repos/db/transactions/6-1.txn/rev-lock': Operation not >>>>> supported >>>> >>>>> I'm not really sure why this is - Im rather new to SVN, but we >>>>> are >>>>> managing files on a network and Versions works nice when working >>>>> on >>>>> your own machine. >>>> >>>>> Any help with this would be great. >>>>> All computers are running Leopard. >>>>> Rich >>>> >> >> >> >> > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Versions" group. To post to this group, send email to versions@googlegroups.com To unsubscribe from this group, send email to versions+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/versions?hl=en -~----------~----~----~----~------~----~------~--~---
