Hi Daniel, Thanks for the feedback. As I responded to Ryan, the directory exists and the log file is being written to.
I'll look at moving the location. Appreciate the advice on that. "You can avoid this by throwing a mutex around the svn(1) call (see flock(1))." Being that I'm pretty new to subversion, you lost me here. Greg -----Original Message----- From: Daniel Shahaf [mailto:d...@daniel.shahaf.name] Sent: Saturday, March 09, 2019 7:22 AM To: Ryan Schmidt; Fairchild, Gregory J - OASAM OCIO CTR Cc: Subversion Users Subject: Re: svn:E155007:None of the tarets are working copies Ryan Schmidt wrote on Sat, 09 Mar 2019 08:43 +00:00: > On Mar 8, 2019, at 14:24, Fairchild, Gregory J - OASAM OCIO CTR wrote: > > Post-commit looks like this: > > #!/bin/sh > > REPOS="$1" > > REV="$2" > > /usr/bin/svn update /var/apache2/2.4/htdocs/ >> > > /rpool/svn/subversion/repository/logs/post-commit.log > > > > Any help will be appreciated. Thanks > > The first question I would ask is: Does the directory > /rpool/svn/subversion/repository/logs exist? If not, create it. That should solve the immediate problem, but you should plan to move that directory to another place. /rpool/svn/subversion/repository is a repository, so you shouldn't create files or directories under it except those specifically described in the documentation, for forward compatibility with future versions of Subversion (which may start using $REPOS_DIR/logs/ in some way or another). While I'm here, let me point out that post-commit runs for different revisions may happen in parallel or even out of order. In this case, the worst that could happen is that the svn(1) invocation in the second run will error out with E155004 and the error will be marshalled back to the user who committed. You can avoid this by throwing a mutex around the svn(1) call (see flock(1)). Cheers, Daniel
