nd-user, ought
to be able to rely on the provided "update.cf" already to have the
structure and flexibility to handle multiple servers. Instead, it is
actually programmed against this!
I'm happy to submit bug reports. Indeed, I'
one file, as an atomic action, may also be highly
desirable. (Indeed, my phrase "highly desirable" might, in some
circumstances, need to be read as "essential".)
Anyway, thanks for the attention and replies.
--
David Lee
Mark Burgess wrote:
> Thanks for reminding me about
to the
CPAN/best-practice question.)
If this is a known bug, that's OK; just let me known its status, please.
--
: David Lee
: ECMWF (Data Handling System)
: Shinfield Park
: Reading RG2 9AX
: Berkshire
:
: tel:+44-118-9499 362
: email: david@ecmwf.int
_
s writing local things might start adopting
bad habits from those poor examples.
So while a generally "open to all suggestions" policy would be great,
there should be at least a small amount of gatekeeping by some of the
established developers.
--
: David Lee (ECMWF)
___
Help-cfengine mailing list
Help-cfengine@cfengine.org
https://cfengine.org/mailman/listinfo/help-cfengine
ples
for our subsequent local development of other things.
Is there mileage in future cfengine distributions including such a
collection? If there was, then presumably several of us on this list
might be able and willing to contribute into it (and, of co
yway, I'll see what I can do with processes. And if there is an RPM
of the new "process_stop" under "-n" fix, I'll test that. And I'll try
to come up with some well-framed questions, and positive suggestions for
documentation.
Thanks.
--
David Lee
Mark Burgess
igure, build, install stuff.
But if, at some pre-release point, you happen to build a RH-5/Centos-5
RPM (I'm running "cfengine-community-3.1.4-1.el5"), I'll happily give
that a go. (And I may be able also to do RHEL-6 by that time.)
Thanks again.
-- David Lee
Mark Burg
David Lee wrote:
> [...]
> And now I find that the one major advance that, in the documentation,
> had looked really promising, namely the concept of services, appears to
> have been deliberately hobbled in the community edition. (I hope
> someone can tell me it's not so
mising, namely the concept of services, appears to
have been deliberately hobbled in the community edition. (I hope
someone can tell me it's not so.) Sigh.
--
: David Lee
: ECMWF (Data Handling System)
: Shinfield Park
: Reading RG2 9AX
: Berkshire
:
: tel:+44-118-9499 362
: email: david
lack of symmetry seems strange. Why no "stop_class" (in parallel
to "restart_class")? Is there a rationale behind it? Is that rationale
documented? How does the end-user achieve parallel-looking (and
associated clarity) start and stop procedures?
--
p services (Redhat/Centos "service XXX start").
Also there is analogous functionality on other OSes (Solaris-10 "svc" etc.).
From that perspective, there is a parallel with package installation
and removal.
For packages there is already higher-level functionality in &quo
cedures. But what is the cleanest
cfengine-3 way to manage "chkconfig XXX {on|off}"?
The information isn't leaping out of the documentation. But a pointer
to a suitable manual page might be OK for me.
(Using "cfengine-community-3.1.4", by the way.)
--
: David Lee
: ECMWF (
12 matches
Mail list logo
