Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

In UNIX, a file's read and write permissions are independent, so you can make a file writable, but not readable. If I trust someone to write to a file, why wouldn't I want them to be able to read it? If there's important stuff in there, but I don't want him to read it, then why would I give him the ability to overwrite it?

share|improve this question

closed as off topic by MaQleod, soandos, Diogo, ChrisF, Ƭᴇcʜιᴇ007 Nov 5 '12 at 12:55

Questions on Super User are expected to relate to computer software or computer hardware within the scope defined by the community. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about reopening questions here.If this question can be reworded to fit the rules in the help center, please edit the question.

An upload-only folder. Perhaps a person implementing a folder that permits students to upload their homework. – Zoredache Nov 5 '12 at 7:25

Well, you can have multple processes to write to a file but you don't want them to see what each other is writing to.

In another word, let's say you have a bank system. Each time a business makes a trasaction, you allow them to write it to a file. But you don't want the business to read what other businesses wrote.

Does this make sense?

share|improve this answer

Not the answer you're looking for? Browse other questions tagged .