Re: Closing STDIO Caused Pipe Not To Work

Replies are listed 'Best First'.
Re^2: Closing STDIO Caused Pipe Not To Work by Errto (Vicar) on Aug 27, 2007 at 04:45 UTC
--. The question raised by the OP was entirely legitimate, presented clearly, with fairly complete code (except neglecting to say what the external command was), and with reference to an earlier question by the same poster. I see no fault in it other than a failure to use `<code>` tags which is not the most severe crime on the book. Moreover, there is not the slightest indication that this is a homework problem, nor is Anonymous Monk asking us to solve his or her problem from scratch, which is usually the hallmark of such questions. I should also add some that people have genuine and valid reasons for posting anonymously, and absent any other evidence, I would not question that in this case. Those links are great links to suggest to a person who asks vague, poorly worded, poorly formatted, code-free, etc. questions, but is inappropriate in this situation. And while it is true that there are "more than one postings available in the monastery regarding pipes" I don't get the impression you actually looked for any that relate even remotely to the OP's problem in this thread. Update: I should clarify that this node is, in part, in response to Re^3: Closing STDIO Caused Pipe Not To Work as well.	[reply] [d/l]
Re^2: Closing STDIO Caused Pipe Not To Work by Anonymous Monk on Aug 27, 2007 at 04:18 UTC
I am the original poster of the question. Thanks for sending me around chasing the geese. I just spent 1 1/2 hours looking thru perl monks web site and only found posting http://www.perlmonks.org/?node_id=412947 similar to mine with no solution. If you know where it is, why don't you just point me to it instead of being sarcastic.	[reply]
Re^2: Closing STDIO Caused Pipe Not To Work by Anonymous Monk on Aug 27, 2007 at 03:21 UTC
In other words, you don't know the answer but you think you can gain some XP by posting this crappy, useless piece of boiler plate.	[reply]
Re^3: Closing STDIO Caused Pipe Not To Work by atemon (Chaplain) on Aug 27, 2007 at 04:17 UTC
Hey monk, I don't know who you are. First I thought NOT to reply. But later I changed my mind thinking that, if I am NOT replying, others may think I agree with you. Sorry monks if its offending. Dear anonymous (?) why are you so frustrated and angry regarding reply ? We are here NOT to do homework for you. I was reading your posts Client Pull Not Working correctly and close STDOUT does not work, why? from the beginning. All the three (including this ) threads together looks like a homework done. I have my own working version of your program as I used to try & learn any useful code. Back to the problem. Whats the error you get when you open the pipe? You says that you have a problem at opening pipe and didn't mention anything about the error message you got. Did you try whats discussed at Why doesn't open() return an error when a pipe open fails? and perlipc isn't it a fact that you are afraid of loosing XP and thats the reason to post this "home work" as "Anonymous"? Please do not think that all monks out here are too much XP conscious. I know this post can bring me lots of -- XPs Update: http://www.perlmonks.org/?node_id=412947 similar to mine with no solution. If you know where it is, why don't you just point me to it instead of being sarcastic. We are here NOT to do homework for others! Cheers ! --VC There are three sides to any argument..... your side, my side and the right side.	[reply]
Re^4: Closing STDIO Caused Pipe Not To Work by Anonymous Monk on Aug 27, 2007 at 04:24 UTC
And may I say that this is not a HW problem. Doesn't school ended back in the beginning of August ot June? I don't know who the other Anonymous poster is by the way.	[reply]
Re^4: Closing STDIO Caused Pipe Not To Work by Anonymous Monk on Aug 27, 2007 at 04:41 UTC
First you suggest he should read how to post a question, but his question is perfectly well formed and properly formatted. Next you suggest he SuperSearch for pipes, but his question has as much to do with pipes as it does fork. Both are required to describe problem, but neither are the direct cause of the problem that he clearly describes. Next, when challenged, you point to a random selection of pipe related posts, none of which has anything to do with the question asked. And finally, you resort to that other hoary ol' cheshnut. It looks like homework. Hint: The answer to the question isn't posted anywhere on PM. So twonk, like that other guy said, if you don't know the answer, just shut up.	[reply]