Sponsored Content
Full Discussion: congrats & new forums
Contact Us Post Here to Contact Site Administrators and Moderators congrats & new forums Post 283 by Neo on Sunday 19th of November 2000 10:31:59 PM
Old 11-19-2000
The reason there is only one forum is that adding another forum complicates things. Right now, there is 'UNIX for Dummies'. If we add, UNIX, Advanced Topics (just one more) then what happens when 'UNIX for Dummies Questions' get posted in the 'Advanced UNIX' area? Or the other way?

Also having an advanced topic forum creates the problem of having problems with 'status'. People who answer in 'UNIX for Dummies' might not want to continue to participate in 'UNIX for Dummies' when they are active in 'UNIX for Advanced Users' (or something like that).

In other words, I don't think we are ready to fork another child forum just yet. Maybe later?

[Edited by Neo on 11-19-2000 at 10:42 PM]
 

5 More Discussions You Might Find Interesting

1. Post Here to Contact Site Administrators and Moderators

Congrats

I guess this is the most appropriate section for this post... Just wanted to give a big congrats to LivinFree for passing the 1000 post mark. Nice job! (2 Replies)
Discussion started by: PxT
2 Replies

2. What is on Your Mind?

congrats to zazzybob

i definitely want to thank and congratulate zazzybob on becoming a moderator in record time.. ZazzyBob you definitely have skills and hopefully they will continue to grow and spread... thanx for helping me out all those times moxxx68 (1 Reply)
Discussion started by: moxxx68
1 Replies

3. How to Post in the The UNIX and Linux Forums

How to Navigate in UNIX & Linux Forums..?

Hi , i am a new user to this forum can anyone please help me in navigation for this forum. also when i am trying to open any thread i am getting below error. Bad Request Your browser sent a request that this server could not understand.] Thanks. (1 Reply)
Discussion started by: nkchand
1 Replies

4. What is on Your Mind?

Congrats to RudiC - 3000 Thanks!

Congratulations to RudiC for crossing the magic boundary of being thanked 3000 times! As someone who often has profited greatly from your insight i stand in awe before this achievement. Thank you for your ongoing dedication and thank you for your willingness to share your knowledge! bakunin ... (15 Replies)
Discussion started by: bakunin
15 Replies

5. What is on Your Mind?

Congrats to Nezabudka for her Formulator Badge (UserCP Prototype v0.40)

Please join me in thanking one of our most active new members, nezabudka, who suggested that we start using the new usercp prototype and change the menu items around, effectively "promoting" the new prototype CP. At first, I did not understand her suggestion, but after 'coming down" from days of... (1 Reply)
Discussion started by: Neo
1 Replies
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)
All times are GMT -4. The time now is 12:45 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy