[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: interfaces "extras"

From: Mark Burgess
Subject: Re: interfaces "extras"
Date: Tue, 08 Nov 2005 21:30:43 +0100

Yes, cfengine tries to use the actual C code.  But of course the
ioctl code, like sockets etc is a disaster of incomprehensible
non-portability. you can't add extra stuff. The shell commands for
near-kernel stuff are your best bet.


On Tue, 2005-11-08 at 19:46 -0500, Christopher Browne wrote:
> A question about the interfaces: section...
> We've got some extra parameters that we commonly want to submit to
> ifconfig.  The docs indicate the following parameters:
> Can we add additional things that would be passed to ifconfig?
> Pointedly, we'd like to use cfengine to manage some aliased interfaces
> on AIX, where the typical command line for ifconfig is:
>  /etc/ifconfig en5 inet rg650-admin-app1 netmask 0xffffff00 broadcast 
> alias
> What this is doing is to add the address (aka
> rg650-admin-app1) as an alias to which the ethernet card "en5" should
> respond.
> It looks in the source as though ifconf.c uses ioctls directly to do
> things; I *presume* that means I can't use the built-in cfengine
> interface definition mechanism, and will have to go straight to
> "shellcommands:"
> Is that right?  Or am I on crack?  :-)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]