We have had a number of instances over the last month where we have
received the following message when our application has output reports
to the lpr subsystem on RedHat Linux 6.0:
No way to print this type of input file: ES-channel Fasttracker
"oktalyzer" module sound
By turning off the printer I was able to capture the attached files. One
is identified by the file command as a asci text file with escape
sequences.
The other is identified by the file command as sound file. It
consequently is not printed since linux has decided that it is a sound
file and evidently is trying to process it with some other program or
filter.
The only difference in the two files is the absence of two "D's" which
were deleted from the word DRESHLER in the description field of last two
records. In subsequent test we determined that deleting the "D" from
either of the two or changing the certain characters within any of the
description fields to lower case will change the signature of the file.
What signature does the file command or the Linux print spooler, or
whatever determines what to do with a file, when the lpr command is
used?
Below is the screen capture of the commands and response:
[root@dpnacct /junk]# file dfA341*
dfA341ATCuuLX: ES-channel Fasttracker "oktalyzer" module sound
[root@dpnacct /junk]# lpr -PNP02 dfA341*
parport 0: detected irq 7; use procfs to enable interrupt-driven
operation
[root@dpnacct /junk]# file dfA339*
dfA339ADbvfKx: ASCII text (with escape sequences)
Thanks
--
Steve Dixon
Dpn, Incorporated
System Administrator
Phone - 702.873.3282
Email - [EMAIL PROTECTED]
dfA339ADbvfKx
dfA341ATCuuLX
