At 16.10 this afternoon I started a process via a shell script which is nso resource-hungry that absolutely nothing else on the computer (amd64 laptop, cpu with two cores) got done . Even the clock stands frozen at 16.10 for many hours!
I thought that with a modern, time-sharing OS like linux that would not be possible! but that is obviously wrong. ¿Is it possible to change some configuration file or something to prevent that ever happening again? (I know, I sjold have icluded some nice in that shell script, but that is easy to forget . But anyhow, tim e-sharing should garantee some time to all processes! (In the script, I am loopìng over the about 3700 tar.gz files in one directory. For e ach of them, I am spawning a sub-shell (using &) doing some installation wo rk). Kjetil -- "If you want a picture of the future - imagine a boot stamping on the human face - forever." George Orwell (1984) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlkti=m+dobfzjw57dvpiuhl2=tcwjyzsyuwkong...@mail.gmail.com
