grsecurity forums

I compiled a kernel with support for support for fork bomb protection among other things, and I configured most of them.

However, I forgot to define a GID in /proc/sys/kernel/grsecurity/fork_bomb_gid (this is set to 0), and now I suddenly can't change any of the values in .../grsecurity/.
This would not have been a big problem, of course, if the kernel wasn't fork protecting gid 0

I've tried changing it in single user mode and during boot by rc-scripts, but neither worked.
I can surely see the reason why doing this shouldn't be easy, but there must be a way, mustn't it? I'm thankful for all help.

I found the error.
Once I changed the rc script to set grsec_lock to 0 before setting all the other values, and change it back to 1 when it's done, everything worked like a charm. I guess I should've read more docs before posting.