lp:\
:lp=9100@192.168.1.35:\
:sh:\
:mx#0:\
:if=/usr/local/libexec/psif:\
:sd=/var/spool/lpd/lp:\
:lf=/var/log/lpd-errs:#!/bin/sh
IFS="" read -r first_line
first_chars=`expr "$first_line" : '\(....\)'`
case $first_chars in
%!PS|%PDF)
( echo "$first_line" ; cat ) | /usr/local/bin/gs -dSAFER -dNOPAUSE -dBATCH -r600 -q -sDEVICE=pxlmono -sOutputFile=- - && exit 0
exit 2
;;
*)
echo "$first_line" && cat && exit 0
exit 2
;;
esac lpc status lp and lpq -Plp lpc status says
lp:
queuing is enabled
printing is enabled
1 entry in spool area
sending to 192.168.1.35 port 9100 lpq shows the task in queueDec 20 10:15:14 192 lpd[895]: lpd startup: logging=0lpc abort lp
lpc up lp lpc restart lplp:\
:lp=:\
:rm=192.168.1.35:\
:rp=lp1:\
:sh:\
:mx#0:\
:if=/usr/local/libexec/psif:\
:sd=/var/spool/lpd/lp:\
:lf=/var/log/lpd-errs:
lpc down/up to reinitialize (the connection) the print jobrestart { all | printer }
Attempt to start a new printer daemon. This is useful when some
abnormal condition causes the daemon to die unexpectedly, leaving
jobs in the queue. lpq(1) will report that there is no daemon
present when this condition occurs. If the user is the supe‐
ruser, try to abort the current daemon first (i.e., kill and
restart a stuck daemon)FS-6525MFP print server is build-in into device
If you read carefully what "restart" does, it doesn't help in your case since you have a daemon running/working, you should use
lpc abort lp and lpc up lp to kill the daemon and start a new one.With a ping you can confirm if there is a network problem (packet loss?)
Available options:
-c By default, if some remote host has a connection error while try-
ing to send a print request to lpd on a local host, lpd will only
send error message to that remote host. The -c flag causes lpd
to also log all of those connection errors via syslog(3).
-d Turn on SO_DEBUG on the Internet listening socket (see
setsockopt(2)).
-l The -l flag causes lpd to log valid requests received from the
network. This can be useful for debugging purposes.O.K. Haven't noticed that.
It may happen, but the ping restores much faster than lp job.
Not yet. The problem is the laggs start not immediately after reboot, and I do not print that much every day.
Mostly, PDF files, but also some TIFFs, and PSes occasionally. And mostly from command line.
I'll try that, thanks.
I'll say the type of emulation next time I'll get to the printer (it's on my working place, now we have some kind of holidays).
%PDF-1.5...For me, a network problem has to do with the components between the 2 computers that communicate, in your case the wiring and switch, to test the network, you can simulate the traffic of a print job of 5 MB (5,242,880 Bytes) by sending 3,496 packets of 1,500 Bytes each with
ping -c 3496 -s 1500 192.168.1.35.Been strict: NO, but for me "PostScript 3 compatible" mean that a third-party PostScript interpreter is running inside your printer (not the official from Adobe).
According to the manual, you can print PDF, TIFF, JPEG and XPS from USB stick, but I suspect that they transform the file internally before printing it
Yes, but sometimes I even forget about it, still it is printed may be after 20 minutes.
On the contrary, this psif is totally correct for PDFs, but PSes may not have any '%PS' header (and still be correct PostScript files), so it would not work for them. psif can be tested easily without network, and it gives no lags and nice PCL (or should they be called PXL?) files. Yes, it is print/ghostscript9-agpl.
The lag can occur during any kind of file. It occurred before I put this psif in place and when I mixed CUPS and direct printing, when I print ASCII files etc...
Surely they transform somehow internally, but for now I could not make the printer to understand PDFs or PSes from my network. (Also, I was not able to print PSes from flash sticks, what extension it expect? XPS? Is it some variant of PS or just PS?)
lp=/dev/unlpt0 and see if the lag occurHardly so, the problem is present even when I am alone in the office. Although when someone from notebook loses WiFi connection during printing, he has a problem.
Easily. Put PDF or PS from standard input from command line, write standard output to file and find some utility to view .PCL files. (the last one may be less trivial) )
I even do not have USB cable for the printer (and long enough to reach it) )))
Yes, your are right, the start script was from that script from The Handbook, and I've said in #15 and #18 that sending PDF or PS to printer make it consider it is text file and print all these '%PDF...' or '%!PS...' until I stop it by hand. And I do not know (yet?) how to set “the right” emulation. I still shall try the #14 menu.
The hang is with PDFs, TIFFS, PSes etc. Everything it prints. More that that, it can print most of TIFFs without conversion to anything. And, by the way printer processor is slower than CPU on a desktop, so making conversion on desktop is not slower (anyway, a laser printer will do it, the rasterization thing, right?).
).It was PCL6 default emulation.
tcpdump -s 0 -n -i fxp0 host 192.168.1.35 -w filename.pcap