search for: erroneus

...not check if it works, but I've set a similar rule to block "Xmas scans" and, checked against a Hping3 scan (-UPF option), it seems to work fine: nft> add rule filter input tcp flags & (fin | syn | rst | psh | ack | urg) == fin | psh | urg log drop Since I've watched that erroneus syntax on other Nftables tutorials around the net, I guess it *did* work sometime in the past, but now it's broken. Debian Testing/Strech kernel 4.6.0-1-amd64 nftables 0.6-2 -- You are receiving this mail because: You are watching all bug changes. -------------- next part -------------- An H...

sorry I had a mistake sending my question without a subject. I do resend again. Please excuse me. > Hello > I have a data array with soil variables (caperf), in which the variable "clay" is factor (as I see entering str(caperf)) . I need to do a regression model, so I need to have arcilla (=clay) as a numeric variable. For that I have entered > >

...g VBA that directly manipulates the database extensively). Why don't you make a test by directly opening the mdb which contains the data (tables) twice from the same client and see what will happen. You should at least set debug level to 3 and send the part of the log that is created during the erroneus behaviour (do the same for the case of your real-life application that is your main problem). I am including at the end of this posting an abstract of my log files > I'm not sure where this belongs to. Since your description is more > detailed > than mine, would you do the posting ?...

...the previously mentioned failure mechanism. Anyway after disabling oplocks errors became less frequent (coincidence?) and later I noticed all the stuff I mentioned early and was able to eliminate errors by not opening the database twice in the same PC. Unfortunately testing is not easy in my case. Erroneus behaviour may not apear in a controlable test and doing the test in the real working environment makes me nervous since it involves critical data of my company. I'm not happy with samba 2.2.0. Please let me now for anything else you discover on this subject. I think we should do a posting in t...