When I run that command, I now get - [EMAIL PROTECTED] bin]# /usr/bin/perl mailgrep.pl Can't modify constant item in scalar assignment at mailgrep.pl line 27, near ">" syntax error at mailgrep.pl line 27, near ">" syntax error at mailgrep.pl line 30, near "$queue) " syntax error at mailgrep.pl line 64, near "<" syntax error at mailgrep.pl line 64, near ">" syntax error at mailgrep.pl line 71, near "}" Execution of mailgrep.pl aborted due to compilation errors. [EMAIL PROTECTED] bin]#
Ron -----Original Message----- From: Matt Kettler [mailto:[EMAIL PROTECTED] Sent: Thursday, August 19, 2004 12:00 PM To: Ronald I. Nutter; [EMAIL PROTECTED] Subject: RE: Mailgrep perl script problem At 11:53 AM 8/19/2004, Ronald I. Nutter wrote: >I have a file called perl and perl5.8.3 in the /usr/bin directory. I >ran vi against the perl file and what was on the screen didn't look >like any text file I had ever seen. Fair enough, I just wanted to make sure you didn't have some strange situation where perl was in /usr/local/bin instead of /usr/bin. does the following command produce the same error (forcing a specific interpreter to be called): $/usr/bin/perl mailgrep.pl
