Return to Question

I've been noticing an influx of questions lately which not only show a total lack of research, but are completely and thoroughly answered in the product documentation.

Such questions almost always get downvoted, and are often closed, but some remain open as there isn't a close reason which quite exactly covers this circumstance. Worse, they often collect answers which are almost always low-quality or completely useless.

As you're aware, this is a site for professionals, and as such, reading Google or the product documentation (as appropriate) should be done prior to asking a question.

Examples of such questions (feel free to add more when you spot one):

• http://serverfault.com/q/467773
• http://serverfault.com/q/467779
• Is the ssh key name a part of the authentication?
• http://serverfault.com/q/638497
• How to make sudo -u not require password

In addition to the five standard close reasons we're all used to, a very small number of Stack Exchange sites have a sixth close reason:

• general reference

  This question is too basic; it can be definitively and permanently answered by a single link to a standard internet reference source designed specifically to find that type of information.

Adding this close reason, perhaps with slightly different text making reference to documentation, seems to be a good idea.

I've been noticing an influx of questions lately which not only show a total lack of research, but are completely and thoroughly answered in the product documentation.

Such questions almost always get downvoted, and are often closed, but some remain open as there isn't a close reason which quite exactly covers this circumstance. Worse, they often collect answers which are almost always low-quality or completely useless.

As you're aware, this is a site for professionals, and as such, reading Google or the product documentation (as appropriate) should be done prior to asking a question.

Examples of such questions (feel free to add more when you spot one):

• https://serverfault.com/q/467773
• https://serverfault.com/q/467779
• Is the ssh key name a part of the authentication?
• https://serverfault.com/q/638497
• How to make sudo -u not require password

In addition to the five standard close reasons we're all used to, a very small number of Stack Exchange sites have a sixth close reason:

• general reference

  This question is too basic; it can be definitively and permanently answered by a single link to a standard internet reference source designed specifically to find that type of information.

Adding this close reason, perhaps with slightly different text making reference to documentation, seems to be a good idea.

I've been noticing an influx of questions lately which not only show a total lack of research, but are completely and thoroughly answered in the product documentation.

Such questions almost always get downvoted, and are often closed, but some remain open as there isn't a close reason which quite exactly covers this circumstance. Worse, they often collect answers which are almost always low-quality or completely useless.

As you're aware, this is a site for professionals, and as such, reading Google or the product documentation (as appropriate) should be done prior to asking a question.

Examples of such questions (feel free to add more when you spot one):

• http://serverfault.com/q/467773
• http://serverfault.com/q/467779
• Is the ssh key name a part of the authentication?
• http://serverfault.com/q/638497
• How to make sudo -u not require password

In addition to the five standard close reasons we're all used to, a very small number of Stack Exchange sites have a sixth close reason:

• general reference

  This question is too basic; it can be definitively and permanently answered by a single link to a standard internet reference source designed specifically to find that type of information.

Adding this close reason, perhaps with slightly different text making reference to documentation, seems to be a good idea.

I've been noticing an influx of questions lately which not only show a total lack of research, but are completely and thoroughly answered in the product documentation.

Such questions almost always get downvoted, and are often closed, but some remain open as there isn't a close reason which quite exactly covers this circumstance. Worse, they often collect answers which are almost always low-quality or completely useless.

As you're aware, this is a site for professionals, and as such, reading Google or the product documentation (as appropriate) should be done prior to asking a question.

Examples of such questions (feel free to add more when you spot one):

• http://serverfault.com/q/467773
• http://serverfault.com/q/467779
• Is the ssh key name a part of the authentication?
• http://serverfault.com/q/638497
• How to make sudo -u not require password

In addition to the five standard close reasons we're all used to, a very small number of Stack Exchange sites have a sixth close reason:

• general reference

  This question is too basic; it can be definitively and permanently answered by a single link to a standard internet reference source designed specifically to find that type of information.

Adding this close reason, perhaps with slightly different text making reference to documentation, seems to be a good idea.

I've been noticing an influx of questions lately which not only show a total lack of research, but are completely and thoroughly answered in the product documentation.

Such questions almost always get downvoted, and are often closed, but some remain open as there isn't a close reason which quite exactly covers this circumstance. Worse, they often collect answers which are almost always low-quality or completely useless.

As you're aware, this is a site for professionals, and as such, reading Google or the product documentation (as appropriate) should be done prior to asking a question.

Examples of such questions (feel free to add more when you spot one):

• http://serverfault.com/q/467773
• http://serverfault.com/q/467779
• Is the ssh key name a part of the authentication?
• http://serverfault.com/q/638497/

In addition to the five standard close reasons we're all used to, a very small number of Stack Exchange sites have a sixth close reason:

• general reference

  This question is too basic; it can be definitively and permanently answered by a single link to a standard internet reference source designed specifically to find that type of information.

Adding this close reason, perhaps with slightly different text making reference to documentation, seems to be a good idea.

I've been noticing an influx of questions lately which not only show a total lack of research, but are completely and thoroughly answered in the product documentation.

Such questions almost always get downvoted, and are often closed, but some remain open as there isn't a close reason which quite exactly covers this circumstance. Worse, they often collect answers which are almost always low-quality or completely useless.

As you're aware, this is a site for professionals, and as such, reading Google or the product documentation (as appropriate) should be done prior to asking a question.

Examples of such questions (feel free to add more when you spot one):

• http://serverfault.com/q/467773
• http://serverfault.com/q/467779
• Is the ssh key name a part of the authentication?
• http://serverfault.com/q/638497
• How to make sudo -u not require password

In addition to the five standard close reasons we're all used to, a very small number of Stack Exchange sites have a sixth close reason:

• general reference

  This question is too basic; it can be definitively and permanently answered by a single link to a standard internet reference source designed specifically to find that type of information.

Adding this close reason, perhaps with slightly different text making reference to documentation, seems to be a good idea.