Slashdot Mirror
Learn How UNIX Multitasks
BlueVoodoo writes "On UNIX systems, each system and end-user task is contained within a process. Learn how to control processes and use a number of commands to peer into your system."
← Back to Stories (view on slashdot.org)
Don't forget to set the I_WANT_A_BROKEN_PS environment variable!
Specialized tools? Everybody uses these all the time, and I note he didn't mention nice or renice - the ones nobody ever uses. This is not intermediate level stuff, this is beginner stuff. Awk, M4 and sed are intermediate - and they aren't specialized tools either.
This is an intuitive way to monitor the processes on your system. It's just "point and click"...I mean "point and shoot."
http://psdoom.sourceforge.net/
--Welcome to the Realm of the Hawke--
Yea you are a big man now. You read an article and you understood it before you read the article. So you feel inclined to instult the fact that some people may not know this.
Yes this is Basic Unix Command Line suff. But a lot of Unix users don't go beyond typing the command to run the program. Forking, Piping, Scripting, is more then what they really use. An some of the times these people who don't understand this are actually smarter then most of us. Say a Physicist who uses Unix to test their math or run complex simulations. Also there are a lot of people using Linux/Unix who were never formally taught how to use it. So they stick in the GUI, or Find and install programs that a simple small script can acomplish. I know you want to do your "I am an Alpha Geek" while thumping your chest. But if an article gets posted and you really don't care, then don't read it and move along. Because getting an article on information that you already know isn't a big deal, this is far more mature then say the latest Cool PC Mods.
If something is so important that you feel the need to post it on the internet... It probably isn't that important.
I used to run "w" and see what other people were doing, then look at the man page for that.
Patrick Doyle
I mod down every jackass who puts his moderation policy in his sig. Oh, wait a sec....
I sent it to two teams I work with. I had recently made a presentation that explains some similar things, and this comes at it from a different angle. I think it was very useful.
(Myself, I know it all, but not everyone does)
Actually I write C/C++ on HPUX and most unix sysadmins we seem to be able to find in the local (Orlando) market are retarded.
Check out my lame java blog at www.javachopshop.com
Ok, agree with one exception.
.NET application for a specific Windows architecture, then I wouldn't consider the user illiterate for not knowing the processes and binary code Unix launches on startup. At least, not in the incompetent sense that the word is being used here.
.NET, if they have little knowledge outside of the specific job they are completing then their creativity is severly limited and fundamental insights they should just have are not there.
.NET web development and when the develoeprs have no understanding of OSes and even *nix concepts they are nothing more than monkeys cranking out code that is dictated to them.
If you hire someone who is supposed to be working with Windows/*NIX interoperability and hadn't a clue how UNIX works, then you have a problem and, yes, the new guy is illiterate for the task he is given. If you hire a developer to make a
I am more demanding than this on developers and techs. I don't care if the project is 100% MS and
I have worked with many projects like ASP and
Another problem with such closed knowledge is even in little things, like in the example of Web development. I 'inherited' a tech that was supposed to be a great Web developer(MS tools), and when parts of the project were moved to Linux servers, the person literally did not understand why upper & lower case mixed reference tags were failing. And as scary as that sounds it very common.
But this is just like my personal stand on people in the OSS *nix world that have fallen so far away from MS that they fail to understand the newer MS OSes and what things are done right in the NT architecture that *nix has never done very well at. Techs will mislead clients because they don't understand 'easier' concepts that other people are using that came from the MS world even though they could be implemented on *nix.
This is also especially true for OSS *nix developers, if they don't know what else is out there, they could be recreating wheels that companies like MS, Sun, etc have already solved. And sadly I find this a lot even in some very well known and good OSS projects. There is something to be said for learning from your competition or people that have gone before you.
Maybe it is more like the difference between knowledge and understanding.
The existence of tags like "duh" and "slownewsday" creates a perverse incentive to approve articles like these.