On Fri, Feb 21, 2014 at 11:39 AM, Bryan Evenson <[email protected]> wrote: >> > At this point, ifplugd is not running. After some poking around, I see >> > that >> there is no default daemon script for ifplugd included with Busybox. I'm >> assuming a script to do the above isn't that difficult, but I can't seem to >> find >> any examples on how to do this. Does anyone have a simple example that I >> can go by? I did see the example in the Busybox source under >> examples/var_service/ifplugd_if, but I couldn't make any sense of what that >> script did and how to make use of it. >> >> It means that busybox/examples/var_service/README is badly located, or >> badly written, or both. >> > > I found the README you were talking about. I have never used runsvdir before > and I don't have it included in my version of Busybox. I didn't realize that > Busybox was assuming you'd use runsvdir to run ifplugd,
We don't pull Lenart Pottering here. Busybox does not assume or require you to use runsvdir with ifplugd. You can use ifplugd with or without runsvdir. ifplugd is written in a way that it's *you* who decide what to do when link goes up or down (by the way of writing desired actions in your script). > which was the start of my confusion. And since I didn't know that's what was > assumed, I didn't think to look a couple directories up for a related README. How about this fix (adding another README)? $ cat examples/var_service/ifplugd_if/README The real README file is one directory up. > A little more background on my system. It's an ARM family processor and I'm > using the Yocto Project's Poky distribution on my system. The default image > for that build uses sysVinit and is setup for ifup/ifdown. > So if I wanted to use ifplugd, is the suggestion that I include runsvdir and > runsv in my Busybox configuration and use it to run ifplugd? If you want to use ifplugd, use it. Namely, decide where to start it, and what to put into its helper script. > I'm unclear what runsvdir is doing that sysVinit can't. There are plenty of stuff about daemontools and runsvdir on Google. A very short synopsis: runsvdir babysits processes just like sysVinit does for getties / X / whatever, but in a better way: you can add/remove/start/stop these babysitted processes without sending signals or editing text config file. > If not ifup, what would you suggest? I'm open to ideas, > just looking for the simplest path to get to where I want to go. The very simplest path wouldn't work: you can't design your networking for a single wired ethernet with static address or DHCP, and then start bolting on hacks to make it work with wifi, more than one interface, vpn's, dynamic firewalling etc. It would be a horrifying mess. I went through that path already. Here is my current "best idea": http://busybox.net/~vda/no_ifup.txt _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
