05-03-2008
When is 'ifup' really done?
I have been looking in the scripts for interface management, in an effort to kick off a script of my own on any "significant network event" (I will qualify that in a bit)
I managed to add a check to tell netplugd to run my script every time there is a hot-plug event. Now I need to make it so my script is also kicked off on a 'service network restart' or simply an 'ifup ethX'... which seemed doable to me...
Looking in the ifup script, I saw the ifup-eth script get kicked off, from there, the ifup-post script, to the ifup-local script (which doesn't exist, so isn't run)... stupid me, I made the assumption that "post" meant "after", and instead of seeing my script run, I see messages like "arping: recvfrom: Network is down" (arping is being called from my script)
btw - the first exec of my script happens *after* the interfaces are raised, but only because I do it via the boot-order rc3.d script-list
Any idea how I can make my script *actually* kick off after the interface is *actually* up?
3 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I have a little script in the /etc/network/if-up.d (debian). It should do something and write the output to a log file. But it doesn't seem to work.
ifup wlan0 dosomething >> /var/log/dosomething.log
I would like to add the date to the output, can somebody help me please?
Thanks! (6 Replies)
Discussion started by: borobudur
6 Replies
2. Red Hat
hi there
the ethernet wire was out of the pc when the system started.
#ifconfig
#ifconfig -a
i did not get any ip for eth0.
i plug the cable into the pc
#ifdown eth0
#ifup eth0
now the ip address is assigned to eth0
Question is : IS this right way to bring ethernet down... (2 Replies)
Discussion started by: dplinux
2 Replies
3. Red Hat
I've got an issue with a VMWare server running RHEL 6.3 that has dual E1000 NICs. I have configured the cards as I would normally do in /etc/sysconfig/network-scripts as ifcfg-eth0 and ifcfg-eth1. I can execute ifup eth0 and bring the interface up quite happily, however when I execute ifup eth1 it... (2 Replies)
Discussion started by: phaedrus
2 Replies
script(1) User Commands script(1)
NAME
script - make record of a terminal session
SYNOPSIS
script [-a] [filename]
DESCRIPTION
The script utility makes a record of everything printed on your screen. The record is written to filename. If no file name is given, the
record is saved in the file typescript. See WARNINGS.
The script command forks and creates a sub-shell, according to the value of $SHELL, and records the text from this session. The script ends
when the forked shell exits or when Control-d is typed.
OPTIONS
The following option is supported:
-a Appends the session record to filename, rather than overwriting it.
NOTES
script places everything that appears on the screen in filename, including prompts.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
|CSI |Enabled |
+-----------------------------+-----------------------------+
SEE ALSO
attributes(5)
WARNINGS
script can pose a security risk when used in directories that are writable by other users (for example, /tmp), especially when run by a
privileged user, that is, root. Be sure that typescript is not a link before running script.
SunOS 5.10 30 Jan 2004 script(1)