What does this mean exactly? I get this message when i am trying to install. Checked media and the disk is fine. 11.3 RC1 is the media i am installing
furhead1 wrote:
> What does this mean exactly? I get this message when i am trying to
> install. Checked media and the disk is fine. 11.3 RC1 is the media i am
> installing
not much info in your post to go on…maybe see if you can use this to
figure out what to do next: http://tinyurl.com/23xwkyz
and, if you can’t get right with that and need our help we need some
info…like what kind of hardware, when this is happening in install,
etc etc etc…
and, actually since you are trying to install unreleased software you
might find it is a KNOWN bug…you should at the very least search
our http://forums.opensuse.org/get-help-here/pre-release-beta/ for
similar problems encountered by others and BE SURE to file a bug
report immediately if it is not yet reported in bugzilla…that is the
ONLY hope of getting it fixed prior to actual release of 11.3
to file a bug, see: http://en.opensuse.org/Submitting_Bug_Reports
and, in all cases: all posts on unreleased software should be in the
forum noted above…
–
DenverD (Linux Counter 282315)
CAVEAT: http://is.gd/bpoMD
posted via NNTP w/TBird 2.0.0.23 | KDE 3.5.7 | openSUSE 10.3
2.6.22.19-0.4-default SMP i686
AMD Athlon 1 GB RAM | GeForce FX 5500 | ASRock K8Upgrade-760GX |
CMedia 9761 AC’97 Audio
The “respawn too fast” message is a message from init.
init is the process with process number 1. It is the first process to be started when the system boots. It’s configuration is in* /etc/inittab.* There you will find wich processes have to run on a certain runlevel. You will find there entries which have the word respawn in column three. That means that init will watch that process and when it dies for whatever reason it will start it again.
Now when such a process dies in a very short time (for whatever reason) again and again it would be a performace hassle to go on restarting it (and apperently it would be useless because it seems that that process/program isn’t doing something usefull). It could even block other system functioning with this tight loop. It is therefore that init stops for five minutes doing the respawn to give the systems manager a change to log in and do something to stop this behaviour.
Thus there is something realy wrong here. Did you by any chance change something in /etc/inittab before this happened?
Also take care, that this is a general answer on the general question about the message. Having problems with 11.3 are better addressed at the Prerelease/beta Forum because all the testers are luring there.