Harti Brandt wrote: > TL>> > is there any way to get at the if_multiaddrs list from user space (except > TL>> > for digging through the kernel with kvm). > TL>> > TL>> I'm affraid not. > TL> > TL>Actually, the easiest way is to remember the things when you > TL>set them in the first place. > > That's not an option for a daemon needing this information.
Why not? Who set them up? Wasn't it the Daemon that bound the sockets and the multicast addresses? This is like the Java-thing where people were too lazy to keep track of their memory allocations, so they invented dynamic scoping and garbage collection, or the Linux thing, where people were too lazy to remember the name of the file they called open(2) on in order to get a descriptor, and so wanted a function call to get the path to the file, totally ignoring the effects of directory permissions, hard links, and exclusion groups. Like the X Server: if you put the thing into the mode, it's your job to remember it so that you can take it out, later. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
