On Tue, Nov 02, 2004 at 01:11:19AM -0500, Lumberjack wrote: > Couple follow ups. I searched back the last two or three months and didn't > find any "no nos" on using /proc/net/ip_conntrack. All I can figure is > that it could be a hit to read through if very large. Not sure yet how > /proc fs might lock things either (if that might be an issue). So any > reason for using this to be a "bad thing" please provide some sort of hint > if possible. the thread that it ended up coming out in that i was thinking of: http://marc.theaimsgroup.com/?l=netfilter&m=109649105915501&w=2 and yes--it has to do with read locking. > Another. If I do something to read in the contents of > /proc/net/ip_conntrack and then do something to send some output to stdin > of iptables-restore/iptables does my app need to be GPL based? Boarders > here seem rather grey. I am not modifying any GPL code nor extending it so > it doesn't seem to me be something that "modifies" and thus requires to be > released under the GPL. can't help ya there... -j -- "Here we have an ordinary square. Whoa! Slow down egghead!" --The Simpsons
