How to become good UNIX engineer


 
Thread Tools Search this Thread
The Lounge What is on Your Mind? How to become good UNIX engineer
# 15  
Old 11-03-2010
Learn - Do - Break stuff - Fix stuff

With enough of that you should be well on the path
Login or Register to Ask a Question

Previous Thread | Next Thread

4 More Discussions You Might Find Interesting

1. Advertise with Us

Systems Engineer- Emeryville, CA (UNIX, C)

Systems Engineer- Emeryville, CA (UNIX, C) Gracenote is seeking a Systems Engineer to develop features and fixes in Gracenote's online media recognition service. You will contribute regularly to team design and code reviews, and be responsible for the analysis and resolution of software defects... (0 Replies)
Discussion started by: cwilliams
0 Replies

2. UNIX for Dummies Questions & Answers

Information on Network engineer and Unix Systems Engineer

Hi, I'm exploring a few different careers( Unix System's Admin, Network Engineer, and Unix System's Engineer). I asked in another thread about System's Admin, so I have some more info on that already. I'm not finding very much info on Network Engineers or Unix System Engineers though. Can you guys... (0 Replies)
Discussion started by: hpicracing
0 Replies

3. UNIX for Dummies Questions & Answers

What is the industry standard for number of servers per Unix/Linux engineer?

What is the industry standard for number of servers per Unix/Linux engineer and are there any white papers or the like that discuss this? (1 Reply)
Discussion started by: Rav78uk
1 Replies

4. UNIX for Dummies Questions & Answers

Good Unix Shells ?

Hey Guys i am new to Unix and i have downlaoded Cygwin for Windows and deleted it. I was just wondering is there any good shells like that for windows that just as good thanks for your time ][ce (1 Reply)
Discussion started by: IceCold
1 Replies
Login or Register to Ask a Question
io_nonblock(3)						     Library Functions Manual						    io_nonblock(3)

NAME
io_nonblock - switch to non-blocking I/O SYNTAX
#include <io.h> void io_nonblock(int64 fd); DESCRIPTION
io_nonblock puts UNIX descriptor fd into ``non-blocking mode.'' Calling io_nonblock(fd) before io_fd(fd) makes io_tryread and io_trywrite faster and more efficient. Actually, current UNIX kernels do not support non-blocking descriptors; they support non-blocking open files. Furthermore, many programs will break if they encounter non-blocking mode. This means that you must not use io_nonblock for a descriptor inherited from another pro- gram. io_nonblock has no return value; it always succeeds. If d is not the number of a UNIX descriptor, io_nonblock has no effect. If io_fd is given a descriptor in blocking mode, io_tryread and io_trywrite go through the following contortions to avoid blocking: 1 Stop if poll says that the descriptor is not ready. Otherwise there's a good chance, but not a guarantee: even if poll says the descrip- tor is ready, the descriptor might not be ready a moment later. (Furthermore, poll can fail on some systems.) 2 Catch SIGALRM. SIGALRM must not be blocked, and must not be used elsewhere in the program. 3 Set an interval timer so that any blocking call will be interrupted by SIGALRM within 10 milliseconds. (Current UNIX kernels do not allow any shorter interval.) Of course, this may still mean a 10-millisecond delay. If io_fd is given a descriptor in non-blocking mode (or a descriptor for a regular disk file), io_tryread and io_trywrite avoid these con- tortions. SEE ALSO
io_wait(3), io_canwrite(3) io_nonblock(3)