> From: Richard Weinberger [mailto:richard@xxxxxx] > Sent: Monday, July 21, 2014 2:55 PM > > Yue, > > Am 21.07.2014 04:44, schrieb Yue Zhang (OSTC DEV): > >> From: Richard Weinberger [mailto:richard.weinberger@xxxxxxxxx] > >> Why 10? Is this a random number which works by accident for ifplugd? > >> What about other networking implementations, is 10 also ok for them? > >> -- > >> Thanks, > >> //richard > > > > Hi, Richard > > > > I checked ifplugd's code. The deferring time is 5 seconds. That's how > comes > > the "10s". I agree with you this is a magic number and should be avoid. > However, > > this is the only feasible solution right now. If there is a better solution, I will > be > > glad to switch to it. > > > > I tested the fix in Redhat, Ubuntu and SUSE and it works in all of them. > > The problem I see is that there is no good way to trigger a DHCP renew from > a network device drivers. You're on the wrong layer. > 10 seconds may work but this is IMHO a hack which can easily break. > There are also more networking implementations than ifplugd. > Specially the systemd implementation looks promising. > > Can't you propagate the RNDIS_STATUS_NETWORK_CHANGE event to > userspace? > IIRC on HyperV guests already have a guest daemon. Let the daemon handle > the event such that distros can install their own hooks... > > Thanks, > //richard Hi, Richard The problem of systemd implementation is that in different distros, the ways to restart service are different. Propagating the event to userspace also doesn't help for this issue. The advantage of current solution is that it simulates a cable plugging in/out event. IMHO, in all the distros, this simulated event has already been well handled. It is a dup effect to implement new hooks. Thanks ---- Yue _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
