On 06/06/2014 07:47 AM, Carlos E. R. wrote:
Once I had the old init consuming... I don't remember, maybe 90% CPU. It was outrageous and absurd. Well, the cause was that my modem had got into an unknown state, an internal loop or something, maybe sending repeated irq signals via serial port (I did not find out what), but "init" was attending to the modem signals full time with all the cpu power available. A power cycle of the modem solved the issue - but before finding the culprit, I did reboot Linux, to no use. It kept me mad for hours.
Yes, that's one of the problems with the old init and sysvinit, its sequential. The model is 'for each S*...'. So if one gets hung up in a forever loop it can't proceed to the next. Now I only have to worry about things like the file system doing a sync/rebalance and eating all the CPU. That happened along the development path or BtrFS at one time :-) All the way up to load average 23, and back down a few minutes later! Aaron is wrong: Linux is not UNIX. Linux offers much more opportunity for experimentation and development than UNIX ever did. -- “I'm not interested in preserving the status quo; I want to overthrow it.” ― Niccolò Machiavelli -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org