![]() |
On Thu, 16 Nov 2006, Jean-Pierre Radley wrote: > Aidan Van Dyk typed (on Thu, Nov 16, 2006 at 05:12:02PM -0500): > | * Jean-Pierre Radley <jpr@xxxxxxx> [061114 20:39]: > | > | > Running 'bin/faxrcvd "recvq/fax000001600.tif" "tty2A" "000003116" ""', > | > with awk: > | > > | > awk: Syntax error > | > at line 6 of program << > | > function p(varn ... >> in function p > | > context is > | > printf >>> "export <<< > | > 1 extra { > | > awk: illegal statement > | > at line 6 of program << > | > function p(varn ... >> in function p > | > bin/faxrcvd: : cannot execute > | > bin/faxrcvd: syntax error at line 3: `}' unexpected > | > > | > with mawk: > | > > | > mawk: line 6: runaway string constant "export ... > | > bin/faxrcvd: : cannot execute > | > bin/faxrcvd: syntax error at line 3: `}' unexpected > | > > | > with gawk: > | > > | > gawk: cmd. line:5: printf "export > | > gawk: cmd. line:5: ^ unterminated string > | > bin/faxrcvd: : cannot execute > | > bin/faxrcvd: syntax error at line 3: `}' unexpected > | > | It seems to be a problem with: > | /opt/K/SCO/Unix/6.0.0Ni/usr/bin/sh > | > | I just can't figure out what the quoting rules on that sh seem to be. > | > | Using bash seems to work. /bin/sh works on the solaris systems I've > | used works... > | > | We should probably change the scripts in $SPOOL/bin to use the > | @SCRIPT_SH@ instead of being hard-coded. Good plan. > > No other program or script has ever blamed /bin/sh on any SCO system > I've run; its man page ends with: /bin/sh on OpenServer is quite lame. Try one of the shells in /u95/bin > > Tim, have you played with this beta version? Not yet. Been busy with other things (that pay the bills). :-) -- Tim Rice Multitalents (707) 887-1469 tim@xxxxxxxxxxxxxxxx ____________________ HylaFAX(tm) Users Mailing List _______________________ To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*