On Feb 14,  4:21pm, Christos Zoulas wrote:
} On Sep 24,  9:30pm, smb@cs.columbia.edu ("Steven M. Bellovin") wrote:
} | On Mon, 25 Sep 2006 01:18:24 +0000 (UTC), christos@astron.com (Christos
} | Zoulas) wrote:
} | > In article <20060924201851.280c509e.smb@cs.columbia.edu>,
} | > Steven M. Bellovin <smb@cs.columbia.edu> wrote:
} | > >I received the following messages from init after upgrading to 4.99.3
} | > >from this afternoon:
} | > >
} | > >Sep 24 20:09:17 berkshire init: can't add utmpx record for runlevel
} | > >Sep 24 20:09:17 berkshire init: can't add utmpx record for port system boot
} | > >Sep 24 20:09:17 berkshire init: can't add utmpx record for port system down
} | > >Sep 24 20:09:17 berkshire init: can't add utmpx record for runlevel
} | > >Sep 24 20:09:17 berkshire init: can't add utmpx record for port console
} | > >Sep 24 20:09:17 berkshire init: can't add utmpx record for port ttyE1
} | > >Sep 24 20:09:17 berkshire init: can't add utmpx record for port ttyE2
} | > >Sep 24 20:09:17 berkshire init: can't add utmpx record for port ttyE3
} | > >
} | > >Was I supposed to have tweaked something?  I see nothing in UPDATING
} | > >saying what to do.
} | > 
} | > Does who -a show these entries?
} | 
} | No.
} 
} Ok, something must be different in my startup code because my init can
} write them... I will look some more.

     I saw those as well on an i386 build that I did on Sunday.  I was
short on time, so I din't have a chance to look into it and I don't
have the machine handy.

}-- End of excerpt from Christos Zoulas