Dear Gurus,
The problem we had with init, that was always taking CPU time,
was related to a bad reinstallation of lattelnet. This also caused
/usr/var/adm/wtmp to fill completely /usr, preventing shutdown
to single user. After correct reinstallation of lattelnet
and clearing up wtmp thins went well.
Oyanarte Portilho
Dept. of Physics
Univ. of Brasilia, Brazil
Original post:
We have reintalled our operating system (DU 3.2)
and are getting a problem with init. It is always
running, as shown in the line below, that we got
using ps axu:
USER PID %CPU %MEM VSZ RSS TTY S STARTED TIME COMMAND
root 1 16.0 0.0 296K 56K ?? U 16:22:32 10:11.36 /sbin/init -a
Also, when trying to go to single user mode we get the
message in the console:
INIT: failed write of utmp entry: "ss"
The first lines of /etc/inittab are:
is:3:initdefault:
ss:Ss:wait:/sbin/rc0 shutdown < /dev/console > /dev/console 2>&1
s0:0:wait:/sbin/rc0 off < /dev/console > /dev/console 2>&1
fs:23:wait:/sbin/bcheckrc < /dev/console > /dev/console 2>&1
kls:Ss:sysinit:/sbin/kloadsrv -f & < /dev/console > /dev/console 2>&1
sysconfig:Ss:sysinit:/sbin/init.d/autosysconfig start < /dev/console > /dev/console 2>&1
update:23:wait:/sbin/update > /dev/console 2>&1
it:23:wait:/sbin/it < /dev/console > /dev/console 2>&1
kmk:3:wait:/sbin/kmknod > /dev/console 2>&1
s2:23:wait:/sbin/rc2 < /dev/console > /dev/console 2>&1
s3:3:wait:/sbin/rc3 < /dev/console > /dev/console 2>&1
cons:1234:respawn:/usr/sbin/getty console console vt100
Does anybody have idea of what is going on?
Received on Fri Jan 10 1997 - 14:55:12 NZDT