On 5/14/2013 12:13 AM, Ian Kent wrote:
Indeed that's probably good to do too. I'd be interested to hear if this patch functions OK with the IFF_UP check in place. In the mean time I'll add the patch to my queue for the next commit.
I've been running it for a day on a few boxes with no problems. The only additional line is a logging line I had when originally testing.
May 14 04:58:47 cockatrice automount[365]: get_proximity:168: getifaddrs: ifa_name lo, ifa_flags 0x00010049 May 14 04:58:47 cockatrice automount[365]: get_proximity:168: getifaddrs: ifa_name eql, ifa_flags 0x00000400 May 14 04:58:47 cockatrice automount[365]: get_proximity:168: getifaddrs: ifa_name eth0, ifa_flags 0x00011043 May 14 04:58:47 cockatrice automount[365]: get_proximity:168: getifaddrs: ifa_name wlan0, ifa_flags 0x00001002 May 14 04:58:47 cockatrice automount[365]: get_proximity:168: getifaddrs: ifa_name wmon0, ifa_flags 0x00011043
IFF_UP is 0x01 so that looks correct. eql was the one that it was crashing on with no ifa_addr.
Doug -- To unsubscribe from this list: send the line "unsubscribe autofs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
