At this time I am not sure what the problem is.
Our application generates files, theses files may contain characters in the
range of 128-255.
We are then trying to print this file (Red Hat 7.0) to a c.itoh CI-5000
printer( supposed to be fully comptatible with linux), but those files which
contai
ersonally or implicitly by virtue of what the software
generates), and arranging printing accordingly.
All my printing (except occasionally to a Stylus Colour) is to a
PostScript printer, and lpr simply feeds the file to the printer.
If it's not a PS file, then it's converted beforehand
so, is there any solution to this problem? i tried just commenting out
the parts of magic that were causing the problem but then i just get
empty sheets of paper.
"H. Peter Anvin" wrote:
>
> John DeDourek wrote:
> >
> > I don't have a solution. I do agree t
John DeDourek wrote:
>
> I don't have a solution. I do agree that it is useful for the printing
> system to automatically identify files and treat them with the
> appropriate
> filter. It is good to have the "file" utility make a guess as to file
> type.
I sent a more detailed response via e-mail. This is a more general
reply to the list because I believe this represents an interesting
problem.
Printing apparently uses the "magic rules" in /usr/share/magic to
determine file type for printing.
The original Unix "magic" syste
Steve Dixon wrote:
>
[]
> 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?
[]
> [root@dpnacct /junk]# file dfA341*
> dfA341ATCuuLX: ES-channel Fasttracker "oktalyzer" module sound
file utility just l
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 printe
Steve Dixon wrote:
>
> i know that on our SCO boxes the samba that we have writes to a
> smbprint.log in /tmp, but as far as i can see there isnt such a thing on
> linux. the version of samba on these SCO boxes if rather old, so i dont
> know if that has anything to do with it or not.
> Steve
>
is any such log file, be it
> > normal printing or through samba printing. thanks.
>
> This is the default operation:
> [root@emu log]# grep lpd messages | head
> Oct 3 09:19:23 emu lpd[19965]: possum.os2.ami.com.au requests recvjob lp
> Oct 3 15:27:53 emu lpd[24820]: emu.os2.ami.c
file, be it
> normal printing or through samba printing. thanks.
This is the default operation:
[root@emu log]# grep lpd messages | head
Oct 3 09:19:23 emu lpd[19965]: possum.os2.ami.com.au requests recvjob lp
Oct 3 15:27:53 emu lpd[24820]: emu.os2.ami.com.au requests printjob lp
Oct 3 17:14:0
where is the log file that shows who prints what to where on a server
that is used as a printserver? ive looked everywhere and cannot find
anything in any file that says a job has been run through. i know the
lpc commands but i wanted to know if there is any such log file, be it
normal printing
11 matches
Mail list logo
