2011.Szeptember 3.(Szo) 21:46 időpontban Anthony G. Basile ezt írta: > It does look like the same issue again. I don't think we really solved > it, but just found a workaround which you specify above.
It's definitely back. > It turns out that you can compile it static and change mode upon booting > by echoing values to /sys/class/net/bond0/bonding/mode. I do that on > two systems running ancient 2.6.34 kernels, but this should work on > 3.0.x. You can try that. The problem is, that if I put some echo lines in the preup phase of the network setup, it returns with an error message, that the file cannot be written to. After I could manually do it, it is already up, and the kernel denies to modify the running interface. Additionally these grsec lines can be also seen in the logs. > However, it bothers me that we don't understand what's going on. You > can try disabling GRKERNSEC_MODHARDEN and rebooting to see if grsec is > denying some udev trigger. But modharden should only prevent non-root > processes from autoloading. I can't test on mine because they are on > high availability clusters. Disabling MODHARDENED would definitely make the grsec messages disappear. I'll try to figure out what happens regarding reading and writing the bond mode during boot. Compiling it in the kernel with modified defaults solves all problem, but it's not a real solution. Thanks for your time: Dw. -- dr Tóth Attila, Radiológus, 06-20-825-8057 Attila Toth MD, Radiologist, +36-20-825-8057
