Re^3: how to supress stdout

Replies are listed 'Best First'.
Re^4: how to supress stdout by parv (Parson) on Dec 13, 2008 at 00:07 UTC
First, standard output is redirected to /dev/null. Assuming 1 is standard output file descriptor & 2 is standard error, standard error is also redirected to the same place as standard output (which is to /dev/null). Above will work only when a bourne-like shell (FreeBSD /bin/sh, bash, zsh, etc.) handles the redirection.	[reply]
Re^5: how to supress stdout by ikegami (Patriarch) on Dec 13, 2008 at 17:26 UTC
Aren't fd 1 and 2 stdout and stderr by definition?	[reply]
Re^6: how to supress stdout by parv (Parson) on Dec 14, 2008 at 09:41 UTC
Yes, they are. As for the assumption in "Assuming 1 is standard output ...", if fd's 1 & 2 have been already closed & opened to some other fd's (before redirection), would fd's 1 & 2 still work for the purpose (of redirection after being redirected)?	[reply]
Re^7: how to supress stdout by ikegami (Patriarch) on Dec 14, 2008 at 16:13 UTC
Re^5: how to supress stdout by Bloodnok (Vicar) on Dec 13, 2008 at 16:54 UTC
... and there's me thinking that is only true if the re-direction is done in the shell - perl seems to 'know' how 'proper' re-direction works when done as in this example i.e. in a call to one of the `open()` functions. Maybe it's senility setting in big time ?? A user level that continues to overstate my experience :-))	[reply] [d/l]
Re^6: how to supress stdout by ikegami (Patriarch) on Dec 13, 2008 at 17:02 UTC
No, Perl doesn't know. `open` invokes the shell when it sees shell meta characters such as `>` in the command.	[reply] [d/l] [select]
Re^7: how to supress stdout by Bloodnok (Vicar) on Dec 13, 2008 at 17:13 UTC
Re^8: how to supress stdout by ikegami (Patriarch) on Dec 13, 2008 at 17:23 UTC
Some notes below your chosen depth have not been shown here