Re: Impact of having a large number of open file descriptors
On May 28, 2008, at 7:46 AM, Oliver Fromme wrote: Ivan Voras wrote: Im thinking again of the old idea of implementing poor man's file replication system using kqueue to monitor changes on files. It would be cool to have a kernel interface so you could attach to a mountpoint and receive a log of all activity on that file system. That's similar to what DragonFly's journaling feature does. Unfortunately the kqueue interface isn't capable of doing something like that ... So this is not an answer to your question, I'm afraid. I have an old patch that makes kqueue monitor every file write on the system and return the inode number in the knote's data field: http:// people.freebsd.org/~ssouhlal/testing/kqueue-anyvnode-20050503.diff . I'd think it shouldn't be too hard to make it per-mountpoint.. While at it, will EVFILT_VNODE and NOTE_WRITE catch "additional" ways the file can be modified, meaning mmap()? I think it does, although it will get delayed until the mmapped pages get flushed to disk. -- Suleiman ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
airodump-ng loses all stations after 30 mins
Playing with wireless I tried to use airodump-ng to see what one can get out of it. Command /usr/local/sbin/airodump-ng -w xx ral0 works fine for ~30 minutes and then loses all stations. Restarting this command gets it to the state with no stations right away. But after I do 'ifconfig ral0 down ; ifconfig ral0 up' command works again. Until it loses stations in ~30 minutes again and everything repeats. It seems that ral0 gets into some internal state that prevents airodump-ng from picking up packets. And down/up clears it. But the output of 'ifconfig ral0' doesn't change after down/up: ral0: flags=2a9c3 metric 0 mtu 1500 ether 00:18:f8:2e:40:25 inet 192.168.168.133 netmask 0xff00 broadcast 192.168.168.255 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect ) status: associated ssid "" channel 5 (2432 Mhz 11g) bssid 00:18:f8:2e:40:25 authmode OPEN privacy OFF txpower 50 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi11g 7 roam:rate11g 5 protmode CTS My card is recognized as: ral0: mem 0xcffe8000-0xcffe irq 17 at device 10.0 on pci0 And I use 7.0-STABLE. This seems like a bug in the driver. But I am asking here hoping someone will have an answer off the top of their head. Yuri ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
