Slackware This Forum is for the discussion of Slackware Linux.
|
| Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
06-27-2006, 01:39 PM
|
#1
|
|
Member
Registered: Apr 2005
Location: Canada
Distribution: Slackware
Posts: 496
Rep:
|
Detect network cable being plugged in
Hi all,
When I plug or unplug my network cable (from eth0, a standard 10/100 nic), and use "dmesg", I see status notices like:
Code:
eth0: network connection down
eth0: network connection up using port A
My question: is there a way to detect these changes without using dmesg? Perhaps something changes in /proc/ or some event I could listen to? Basically I want to run a simple script when the network cable is plugged in. I have tried ifplugd, but it didn't seem to work properly for me.
Any ideas / advice?
|
|
|
|
06-27-2006, 03:46 PM
|
#2
|
|
Senior Member
Registered: Dec 2004
Location: In my house.
Distribution: Ubuntu 10.10 64bit, Slackware 13.1 64-bit
Posts: 2,649
Rep:
|
Did you try the scripts at Alien Bobs site? They work like a charm for me. Just change all of them at once to be sure everything works right.
|
|
|
|
06-28-2006, 11:00 AM
|
#3
|
|
Member
Registered: Apr 2005
Location: Canada
Distribution: Slackware
Posts: 496
Original Poster
Rep:
|
Thanks for the link, it looked like a good soluation, but then I realized it basically wraps ifplugd (and libdaemon), which I still haven't had any luck with.
Any more ideas? If not I guess I will have to write some sort of dmesg watching script 
|
|
|
|
06-28-2006, 11:09 AM
|
#4
|
|
Member
Registered: Jan 2006
Posts: 37
Rep:
|
Have you tried syslog? It can log kernel messages that show up in dmesg and you can send output to the console. If you don't want to see all the kernel message ring data, you could log to a file and tail it to the console as a background process with a grep for just ethernet messages.
Not very elegant, but it's a quick hack & slash for what you want.
(Note: That's according to the man page for dmesg. I haven't bothered to test it.)
|
|
|
|
06-28-2006, 11:14 AM
|
#5
|
|
Slackware Contributor
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 4,679
Rep: 
|
Quote:
|
Originally Posted by Vgui
it basically wraps ifplugd (and libdaemon), which I still haven't had any luck with.
|
Why don't you just give it a try? Can you tell me what went wrong with your own ifplugd experiences?
Eric
|
|
|
|
06-28-2006, 11:24 AM
|
#6
|
|
Member
Registered: Apr 2005
Location: Canada
Distribution: Slackware
Posts: 496
Original Poster
Rep:
|
Code:
tail -f /var/log/syslog | grep "eth0: network connection up"
That seems to get me the notification I want; I can latch onto it and call my script when it changes.
I like this solution a bit better for 2 reasons: it's simple and clean, and it doesn't require 2 additional software packages (even if they are tiny).
So although I imagine your script is very useful Alien Bob, it is probably overkill for my needs in this situation. And since I didn't elaborate earlier, the problem I was having with ifplugd was it did not trigger anything when the cable was un/plugged. I could see the process running in 'ps', but it didn't seem to actually do anything. I imagine I could have dug deeper and tried different configurations, but the tail solution seems fine for now.
Thanks a lot everyone!
|
|
|
|
06-28-2006, 12:20 PM
|
#7
|
|
Slackware Contributor
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 4,679
Rep: 
|
FYI,
If you want sophisticated logfile monitoring with action triggers, take a look at SEC (simple event correlator) at http://www.estpak.ee/~risto/sec/
I've used this, and found it practical and useful. It's basically no more than one intelligent perl script that can daemonize itself.
Eric
|
|
|
|
01-03-2009, 06:22 AM
|
#8
|
|
LQ Newbie
Registered: Jan 2009
Location: Brazil
Distribution: debian
Posts: 16
Rep:
|
I scripted this, and its work to me,
if [ "` ifconfig eth0| sed -n '/running/I p'`" == '' ];then echo off; else echo on; fi
change eth0 by e eth device you want to.
Good Luck!
Visit Brazil, it a nice place 
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 05:17 PM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|