Sponsored Content
Contact Us Forum Support Area for Unregistered Users & Account Problems Special note to unregistered users Post 302099339 by Perderabo on Monday 11th of December 2006 12:09:26 PM
Old 12-11-2006
Special note to unregistered users

This forum is intended only as a means to contact us if you are having trouble with your account. This forum is the only area on the site where even unregistered users can post. But because some spammers were using this to post spam, we have changed things a little bit. When an unregistered user posts, that post will go into a "Moderation Queue". A Moderator must approve the post before it actually become visible. So don't despair if you post something and it does not immediately show up. Your post have not been lost and will we get to it when we can. But, needless to say, any spam in the Moderation Queue will be deleted forthwith.
 

3 More Discussions You Might Find Interesting

1. IP Networking

using unregistered domain names

hey what the hell happens if you make sure (as best one can) that a domain name like anything.com is not used at all, and you set up your own DNS and use that name without registering with a registrar, i know if the address is in use you will make some people very upset and give many internet users... (2 Replies)
Discussion started by: norsk hedensk
2 Replies

2. Red Hat

Unregistered version RHEL...

Hi everyone, I am working a contract and the customer has not registered there RHEL 5 servers. They have a cluster of servers and it would seem that they all stop logging in messages @ appox 15:50 and then start logging again at 4:04 am. Is this a normal thing for non-registered? Lee (3 Replies)
Discussion started by: Lee Dunsmoor
3 Replies

3. What is on Your Mind?

Updates to Forum Navbar and Thread Reply for Unregistered Users

Hey You may have noticed I changed the navbar at the top a bit. I've almost finished converting the navbar to divs from table tags. In addition, for unregistered users, instead of seeing a "New Reply" button, unregistered users see a "Login to Reply" and icon which looks the same as our... (2 Replies)
Discussion started by: Neo
2 Replies
postwait(2)							System Calls Manual						       postwait(2)

NAME
postwait: pw_getukid(), pw_wait(), pw_post(), pw_postv(), pw_getvmax() - lightweight synchronization mechanism SYNOPSIS
DESCRIPTION
Postwait is a fast, lightweight sleep/wakeup mechanism that can be used for synchronization by cooperating kernel threads within a single process or between separate processes. A thread calls to block. It resumes execution when it is posted by another thread, the call expires, or is signaled. If one or more posts are already pending, returns immediately. Threads using postwait are identified by their ukid. A thread retrieves its ukid by calling It shares this ukid with anyone it chooses by any means it considers appropriate (for example, shared memory). is called with a timeout ts. If ts is NULL, the thread will not timeout. It will remain blocked until posted or a signal wakes it up. If ts points to a zero-valued timespec, will return immediately with a value (and indicating whether or not it was posted. If ts points to a timespec whose value is greater than zero, the thread will block for that amount of time unless it is posted or inter- rupted by a signal, in which case the timespec pointed to by ts is updated with the remaining time. The return value and are set to indi- cate the reason the call returned. is used to post many threads with a single call. It posts to all threads in the targets array. An value for each target is returned in the errors array. (0 indicates success.) If the errors pointer is zero, no target-specific errors are copied out. There is a maximum number of threads that can be posted with a single call. This value is returned by Posts sent to a kernel thread that already has a post pending against it are discarded. RETURN VALUE
returns 0 if it succeeds, -1 otherwise. returns 0 if posted, -1 otherwise. returns 0 if the post succeeds, -1 otherwise. returns 0 if every post succeeds, -1 otherwise. returns the maximum number of kernel threads that can be posted with a single call to ERRORS
sets to one of the following values if it fails: ukid points to an illegal address. The reliable detection of this error is implementation dependent. sets to one of the following values if it fails: was called with a timeout of 0 but the caller has no post(s) pending. was called with a timeout that expired. ts points to an illegal address. The reliable detection of this error is implementation dependent. was interrupted by a signal. The timespec pointed to by ts is invalid. sets to one of the following values if it fails: The ukid refers to a non-existent kernel thread. sets to one of the following values if it fails: targets points to an illegal address. The reliable detection of this error is implementation dependent. errors points to an illegal address. The reliable detection of this error is implementation dependent. count is less than 0. count exceeds the maximum value (as returned by A ukid refers to a non-existent kernel thread. postwait(2)
All times are GMT -4. The time now is 02:56 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy