Sponsored Content
Full Discussion: Proper Forum Etiquette
Contact Us Post Here to Contact Site Administrators and Moderators Proper Forum Etiquette Post 27635 by tarballed on Wednesday 4th of September 2002 02:03:22 PM
Old 09-04-2002
Proper Forum Etiquette

I'm a frequent visitor to these forums. I generally enjoy topics that are posted as well as the responses. I really pickup a lot of new things to learn.

However, there is one thing that does bother me here. (I dont mean to start a flame war, or any problems at all, just expressing some thoughts)

Whenever I post, even before I post, I always research the issue as much as I can. I feel I learn better if I can actually try and figure my question on my own. However, if I cannot find the answer it is at that time I will post.

When I post, I try to be very specific, detailed and respectful. I feel that should be the correct way to post. I always start off with what im attempting to do and what steps I have done to try and resolve it on my own. In essence, I am polite and respectful in my posts.

What bothers me are these types of posts:

"Hey, how do you do this....?

bye"

I read this posts and cant help but get irritated. Did the person even attempt to research the issue? What about asking politely, being courteous and respectful? You cant help but question new threads that contain one line and end in bye.

Now im not saying that everyone needs to give a story before the post, but how about something more then "how do I do this? thanks." Maybe a little background info. A hint that maybe they tried to find the answer before they posted?

It just seems that everyone wants a quick answer and resolution. They dont want to take the time to try and figure out the problem on their own. It seems that laziness runs rampart in some, while patience and determination are non-exsistent.

I do enjoy helping people with questions. However, when I see those brief, "Give the answer now" posts, I cant help but ignore them.

I'm not trying to start a problem or negative thread here. That is not my intention. I do think that this forum as some top notched individuals who are very helpful and informative. It just bugs me at times when I see these type of posts.

Well, just wanted to get that off my chest.Smilie Like I said earlier, its not my intention to start any problems, just voicing my opinion.

Hope everyone is having a great day.

Tarballed

Last edited by tarballed; 09-04-2002 at 04:05 PM..
 

6 More Discussions You Might Find Interesting

1. IP Networking

Proper routing

I have a series of new machines that are internet facing (have IP's that are accessible via the 'net) and it has internal facing interfaces. I need to be able to communicate back to the internal network to a specific server which processes monitoring and e-mail traffic. I've been told that I should... (3 Replies)
Discussion started by: BOFH
3 Replies

2. UNIX for Dummies Questions & Answers

Proper use of prune...

My goal was to find any directories inside of any directory called "09_Client Original" not modified in the last 30 days. $ find /Volumes/Jobs_Volume/ -type d -name "09_Client Original" -exec find {} -mtime +30 -type d -maxdepth 1 \; The results of this find are passed along in a perl script... (1 Reply)
Discussion started by: guriboy
1 Replies

3. Post Here to Contact Site Administrators and Moderators

Forum etiquette and contact information

I got the following message I tried to send the following reply:Please excuse me for not being more familiar with this forums conventions. I was not aware that I included a personal message. Please help me by: 1. So that I can avoid this problem in the future, please let me know what part of my... (2 Replies)
Discussion started by: lmjennings44094
2 Replies

4. UNIX for Dummies Questions & Answers

Proper syntax

I'm new to Unix, and just had a quick question. I'm writing a bash script, and I was wondering what proper programming etiquette was for piping. How many pipes is too many pipes? OLDEST=$(find . -maxdepth 1 -type d -newermt 2012-07-01 ! -newermt 2012-07-30 | xargs ls -1td | tail -2) echo... (1 Reply)
Discussion started by: jrymer
1 Replies

5. What is on Your Mind?

Forum Update: Disabled Home Page Forum Statistics for Guests (Not Registered)

Just a quick update; to speed up the forums, I have disabled the forum statistics on the home page for non registered users. No changes for registered users. (0 Replies)
Discussion started by: Neo
0 Replies

6. What is on Your Mind?

Mobile: Advanced Forum Statistics to Forum Home Page

For mobile users, I have just added a "first beta" Advanced Forum Statistics to the home page on mobile using CSS overflow:auto; so you can swipe if you need to see more. Google Search Console mobile usability says this page is "mobile friendly" so perhaps this will be useful for some of our... (12 Replies)
Discussion started by: Neo
12 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 09:47 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy