Hello Eric,

- I could not login as the screen is filled with the ttys errors.
- I do not run any special cron jobs. It must be the default. The packages I have are declared in leaf.cfg

LRP="root,config,etc,local,modules,iptables,dhcpcd,ulogd,
    shorwall,dnscache,dropbear,weblet,
    sh-httpd,dhcpd,libm,libpcap,daemontl,tinydns,
    ntpdate,ntpsimpl,libssl,libcrpto,wireless,madwifi,
    liblzo,openvpnz,tc,bridge"
PKGPATH=/dev/hda1:msdos
syst_size=48M
log_size=32M

Besides not-able-to-login into the box, everything else seems working. Just for the sake of it, I shut it down, remove the CF, and mount it in my Fedora box, extract etc.lrp and here is the /etc/inittab

-------- BEGIN

FC_/root/NEWBOX> vi etc/inittab

# /etc/inittab: init(8) configuration.
# $Id: inittab,v 1.1 2004/10/14 19:09:29 espakman Exp $

# The default runlevel.
id:2:initdefault:

# Boot-time system configuration/initialization script.
# This is run first except when booting in emergency (-b) mode.
si::sysinit:/etc/init.d/rcS

# What to do in single-user mode.
~~:S:wait:/sbin/sulogin

# /etc/init.d executes the S and K scripts upon change
# of runlevel.
#
# Runlevel 0 is halt.
# Runlevel 1 is single-user.
# Runlevels 2-5 are multi-user.
# Runlevel 6 is reboot.

l0:0:wait:/etc/init.d/rc 0
l1:1:wait:/etc/init.d/rc 1
l2:2:wait:/etc/init.d/rc 2
l3:3:wait:/etc/init.d/rc 3
l4:4:wait:/etc/init.d/rc 4
l5:5:wait:/etc/init.d/rc 5
l6:6:wait:/etc/init.d/rc 6

# Normally not reached, but fallthrough in case of emergency.
#z6:6:respawn:/sbin/sulogin

# What to do when CTRL-ALT-DEL is pressed.
#ca:12345:ctrlaltdel:/sbin/shutdown -t1 -r now

# Action on special keypress (ALT-UpArrow).
kb::kbrequest:/bin/echo "Keyboard Request--edit /etc/inittab to let this work."

# What to do when the power fails/returns.
pf::powerwait:/etc/init.d/powerfail start
pn::powerfailnow:/etc/init.d/powerfail now
po::powerokwait:/etc/init.d/powerfail stop

# /sbin/getty invocations for the runlevels.
#
# The "id" field MUST be the same as the last
# characters of the device (after "tty").
#
# Format:
#  <id>:<runlevels>:<action>:<process>
# Example how to put a getty on a serial line (for a terminal)
#
# for WRAP box
#
T1:2345:respawn:/sbin/getty -L 38400 ttyS0 vt100

-------------------  END ------------------------

P.S. With the current working CF I have

Shorewall Started
Processing /etc/shorewall/started ...
Starting svscan ...
dnscache queries allowed from 10.9
Starting dnscache with daemontools ...
Creating cdb for tinydns-private
Starting private DNS server listening on 127.0.0.1 with daemontools
Creating cdb for tinydns-public
Starting public DNS server listening on xx.xx.xx.xx with daemontools
Shutting down dnscache with daemontools ...
dnscache queries allowed from 10.9
Starting dnscache with daemontools ...
Running ntpdate to synchronize clock.
Starting periodic command scheduler: cron.

LEAF Bering-uClibc 2.3 uClibc 0.9.20 Rev 3 wrapbox ttyS0
wrapbox login:


----- Original Message ----- From: "Eric Spakman" <[EMAIL PROTECTED]>
To: "M Lu" <[EMAIL PROTECTED]>
Cc: <leaf-user@lists.sourceforge.net>
Sent: Wednesday, October 26, 2005 4:28 PM
Subject: Re: [leaf-user] ttys errros on Bering 2.3


Hello,


Hi Eric,


