[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: symlinks and the copy: directive
From: |
Brian C. Hill |
Subject: |
Re: symlinks and the copy: directive |
Date: |
Tue, 3 Jan 2006 16:31:36 -0800 |
User-agent: |
Mutt/1.4.2.1i |
I tested 2.18 and the problem still exists. Is the fix
not in 2.18?
Brian
======================================================================
On Sat, Dec 24, 2005 at 01:12:06PM +0100, Mark Burgess wrote:
>
> ok - I confirm that this is a bug/typo in cfservd. A patch has been
> applied to the source.
>
> M
>
> On Wed, 2005-12-21 at 16:24 -0800, Brian C. Hill wrote:
> > Hi Mark / everyone,
> >
> > I get this when running cfagent -v on the client. It won't
> > copy the links because the server is complaing that they don't
> > point to anything. That's true on the server, but it won't be
> > in the particular case of this client.
> >
> > WHen you say that it is the default behavior, I assume
> > you mean that the copy: directive doesn't care whether the
> > links resolve or not. Did you mean something else? Is that
> > what worked for you?
> >
> > Brian
> >
> > ------------------ ------------------ ------------------ ------------------
> >
> > cfengine:: Server returned error: unable to stat file
> > /usr/local/bin/openssl
> > cfengine:: (Can't stat /usr/local/bin/openssl)
> > cfengine:: Server returned error: unable to stat file
> > /usr/local/bin/c_rehash
> > cfengine:: (Can't stat /usr/local/bin/c_rehash)
> > cfengine:: Server returned error: unable to stat file /usr/local/bin/go
> > cfengine:: (Can't stat /usr/local/bin/go)
> >
> > ======================================================================
> > On Wed, Dec 21, 2005 at 09:55:34AM +0100, Mark Burgess wrote:
> > >
> > > Actually, on closer examination, this is the default behaviour for copy,
> > > when copying links, as far as I can see. I just tested it and it works.
> > >
> > > M
> > >
> > > On Wed, 2005-12-21 at 09:12 +0100, Mark Burgess wrote:
> > > > Yes - always begin with the manual.
> > > >
> > > > 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.
> > > >
> > > >
> > > > On Tue, 2005-12-20 at 15:09 -0800, 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
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > Help-cfengine mailing list
> > > > Help-cfengine@gnu.org
> > > > http://lists.gnu.org/mailman/listinfo/help-cfengine
> >
--
_____________________________________________________________________
/ Brian C. Hill bchill@bch.net http://brian.bch.net \
| UNIX Specialist BCH Technical Services http://www.bch.net |
- Re: symlinks and the copy: directive,
Brian C. Hill <=