-----Original Message----- From: Hans-Werner Hilse [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 05, 2006 3:43 PM To: [email protected] Subject: Re: [gentoo-embedded] init Id "s0" respawning too fast: disabled for 5 minutes
Hi, On Wed, 5 Apr 2006 15:01:53 +0200 "Jean Blignaut" <[EMAIL PROTECTED]> wrote: >> ----nope just tried still get the "respawning too fast" error even >> with the s0 line commented out--- > Does the error claim that it's still the "s0" line? If so, you must > have make a mistake when commenting it out like editing the > wrong /etc/inittab or similar (initrd regeneration, etc.pp.). No mistake as far is I can tell after checking the /etc/inittab on the booted gnap virtual machine I decided to try changing runlevels from 3 to 4 and back again this seems to have worked cause I havn't seen the message since -- this leads me to believe that some thing else is enabling the s0 tty, something that ignores inittab As a matter of interest: the I/O error hasn't shown up in the logs since I first commented out s0 line in inittab >> Ipt_owner: pid, sid and command matching is broken on SMP. > That's from iptables. So I guess you're right when stating: >> Having noticed where this error happens now I would say its probably >> shorewall since both these happen after * Starting firewall ... > Looking at the error message, your probably trying to use "-m owner". > But it does look like more of a warning rather than an error (or are > you matching PID, SID or command string?). That said, PID/GID matching > should work. I'll have to test and see what works and what doesn't don't know too much about the inner workings of shorewall and my knowledge of iptables matching is -slim- > -hwh > -- > [email protected] mailing list -- [email protected] mailing list
