usernetctl(8) [redhat man page]

USERNETCTL(8)						      System Manager's Manual						     USERNETCTL(8)

NAME

       usernetctl - allow a user to manipulate a network interface if permitted

SYNOPSIS

       usernetctl interface-name up|down|report

DESCRIPTION

       usernetctl  checks to see if users are allowed to manipulate the network interface specified by interface-name, and then tries to bring the
       network interface up or down, if up or down was specified on the command line, or returns true or false status (respectively) if the report
       option was specified.

       usernetctl  is  not  really  meant to be called directly by users, though it currently works fine that way.  It is used as a wrapper by the
       ifup and ifdown scripts, so that users can do exactly the same thing as root:
       ifup interface-name
       ifdown interface-name
       and ifup and ifdown will call usernetctl automatically to allow the interface status change.

OPTIONS

       interface-name
	      The name of the network interface to check; for example, "ppp0".	For backwards compatibility, "ifcfg-ppp0" and "/etc/sysconfig/net-
	      work-scripts/ifcfg-ppp0" are also supported.

       up|down
	      Attempt to bring the interface up or down.

       report Report on whether users can bring the interface up or down.

NOTES

       Alternate device configurations may inherit the default configuration's permissions.

RHS
								   Red Hat, Inc.						     USERNETCTL(8)

IFSERVICES(5)						       Network configuration						     IFSERVICES(5)

NAME

       ifservices-* - control network services with ifup/down

SYNOPSIS

       /etc/sysconfig/network/ifservices-<configuration_name>/

DESCRIPTION

       The  directory  /etc/sysconfig/network/ifservices-<configuration_name>/	is read by the script /etc/sysconfig/network/scripts/ifup-services
       which starts and stops system services when an interface is set up/down.  ifup-services is used by /sbin/ifup, which is	the  command  line
       user interface for setting up network interfaces.

       This  is useful if you don't have a permanent network connection. If you sometimes boot without network and plug in the network cable later
       you can add links to system services in this directory. These services will then be started with ifup and stopped with ifdown.

       The configuration name used for ifservices-* should match exactly the configuration name of the ifcfg-* file for the interface.

       For the usage with NetworkManager (where you don't necessarily  need  a	ifcfg-*  file)	you  can  also	use  /etc/sysconfig/network/ifser-
       vices-<interface>-<essid>/  (for  wlan  interfaces)  or	if that does not exist /etc/sysconfig/network/ifservices-<interface>/.	As a final
       fallback /etc/sysconfig/network/ifservices/ is checked as well. If NetworkManager is active services will be stopped after the interface is
       down.

       The  links  in  this  directory	are  equal to the links in the runlevel directories /etc/init.d/rc*.d/ They have to point to service start
       scripts which are usually in /etc/init.d/.  Links starting with 'S' are start links, which are called in alphabetical order after ifup  has
       set  up	the  interface.  Links starting with 'K' are kill links which are called before ifdown takes down the interface.  See also section
       Sequencing Directories in boot (7).

EXAMPLE

       In this example we use an interface with MAC address 00:de:ad:be:af:00. This interface is not always physically connected. As soon  as  you
       plug in the cable ypbind and autofs should be started. When you pull the cable they should be stopped. This can be reached with:

       in file /etc/sysconfig/network/ifcfg-eth-id-00:de:ad:be:af:00

	   ...
	   STARTMODE=ifplugd
	   ...

       in dir /etc/sysconfig/network/ifservices-eth-id-00:de:ad:be:af:00/

	   S10portmap -> /etc/init.d/portmap
	   S20ypbind  -> /etc/init.d/ypbind
	   S30autofs  -> /etc/init.d/autofs
	   S20autofs  -> /etc/init.d/autofs
	   K30ypbind  -> /etc/init.d/ypbind

       Now you have to disable the start of this services at boot time

	   chkconfig ypbind off
	   chkconfig autofs off

       Notes:

       You  may call scripts/create-ifservices-directory [<interface_name>] to create a directory with the links from this example. This will cre-
       ate the directory ifservices-<interface_name> or if no interface name was given ifservices-template.

       Maybe you have to add also variable IFPLUGD_PRIORITY. For details about startmode ifplugd read ifup (8).

       The service portmap had to be added because ypbind needs it. This service is still started at boot time because it does not need an  active
       network	connection.  But  ypbind  may  now be started earlier as usual. Therefore we make sure that portmap is started before. Starting an
       already running service again does not affect the service.

SEE ALSO

       ifup(8), ifcfg(5).

AUTHOR

       Christian Zoz <zoz@suse.de>

sysconfig							   February 2005						     IFSERVICES(5)