From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.54) id 1FR8V7-0000kI-Sd for garchives@archives.gentoo.org; Wed, 05 Apr 2006 13:56:50 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.6/8.13.5) with SMTP id k35DucET013902; Wed, 5 Apr 2006 13:56:38 GMT Received: from eagle.megaweb.biz (eagle.megaweb.biz [196.22.235.76]) by robin.gentoo.org (8.13.6/8.13.5) with ESMTP id k35DuXPU026624 for ; Wed, 5 Apr 2006 13:56:35 GMT Content-class: urn:content-classes:message Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-embedded@gentoo.org Reply-to: gentoo-embedded@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: [gentoo-embedded] init Id "s0" respawning too fast: disabled for 5 minutes X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Date: Wed, 5 Apr 2006 15:58:57 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [gentoo-embedded] init Id "s0" respawning too fast: disabled for 5 minutes Thread-Index: AcZYt1SUlknlsMxCRRWE6FCXur8Q2QAAGj0A From: "Jean Blignaut" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by robin.gentoo.org id k35DuXPU026624 X-Archives-Salt: 86ef9ddf-ffce-482f-bb3e-b372c32c09f3 X-Archives-Hash: 15ced8bdf454086b0dff78942c3bdb31 -----Original Message----- From: Hans-Werner Hilse [mailto:hilse@web.de] Sent: Wednesday, April 05, 2006 3:43 PM To: gentoo-embedded@lists.gentoo.org 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" 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 > -- > gentoo-embedded@gentoo.org mailing list -- gentoo-embedded@gentoo.org mailing list