|
From: Heiko Z. <he...@zu...> - 2003-11-03 01:41:16
|
Bruce Smith wrote: >>>>the XFS part is not maintained, since it's not working with grsecurity. >>>>you have to get the latest patches and drivers. >>>> >>>> >>>Do we support turning off grsecurity? I turned off grsecurity in >>>menuconfig, did NOT select XFS and got the same thing. >>> >>> >>> >>That should work fine.... >>And yes we support turning of grsecurity, we need to have this working. >>Is it possible that you had XFS leftovers from your last try ? >> >> > >No, I checked. I grep'ed for XFS in .config and it was set to "n". > > The problem is, it could have messed up your kernel sources. Try again with a clean system, before you do anything. >>What are the abort messages ? >> >> > >They are scrolled off my screen now, but it was real similar with the >kernel patches screwing up and hanging waiting for input. > > As I said, try again with a fresh system. >>>grsecurity keeps killing processes on my server, so I need to get rid >>>of it. (or learn it, but turning it off sounds easier) :-) >>> >>> >>> >>What are the messages ? >> >> > >grsec: signal 6 sent to (thttpd:646) UID(65534) EUID(65534), parent (init:1) UID(0) EUID(0) > >I have no idea why it's doing that. >There have been other messages about squid processes too. > > What grsecurity does in this case, is loggin that something (init ?) send the signal 6 to thttpd. Do you have enough RAM ? I would try to get it running, since grsecurity improves the overal system security alot. Thttpd works fine for me, so it would be interesting to find out what's wrong. >>Did you ask for help on the grsecurity forum ? >> >> > >No, I haven't checked into it yet. I thought it would be easier to >turn off grsecurity since this box is behind a firewall anyway. > >Would NOT running /etc/init.d/grsecurity accomplish the same thing? > > You can try to set everything in /etc/sysconfig/grsecurity.proc to 0 and see if it behaves different. cya Heiko |