04-24-2019
There is no need to reboot Linux systems to change the IP address of set up network services.
8 More Discussions You Might Find Interesting
1. BSD
hi
howto restart the network with a wireless interface including wpa_supplicant on freeBSD 7.2 without reboot? (3 Replies)
Discussion started by: ccc
3 Replies
2. AIX
Hi All,
Please let me know the command to restart the network interface and enable it on boot in AIX, similar to /etc/init.d/network restart in Redhat.
Thanks,
Sunil.K
please watch out to post in the right subforum! (9 Replies)
Discussion started by: sunilrk07
9 Replies
3. UNIX for Advanced & Expert Users
I'm becoming a dying breed where I work. More and more sys admins are advocating automatically restarting failed services such as tomcat, jboss, etc. I've always been against doing this except with buggy apps that can't be fixed or avoided.
My main argument is that I feel it's a trick used by... (9 Replies)
Discussion started by: mglenney
9 Replies
4. AIX
hello,
i have an AIX6.1.7.2 machine that it was upgraded recently from AIX5.3.9.4.
when i kill system services that should restart automatically like /usr/sbin/cron it doesnt start.
i checked my /etc/inittab file and i confirmed that this service is in respawn status so when i kill this process... (2 Replies)
Discussion started by: omonoiatis9
2 Replies
5. Shell Programming and Scripting
Hi Guys,
I need bash script to restart the service.
1. Disable the service called SASM
svcadm disable sasm
2. if service went to maintenance mode then it shuld clear it with below command
svcadm clear sasm
3.or else it should restart the mysql service
/etc/init.d/mysql stop... (1 Reply)
Discussion started by: bapu1981
1 Replies
6. Shell Programming and Scripting
Hi,
could someone give me an example for a debian server script? I need to check a process if the process has a high cpu load (top).
If yes the whole server needs to reboot.
Thats it, nothing more. ;)
Hope someone could help me.
Regards
woisch (2 Replies)
Discussion started by: woisch
2 Replies
7. Red Hat
I had a doubt if any services need to be restarted if port no in /etc/services in an RHEL setup is changed. For eg, the port no of 443 for SSL may need to be changed.
I hope my query is clear whether any services need to be restarted if port no in /etc/services is changed.
Please revert with... (10 Replies)
Discussion started by: RHCE
10 Replies
8. Red Hat
Hi,
I have 2 machines in production environment:
1. redhat machine for application
2. DB machine (oracle)
The application doing a lot of small read&writes from and to the DB machine.
The problem is that after some few hours the network from the application to the DB becomes very slow and... (4 Replies)
Discussion started by: moshesa
4 Replies
LEARN ABOUT SUSE
ifcfg-bonding
IFCFG-BONDING(5) Network configuration IFCFG-BONDING(5)
NAME
ifcfg-bonding - interface bonding configuration
SYNOPSIS
/etc/sysconfig/network/ifcfg-bond*
Bonding Interfaces
To setup a bonding interface you need a configuration file ifcfg-bond<X> with the usual network settings. But you must add additional vari-
ables
BONDING_MASTER
must be set to 'yes' to identify this interface as a bonding interface
BONDING_SLAVE_<X>
here you specify the interface name representing the slave network interfaces.
BONDING_MODULE_OPTS
contains bonding options. Here you can set interface timeouts or working modes ('mode=active-backup' for backup mode). For addi-
tional information take a look into the documentation mentioned at the bottom. Note, that this options are not passed as parameters
to the bonding kernel module any more, but set via sysfs interface. This variable will be renamed in the feature.
BONDING_SKIP_REMOVE_WORKAROUND
When set to "yes", a bonding interface will be not removed while ifdown any more to avoid problems, e.g. when some third party ker-
nel module, such as Veritas 'llt' module, does not react correctly to the UNREGISTER event and does not remove its references to the
bonding interface causing all network related operation to stuck.
Note: the bonding options are not reverted when this option is enabled and it is required to either explicitly keep the old options
and set them to their default setting on bonding configuration changes or to reboot.
Example
Example for a bonding interface on eth0 and eth1 using the backup mode
ifcfg-bond0
STARTMODE='onboot'
BOOTPROTO='static'
IPADDR='192.168.0.1/24'
BONDING_MASTER='yes'
BONDING_SLAVE_0='eth0'
BONDING_SLAVE_1='eth1'
BONDING_MODULE_OPTS='mode=active-backup miimon=100'
Additional Information
For additional and more general information take a look into /usr/src/linux/Documentation/networking/bonding.txt. Maybe you need to
install the kernel sources to get this additional documentation.
The configuration of routes for this kind of interface does not differ from ordinary interfaces. See man routes for details.
BUGS
Please report bugs at <http://www.suse.de/feedback>
AUTHOR
Christian Zoz <zoz@suse.de> -- ifup script
Wilken Gottwalt <wgottwalt@suse.de> -- ifcfg-bonding manual page
SEE ALSO
ifcfg(5), ifup(8).
sysconfig April 2005 IFCFG-BONDING(5)