[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: samba printing problems



On Wed, 22 Jul 1998 servis@purdue.edu wrote:

> Another way to test the source of the problem is to print to a file on
> Win3.1. Then send the print file directly to the printer by 'cat
> <file.prn> > /dev/lpN'  where N is probably 1 for 2.0.X kernels and 0
> for 2.1.X kernels.  This will eliminate samba and lpr.  If that works
> then redefine the 'print command' in your smb.conf to something like the
> above 'print command = /bin/cat %s > /dev/lpN'.  If that works then it
> is lpr.  Probably a filter. You should be passing the samba print data
> directly to the lp device. I.E. no 'if' in the printcap file for the
> printer used for samba.

print command = /bin/cat %s > /dev/lp1

in smb.conf just sends the print jobs into oblivion.  At least now it's
not wasting paper with the garbled printouts. :(

cat file > /dev/lp1

worked, but it's a pain to ftp the file to Linux, telnet in and run cat
every time I want to print anything with graphics in it.

Here's /etc/printcap and as you can see, there is no 'if'

(I've also tried it without the df= and tf= lines, but it didn't help.)

stylus|Generic dot-matrix printer entry:\
        :lp=/dev/lp1:\
        :sd=/var/spool/lpd/stylus:\
        :df=/etc/filter.ps:\
        :tf=/etc/filter.pcl:\
        :af=/var/log/lp-acct:\
        :lf=/var/log/lp-errs:\
        :pl#66:\
        :pw#80:\
        :pc#150:\
        :mx#0:\
        :sh:


The output of lpq is sure interesting!

The junk below is all from ONE print job from ONE Win3.1 computer.  Think
this could be part of the problem?  Note that I had to take the printer
offline to get all the pieces to be in the queue together.

server2# lpq -Pstylus
stylus is ready and printing
Rank   Owner      Job  Files                                 Total Size
active compman    254  /tmp/HYUNDAIXXX.a14088                4096 bytes
1st    compman    255  /tmp/HYUNDAIXXX.a14088                2304 bytes
2nd    compman    256  /tmp/HYUNDAIXXX.a14088                4096 bytes
3rd    compman    257  /tmp/HYUNDAIXXX.a14088                2048 bytes
4th    compman    258  /tmp/HYUNDAIXXX.a14088                3584 bytes
5th    compman    259  /tmp/HYUNDAIXXX.a14088                4096 bytes
6th    compman    260  /tmp/HYUNDAIXXX.a14088                256 bytes
7th    compman    261  /tmp/HYUNDAIXXX.a14088                4096 bytes
8th    compman    262  /tmp/HYUNDAIXXX.a14088                3328 bytes
9th    compman    263  /tmp/HYUNDAIXXX.a14088                4096 bytes
10th   compman    264  /tmp/HYUNDAIXXX.a14088                2560 bytes
11th   compman    265  /tmp/HYUNDAIXXX.a14088                2560 bytes
12th   compman    266  /tmp/HYUNDAIXXX.a14088                2816 bytes
13th   compman    267  /tmp/HYUNDAIXXX.a14088                164 bytes

Sorry to anyone who finds this a little long.  Normally I wouldn't send
such big chunks of files and screen output to the list like this, but I'm
so confused at the moment that explaining anything would be difficult (and
prone to error). 



--  
Unsubscribe?  mail -s unsubscribe debian-user-request@lists.debian.org < /dev/null


Reply to: