[ale] odd log message

[Jeff Lightner]

Don't just comment out entries in inittab - change the word "respawn" to
"off" then exit and run "init q".   There are systems that will read the
"respawn" even if there is a comment in front of it so its best to do
things this way even if Linux isn't one of them.  

You can also add the entry suggested earlier.  Turning it "off" gives
you time to troubleshoot the error without it wasting cycles trying to
start it over and over.  Once resolved you simply change the entry back
to "respawn" and run init q again to reread the inittab.

-----Original Message-----
From: ale-bounces at ale.org [mailto:ale-bounces at ale.org] On Behalf Of
Geoffrey
Sent: Tuesday, May 20, 2008 6:51 AM
To: ale at ale.org
Subject: Re: [ale] odd log message

Sean wrote:
> On Monday 19 May 2008 11:22:00 pm Pete Hardie wrote:
>> initd is complaining that a process is being spawned and is dying so
>> fast that the respawn rate is too hihg, and it's throttling it.
>>
>> ths "co" process is probably failing hard with a parameter error.
>> Check your inittab for a bad command line for something called co.
> 
> 
> My inittab includes these lines:
> 
> # Run gettys in standard runlevels
> co:2345:respawn:/sbin/agetty xvc0 9600 vt100-nav

I believe this is an entry to create a serial console entry.  If you 
don't ever use one, I suspect you can comment it out.

-- 
Until later, Geoffrey

Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety.
  - Benjamin Franklin
_______________________________________________
Ale mailing list
Ale at ale.org
http://mail.ale.org/mailman/listinfo/ale
----------------------------------
CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you.
----------------------------------