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-vlan
IFCFG-VLAN(5) Network configuration IFCFG-VLAN(5)
NAME
ifcfg-vlan - virtual LAN interface configuration
SYNOPSIS
/etc/sysconfig/network/ifcfg-vlan*
Virtual LANs (802.1q)
To setup a vlan interface you need a configuration file that contains at least the mandatory
ETHERDEVICE
variable with the real interface used for the virtual LAN.
Further, it may contain the optional
VLAN_ID
variable that specifies the VLAN ID.
By default and when the VLAN_ID variable is not set, the number at the end of the interface name is the VLAN ID.
Preferably the interface name and the configuration file follow the VLAN interface name scheme (type), that is either:
ifcfg-vlan<VLAN-ID> (e.g. ifcfg-vlan42)
or
ifcfg-name.<VLAN-ID> (e.g. ifcfg-eth0.42)
The VLAN-ID can be also 0-padded (e.g. ifcfg-vlan0042 or ifcfg-eth0.0042).
Also in case of custom names, trailing digits are interpreted as VLAN-ID by default (e.g. ifcfg-dmz42). When VLAN_ID is set in the config,
the interface name have any name (e.g. ifcfg-foobar).
Note: The drawback of custom interface names and VLAN_ID usage is, that a rename of the interface is required and that they violate the
name scheme.
The real interface will be set UP automatically and doesn't need a config file in case of a physical interface. But without a config file
YaST will consider this interface as unused, if will not follow hotplug events and you're unable to apply any settings, e.g. ETH-
TOOL_OPTIONS. To avoid that, provide an config file with at least STARTMODE='auto'.
The rest of the VLAN interface IP and routes configuration do not differ from ordinary interfaces. See also man ifcfg and man routes for
details.
EXAMPLES
Sets up vlan3 vlan interface on top of eth0:
ifcfg-vlan3
STARTMODE='auto'
ETHERDEVICE='eth0'
IPADDR='192.168.3.27/24'
Sets up eth0.3 vlan interface on top of eth0:
ifcfg-eth0.3
STARTMODE='auto'
ETHERDEVICE='eth0'
IPADDR='192.168.3.27/24'
Sets up lan1 vlan interface with ID 42 on top of eth0:
ifcfg-lan1
STARTMODE='auto'
ETHERDEVICE='eth0'
VLAN_ID='42'
IPADDR='192.168.3.27/24'
BUGS
Please report bugs at <http://www.suse.de/feedback>
AUTHOR
Christian Zoz <zoz@suse.de>
Michal Svec <msvec@suse.cz>
Bjoern Jacke
Mads Martin Joergensen <mmj@suse.de>
Michal Ludvig <mludvig@suse.cz>
Marius Tomaschewski <mt@suse.de>
SEE ALSO
routes(5), ifcfg(5), ifup(8).
sysconfig August 2004 IFCFG-VLAN(5)