> From: Richard Weinberger [mailto:richard@xxxxxx] > Sent: Monday, July 21, 2014 4:18 PM > > Yue, > > Am 21.07.2014 10:05, schrieb Yue Zhang (OSTC DEV): > > 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. > > This way each distro can provide their own restart script. > Same as every distro has custom start scripts, etc... > > > 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. > > Iff the current solution works for _all_ networking implementations. > > Thanks, > //richard Hi, Richard IMHO, all networking implementations should handle the cable offline event. Consider this situation. I unplugged the network cable and connect it to a new network switch after 10 seconds. If the DHCP renew is not triggered, the network will break. I think in normal cases, it should already been handled properly. Unless there is a strong justification for not doing this. In that case, we shouldn't renew DHCP anyway. Thanks ---- Yue _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
