> exec '/bin/original-print-something', @processed_args or die "Couldn't > exec /bin/original-print-something: $!"; > > > > My problems come when I get a command-line like this: > # cat /etc/hosts | /bin/print-something -a -b some-option -c > someother-option > > In this case, my LOG file will recored the args as "-a -b some-option -c > someother-option", but not the piped input. Where did it go? Is there > a variable that will contain that piped data so I can manipulate that > stuff, too? >
I'm just a beginner myself, but you may want to look into the diamond operator, <>. From the little that I've learned about (and used) it, you can use it to write code that will support input/output piping. If you've got a copy of 'Learning Perl' there's some information on it. I'm sure there are web docs too. > --Errin > > -- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > <http://learn.perl.org/> <http://learn.perl.org/first-response> > -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
