I was writing a program there that when it called a library, it went
spastic mallocing memory. It did this is VERY damn quick and used to crash
the linux box within 10 seconds if not stopped. It managed to kill INIT
once and the results were not pleasant in the slightest. Thing is, how can
I stop a program doing something like this. I have the problem solved so
it doesn't crash but it's very bad form that linux allowed itself to be
brought down in this fashion by a user space process. Ideas for
prevention?
On another note, my understanding is that Init is the system process - ie
the one that starts first and inherits oprphaned processes etc etc etc.
The system was still able to work after Init segfaulted, long enough to
unmount most file systems and call rc 6 manually. Why was the system
still able to function and even start new processes (su) without Init?
Mel
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!