the ttys errors still happened and I am scratching my hair on what could
use tty1 and tty2. I even deleted all lines referring to tty1, tty2... in
/etc/inittab and the errors are still there. I could not see the login
promt on the console attached via minicom and so I cannot login. Is there
a way to see what process/package is using those ttys?

The only way I know of is using "ps" to see the running processes, but
that is somewhat difficult without a working console.

I searched through all source, but couldn't find an other place besides
/etc/inittab where a getty is started on tty1/tty2.
The problem seems to start during, or just after crond runs. Do you have
some custom cron scripts?
Which packages do you have installed?

Eric

Thank you.


Here are some of the lines I copy and paste from minicom window:


..
Linux version 2.4.31 ([EMAIL PROTECTED]) (gcc version 3.3.3) #1 Thu Aug 18
21:03:20 CEST 2005
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 0000000008000000 (usable)
BIOS-e820: 00000000fff00000 - 0000000100000000 (reserved)
128MB LOWMEM available.
On node 0 totalpages: 32768
zone(0): 4096 pages.
zone(1): 28672 pages.
zone(2): 0 pages.
DMI not present.
Kernel command line: console=ttyS0,38400 BOOT_IMAGE=linux
initrd=initrd.lrp init=/linuxrc rw root=/dev/ram0
LEAFCFG=/dev/hsInitializing CPU#0
Detected 266.636 MHz processor.




...
Processing /etc/shorewall/start ...
Shorewall Started
Processing /etc/shorewall/started ...
Starting svscan ...
dnscache queries allowed from 10.9 Starting dnscache with daemontools ...
Creating cdb for tinydns-private
Starting private DNS server listening on 127.0.0.1 with daemontools
Creating cdb for tinydns-public
Starting public DNS server listening on xx.xx.xx.xx with daemontools
Shutting down dnscache with daemontools ...
dnscache queries allowed from 10.9 Starting dnscache with daemontools ...
Running ntpdate to synchronize clock.
Starting periodic command scheduler: cron.
getty: /dev/tty1: cannot open as standard input: No such device
getty: /dev/tty2: cannot open as standard input: No such device
getty: /dev/tty1: cannot open as standard input: No such device
getty: /dev/tty2: cannot open as standard input: No such device
getty: /dev/tty1: cannot open as standard input: No such device
..
INIT: Id "1" respawning too fast: disabled for 5 minutes
INIT: Id "2" respawning too fast: disabled for 5 minutes
INIT: no more processes left in this runlevel





----- Original Message -----
From: "Eric Spakman" <[EMAIL PROTECTED]>
To: "M Lu" <[EMAIL PROTECTED]>
Sent: Wednesday, October 26, 2005 2:33 PM
Subject: Re: [leaf-user] madwifi drivers on Bering 2.3





I will try again from scratch. I just would like to confirm with you
the following:



- I rename 'initrd_ide.lrp' on CD to initrd.lrp but I made no changes
to it. Is that OK?

Yes, that's ok.


- You have tested 2.3 on a WRAP box.


Not me, but Martin Hejl did (he is also one of the Bering-uClibc team).




----- Original Message -----
From: "Eric Spakman" <[EMAIL PROTECTED]>
To: "M Lu" <[EMAIL PROTECTED]>
Sent: Wednesday, October 26, 2005 10:51 AM
Subject: Re: [leaf-user] madwifi drivers on Bering 2.3



But it's somewhat strange the problems you see, the call to getty is
only done in /etc/inittab and you commented it out. So it shouldn't be
possible that you see those messages...

You even can't login with a serial console?


Eric




Actually I could not do it manually even if I wanted to as I cannot
login into the router yet due to the tty errors.




-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
------------------------------------------------------------------------
leaf-user mailing list: leaf-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-user
Support Request -- http://leaf-project.org/






-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
------------------------------------------------------------------------
leaf-user mailing list: leaf-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-user
Support Request -- http://leaf-project.org/



-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
------------------------------------------------------------------------
leaf-user mailing list: leaf-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-user
Support Request -- http://leaf-project.org/

Reply via email to