We have a system that sometimes leaves stray subversion locks laying
around and are trying to clean those up. I'm getting the warning
mentioned in the subject and attempted tho workaround mentioned in
http://cfengine.org/pipermail/help-cfengine/2010-February/007638.html.
But in my case its not enough, I am assuming its because the
wildcarding is at the grandparent directory level, but I'm at a loss
as to how to work around it.
files:
no_svn_running::
"$(dir_projects)/.*/\.svn/."
depth_search => recurse(1),
file_select => by_name("lock"),
delete => tidy;
processes:
"svn" restart_class => "no_svn_running";
I know there's a potential race between setting the class and
performing the deletion on the next pass, but in this specific case it
would cause no problems.
--
Ron Parker
Don't type things you find on the Internet into your computer!
:(){ :|:&};:
_______________________________________________
Help-cfengine mailing list
Help-cfengine@cfengine.org
https://cfengine.org/mailman/listinfo/help-cfengine
