Hi Paul, et al,
That option works for the links directive only, and the links
directive doesn't seem to be able to do what I need done.
I am trying to copy an already-populated directory of symbolic
links from one system to another with the copy directive. Some of the
links point to files that won't exist on all systems, including the
remote server itself, and I cannot get cfengine to copy links to a
system when they files they point to don't exist on the remote server.
Is there some way to tell cfenging to copy the links and not mind what
they point to?
Brian
======================================================================
On Tue, Dec 20, 2005 at 05:21:31PM -0600, Paul Krizak wrote:
According to the documentation:
nofile=kill/force
This decides what happens to links which point to non-existent
files. The default action is to remove such links, or refuse to create
them. By setting the force option you can force cfengine to make
symbolic links to files which do not exist. This is useful for setting
up links to filesystems which are not permanently mounted.
So you can presumably do something like
links:
someclass::
/some/file -> /some/other/file nofile=force
Paul Krizak 5900 E. Ben White Blvd. MS 625
Advanced Micro Devices Austin, TX 78741
Linux/Unix Systems Engineering Phone: (512) 602-8775
Microprocessor Solutions Sector
Brian C. Hill wrote:
I posted this last week; no one responded. Is there a better
way to achieve this?
I want to copy a tree of symbolic links, some of which will not
actually point to anything on some systems. Is there a way to get
cfengine to copy the symbolic link without worrying about whether the
link is 'dangling' or not?
Brian
_______________________________________________
Help-cfengine mailing list
Help-cfengine@gnu.org
http://lists.gnu.org/mailman/listinfo/help-cfengine