open/close and stderr

Ok. Thanks for the clarification. I'm also reviewing the manual page for File::Temp again to see what I may have missed the earlier times. It often helps to try re-reading on a different display device.

As for the code snippet, the pipe gets opened and closed immediately because as it stands the output from the process it calls goes to the temporary file which is read later on further down in the script. The only errors (I think) that could be caught from the open/close itself would be handled by the or die() part. The reason for a two-step approach is that otherwise the diagnostic messages from the program, "tidy", go to stderr and I have not found a way to redirect stderrr properly under Fast-CGI. So I figure the temporary file is the way to go and to leave stderr alone. I tried a lot of ways to redirect stderr, documented and made up, which all work from the shell, but do not work via Fast-CGI.

The data does not need to be in a file, it can be read as strings maybe better. It's just that the stderr issue with Fast::CGI seems to prevent that.

Comment on open/close and stderr

Replies are listed 'Best First'.
Re: open/close and stderr by haukex (Archbishop) on Mar 22, 2018 at 21:25 UTC
The only errors (I think) that could be caught from the open/close itself would be handled by the `or die()` part. No, sorry, with a piped open you need to check `close` for errors as well, as described in close. I have not found a way to redirect stderrr properly under Fast-CGI I unfortunately don't have the time right now to spin up a FastCGI environment, but I would suggest trying both IPC::Run3, as well as a system call inside of Capture::Tiny's `capture` (as shown in its docs). I've had very good experiences with both of those modules. As for the code snippet, the pipe gets opened and closed immediately because as it stands the output from the process it calls goes to the temporary file which is read later on further down in the script. While I'm still having a bit of trouble matching your description to your code (maybe I'm just being dense at the moment), what I am getting from your code is that perhaps tidy is sending things to its `STDOUT` that you want to suppress using the piped open? Since the modules I named above capture both `STDOUT` and `STDERR`, again I'd suggest giving them a try.	[reply] [d/l] [select]
Re: open/close and stderr by marto (Cardinal) on Mar 22, 2018 at 15:29 UTC
As a side note, if you're changing the post titles in your replies, please don't, How do I compose an effective node title?.	[reply]
Re^2: open/close and stderr by mldvx4 (Hermit) on Mar 22, 2018 at 15:45 UTC
Ok. I had considered them a change of topic, but if it's not a big enough change, then I'll leave them as they are.	[reply]
Re^3: open/close and stderr by marto (Cardinal) on Mar 22, 2018 at 15:54 UTC
Cool, it makes Newest Nodes and Recently Active Threads difficult to track threads.	[reply]