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
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?
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
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?
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?
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
NICE(2) Linux Programmer's Manual NICE(2)
NAME
nice - change process priority
SYNOPSIS
#include <unistd.h>
int nice(int inc);
DESCRIPTION
nice adds inc to the nice value for the calling pid. (A large nice value means a low priority.) Only the superuser may specify a negative
increment, or priority increase.
RETURN VALUE
On success, zero is returned. On error, -1 is returned, and errno is set appropriately.
ERRORS
EPERM A non-super user attempts to do a priority increase by supplying a negative inc.
CONFORMING TO
SVr4, SVID EXT, AT&T, X/OPEN, BSD 4.3. However, the Linux and glibc (earlier than glibc 2.2.4) return value is nonstandard, see below.
SVr4 documents an additional EINVAL error code.
NOTES
Note that the routine is documented in SUSv2 to return the new nice value, while the Linux syscall and (g)libc (earlier than glibc 2.2.4)
routines return 0 on success. The new nice value can be found using getpriority(2). Note that an implementation in which nice returns the
new nice value can legitimately return -1. To reliably detect an error, set errno to 0 before the call, and check its value when nice
returns -1.
SEE ALSO
nice(1), getpriority(2), setpriority(2), fork(2), renice(8)
Linux 2001-06-04 NICE(2)