I don't like to do this mainly because ifhp does a good job of communicating with the printers and I like to use it for that purpose -- unless I can just set it as an of and that's it...
Regardless, I like to have that layer of protection against badly formed jobs (seems to be working a little TOO well ;)). ---- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | | Ryan Novosielski - Jr. UNIX Systems Admin |$&| |__| | | |__/ | \| _| | [EMAIL PROTECTED] - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent. | IST/ACS - NJMS Medical Science Bldg - C630 On Thu, 26 Jun 2003, Villy Kruse wrote: > On Wed, 25 Jun 2003, Ryan Novosielski wrote: > > > Date: Wed, 25 Jun 2003 10:23:54 -0400 (EDT) > > From: Ryan Novosielski <[EMAIL PROTECTED]> > > Reply-To: [EMAIL PROTECTED] > > To: [EMAIL PROTECTED] > > Subject: Re: LPRng: Problem with 'file' > > > > Treating it as data is fine with me -- however, when file can't figure out > > what it is, there is a problem, as I do check for file type with ifhp and > > it will refuse unrecognized file types. > > > > In my setup I would route anything comming from a MS-Win system to a printer > queue which have no filter what so ever, and leave the filtering entries to > be used by unix users. > > > > > As you can see from the files below, vi appears to have halved the > > contents of the file -- I'm assuming that the file after vi is done is no > > longer usable. Perhaps this question is now becoming one that is more for > > the "file" mailing list, but I had said that I would post the files in > > question regardless. The curious thing is that file, AFAIK, looks at the > > beginning of a file. vi would not likely be changing the beginning of the > > first line of the file that signals PCL data, so it doesn't make sense > > that it would have an effect on that (not to me, anyway). Also interesting > > is that this printer doesn't seem to use PJL prior to its PCL stream, > > which is odd from my experience. Here is the URL: > > > > http://www.umdnj.edu/~novosirj/PCL-data-problem > > > > > > Hexadecimal dump of the two files. The dump is incomplete, just enough > to get the point. > > The file /var/tmp/xxx/Job927-df-data.prn had 1200 bytes of leading binary > zeroes. Also note the data at 00500: in the data.prn file and compare with > the data at position 0050: in the PCL.prn file. > > > :::::::::::::: > /var/tmp/xxx/Job927-df-PCL.prn.hex > :::::::::::::: > 00000000: 1b 25 2d 31 32 33 34 35 58 40 50 4a 4c 20 4a 4f [EMAIL PROTECTED] JO > 00000010: 42 20 4e 41 4d 45 3d 22 33 65 66 38 36 39 33 30 B NAME="3ef86930 > 00000020: 31 34 38 31 6e 6f 76 6f 73 69 72 6a 22 0a 40 50 1481novosirj"[EMAIL > PROTECTED] > 00000030: 4a 4c 20 45 4e 54 45 52 20 4c 41 4e 47 55 41 47 JL ENTER LANGUAG > 00000040: 45 3d 50 43 4c 33 47 55 49 0a 1b 2a 6f 35 57 04 E=PCL3GUI..*o5W. > 00000050: 09 1b 2a 6f 35 57 04 0d 0d 84 1b 2a 6f 35 57 0a ..*o5W.....*o5W. > 00000060: 05 1b 26 6c 37 48 1b 26 6c 30 4d 1b 2a 6f 37 57 ..&l7H.&l0M.*o7W > 00000070: 08 09 07 01 01 1b 26 6c 32 41 1b 26 6c 2d 32 48 ......&l2A.&l-2H > 00000080: 1b 2a 6f 35 57 0a 01 1b 2a 6f 35 57 07 08 02 1b .*o5W...*o5W.... > 00000090: 2a 6f 30 4d 1b 26 75 33 30 30 44 1b 2a 70 30 58 *o0M.&u300D.*p0X > 000000a0: 1b 2a 70 33 35 59 1b 2a 67 32 36 57 02 04 01 2c .*p35Y.*g26W..., > > :::::::::::::: > /var/tmp/xxx/Job927-df-data.prn.hex > :::::::::::::: > Same > 000004b0: 1b 25 2d 31 32 33 34 35 58 40 50 4a 4c 20 4a 4f [EMAIL PROTECTED] JO > 000004c0: 42 20 4e 41 4d 45 3d 22 33 65 66 38 36 39 33 30 B NAME="3ef86930 > 000004d0: 31 34 38 31 6e 6f 76 6f 73 69 72 6a 22 0a 40 50 1481novosirj"[EMAIL > PROTECTED] > 000004e0: 4a 4c 20 45 4e 54 45 52 20 4c 41 4e 47 55 41 47 JL ENTER LANGUAG > 000004f0: 45 3d 50 43 4c 33 47 55 49 0a 1b 2a 6f 35 57 04 E=PCL3GUI..*o5W. > 00000500: 09 00 00 00 1b 2a 6f 35 57 04 0d 00 0d 84 1b 2a .....*o5W......* > 00000510: 6f 35 57 0a 05 00 00 00 1b 26 6c 37 48 1b 26 6c o5W......&l7H.&l > 00000520: 30 4d 1b 2a 6f 37 57 08 09 00 00 07 01 01 1b 26 0M.*o7W........& > 00000530: 6c 32 41 1b 26 6c 2d 32 48 1b 2a 6f 35 57 0a 01 l2A.&l-2H.*o5W.. > 00000540: 00 00 00 1b 2a 6f 35 57 07 08 00 00 02 1b 2a 6f ....*o5W......*o > 00000550: 30 4d 1b 26 75 33 30 30 44 1b 2a 70 30 58 1b 2a 0M.&u300D.*p0X.* > 00000560: 70 33 35 59 1b 2a 67 32 36 57 02 04 01 2c 01 2c p35Y.*g26W...,., > > > > -- > Villy > > > ----------------------------------------------------------------------------- > YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST > The address you post from MUST be your subscription address > > If you need help, send email to [EMAIL PROTECTED] (or lprng-requests > or lprng-digest-requests) with the word 'help' in the body. For the impatient, > to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED] > with: | example: > subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED] > unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED] > > If you have major problems, send email to [EMAIL PROTECTED] with the word > LPRNGLIST in the SUBJECT line. > ----------------------------------------------------------------------------- > ----------------------------------------------------------------------------- YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST The address you post from MUST be your subscription address If you need help, send email to [EMAIL PROTECTED] (or lprng-requests or lprng-digest-requests) with the word 'help' in the body. For the impatient, to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED] with: | example: subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED] unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED] If you have major problems, send email to [EMAIL PROTECTED] with the word LPRNGLIST in the SUBJECT line. -----------------------------------------------------------------------------
