Uhh, too many forks, PIDs got reused, we're confused

This message is displayed on the console shortly after booting openSUSE 11.2 x86_64 gm:

Uhh, too many forks, PIDs got reused, we’re confused
at 6734 startpar 1499 fork -513

There is nothing in the messages that seems related to this at all. What is this thing? What am I supposed to look at which is forking so prolifically?

same on another 64 bits suse 11.2 machine, but with
different numbers:
“at 7505 startpar 1300 fork -513”

Me too, did not write down the numbers… 32 bit vbox install from DVD KDE

the qeustion is also on al.os.linux.suse
Uhh, too many forks, PIDs got reused, we’re confused - alt.os.linux.suse | Google Discussiegroepen
and a reply to a bugzilla report about it
https://bugzilla.novell.com/show_bug.cgi?id=551635

Lots of info there! The message is from a preloader program,
which I guess preloads a list of programs as soon as possible
during startup so they don’t have to pull each other in
sequentially, so startup is faster. If it gets confused, it
just stops preloading, but the programs get loaded in the
usual way anyhow. At least that’s my understanding of what
the developers are saying, starting with comment #7.

In any case, the message is only a warning, and does not
indicate any real problem with the system. Just a slight
irritation resulting from over-enthusiastic forking.

so, just wait for a update on it.

The error causes “prepare_preload” to give up, I found I hit this often enough for it to become annoying.

unoffiical prepare_preload Patch (if you break anything you get to keep the pieces!)

If you don’t understand it, then just wait for the update, I just got too bored of this annoyance not to fix it myself - https://bugzilla.novell.com/show_bug.cgi?id=551635#c27

Hi,

I have the same problem with openSUSE 11.2 64bit, only if the situation occures many application crash and the system needs reboot to be able to work again. And even the reboot does not really work - I need to switch the computer off and the boot twice to clean the situation up.
Of course I can do regular reboots (at least once a week) to avoid this problem, but then I could go back to Windows, couldn’t I?

Is there any solution to this? My system seems to have all updates installed and unfortunately I cannot upgrade to 11.3 (VMware is not supporting it yet).

Anybody has an idea?

Thanks
Richard