Re: LPRng: Problem with 'file'
On Tue, 24 Jun 2003, Ryan Novosielski wrote: Date: Tue, 24 Jun 2003 18:09:24 -0400 (EDT) From: Ryan Novosielski [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: LPRng: Problem with 'file' There is a LOT different. The most noticeable seems to be the outputs of cmp -l in the first column are about 2-3 times larger than the second one. I'm guessing maybe vi chopped some long lines, if that's what those numbers are? Why would ifhp care? In any case, I'm going to produce a set of small df's to post and see what the consensus is... this is driving me /nuts/. Standard unix vi chops all binary zeroes, and yes, you do get problems with long lines as well. In my experience print data from MS-Windows should be treated as binary data, and any modifications inclusing stripping or inserting CR characters tend to produce garbage. Postscript data, however, can normaly be treated as text files without too much problems. 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. -
LPRng: OF banner program problems
Hello, There seems to be a problem with the banner filter program (of) execution in LPRng versions above 3.8.15. The OF filter starts ok, but after suspending the IF filter never kicks in and just the banner page gets printed. It works as expected with LPRng version 3.8.15 however versions 3.8.19 and above don't. I've been plagued with this problem for quite some time but only just come to realise that this occurs. Does anyone have any suggestions? is this a configuration error or a bug? - as I've used identical configurations with both .15 and .19+ I'd imagine it is a bug. I'll try and have a look at the code to see if I can narrow the problem down, as soon as I have time! cheers, sam -- CERN, Geneva IT - Product Support - Unix Infrastructure E-mail: [EMAIL PROTECTED] - 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. -
Re: LPRng: Problem with 'file'
Ryan Novosielski wrote: 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. 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 I get access-denied on Job927-df-data.prn, Ryan. (Not that I really expect to get anywhere with this, mind you.) (Hmm. Have you updated to a recent rev of file, BTW?) -- - Dave Lovelace [EMAIL PROTECTED] [EMAIL PROTECTED] - 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. -
Re: LPRng: Problem with 'file'
Yes, I have since fixed the permissions -- sorry about that. I am running file 3.4.1, just because I am leery of switching to a completely different rev without knowing the affect it will have on LPRng. AFAIK, 3.4.1 is the most recent 3.x release. _ _ _ _ ___ _ _ _ |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 Wed, 25 Jun 2003, Dave Lovelace wrote: Ryan Novosielski wrote: 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. 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 I get access-denied on Job927-df-data.prn, Ryan. (Not that I really expect to get anywhere with this, mind you.) (Hmm. Have you updated to a recent rev of file, BTW?) -- - Dave Lovelace [EMAIL PROTECTED] [EMAIL PROTECTED] - 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. -
Re: LPRng: Problem with 'file'
Ryan Novosielski wrote: Yes, I have since fixed the permissions -- sorry about that. I am running file 3.4.1, just because I am leery of switching to a completely different rev without knowing the affect it will have on LPRng. AFAIK, 3.4.1 is the most recent 3.x release. Ryan, This is definitely interesting. On our (now old creaky) SYSV Unix box, running the file that came with it, Here's what I see for your two files: Job927-df-PCL.prn: data Job927-df-data.prn: English text (Can't make it tell me what the rev on file is.) On our RH Linux (old - RH 6.2) system, which is running file 3.28, I get: Job927-df-PCL.prn: HP Printer Job Language data Job927-df-data.prn: data The HP Printer Job Language data is what you'd want it to show, am I right? The relevant entries from the magic file are somewhere in this mess, I think: -snip-snip-snip-snip-snip-snip-snip-snip- # HP Printer Job Language 0 string [EMAIL PROTECTED] HP Printer Job Language data # HP Printer Job Language # The header found on Win95 HP plot files is the Silliest Thing possible # (TM) # Every driver puts the language at some random position, with random case # (LANGUAGE and Language) # For example the LaserJet 5L driver puts the PJL ENTER LANGUAGE in line 10 # From: Uwe Bonnes [EMAIL PROTECTED] # 0 string [EMAIL PROTECTED] HP Printer Job Language data 0 string \0 %s 0string \0 %s 0 string \0 %s 0 string \0 %s #15string \ ENTER\ LANGUAGE\ = #31string PostScript PostScript # HP Printer Control Language, Daniel Quinlan ([EMAIL PROTECTED]) 0 string \033E\033 HP PCL printer data 3 string \l0A - default page size 3 string \l1A - US executive page size 3 string \l2A - US letter page size 3 string \l3A - US legal page size 3 string \l26A - A4 page size 3 string \l80A - Monarch envelope size 3 string \l81A - No. 10 envelope size 3 string \l90A - Intl. DL envelope size 3 string \l91A - Intl. C5 envelope size 3 string \l100A - Intl. B5 envelope size 3 string \l-81A - No. 10 envelope size (landscape) 3 string \l-90A - Intl. DL envelope size (landscape) -snip-snip-snip-snip-snip-snip-snip-snip- I suggest that you look at your magic file. Consider patching these things in. On later revs of RedHat, we've had to run file with a special option to create a file called (IIRC) magic.mgc before any changes have any effect; I'd guess that's for a later rev of file than you're running, but I really don't know can't check right now. I'll actually *look* at your files tomorrow when I find time. -- - Dave Lovelace [EMAIL PROTECTED] [EMAIL PROTECTED] - 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. -
LPRng: [ANNOUNCE] PyKota v1.09beta is out with full LDAP support !
Hi, I'm pleased to announce that PyKota v1.09beta is out with full LDAP support. PyKota is a GPLed but commercially supported Print Quota management system which works with CUPS and LPRng. Learn more about it at : http://www.librelogiciel.com/software/PyKota/action_Presentation The more important changes since 1.08 are : - LDAP schema finalized (hopefully) and full LDAP support added to store quota information. You can now store quota information either in PostgreSQL or in an OpenLDAP directory. Tested only with OpenLDAP, not sure if the python-ldap module at sourceforge works with other LDAP servers. Please report any problems. - The repykota command now only returns the current user's quota information unless launched as the root user. When launched as root, the command line accepts users or groups names which can eventually contain wildcards, and returns quota information for each user or group whose name matches. - The warnpykota command behaves the same as the repykota command. - Severe database access optimizations were done, especially in the repykota command. You are encouraged to download and try to break this version, especially the LDAP backend. Please report any problem. FYI if nothing bad happens, 1.09 final will be released by the end of the week, with tarballs and rpms as usual for people who purchased an official package. Only bug fixes will be incorporated from now until 1.09final is released. bye, and thanks to all who made this possible ! Jerome Alet - 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. -
Re: LPRng: Problem with 'file'
Ryan, Using file version 3.37 on Debian Linux and file version 3.39 on Solaris 9, I get the same output. Job927-df-data.prn: data Job927-df-PCL.prn: HP Printer Job Language data --- Keith Rinaldo Systems Administrator College of Engineering University of Nevada, Las Vegas - Original Message - From: Ryan Novosielski [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 7:23 AM 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. 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 _ _ _ _ ___ _ _ _ |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 Wed, 25 Jun 2003, Villy Kruse wrote: On Tue, 24 Jun 2003, Ryan Novosielski wrote: Date: Tue, 24 Jun 2003 18:09:24 -0400 (EDT) From: Ryan Novosielski [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: LPRng: Problem with 'file' There is a LOT different. The most noticeable seems to be the outputs of cmp -l in the first column are about 2-3 times larger than the second one. I'm guessing maybe vi chopped some long lines, if that's what those numbers are? Why would ifhp care? In any case, I'm going to produce a set of small df's to post and see what the consensus is... this is driving me /nuts/. Standard unix vi chops all binary zeroes, and yes, you do get problems with long lines as well. In my experience print data from MS-Windows should be treated as binary data, and any modifications inclusing stripping or inserting CR characters tend to produce garbage. Postscript data, however, can normaly be treated as text files without too much problems. 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. - - 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
Re: LPRng: Problem with 'file'
The 1st 1200 bytes of the file are all zero (AKA 0x00) immediately after that you have the normal ESC code for some PJL stuff Try stripping off just those bytes or get http://www.scs.ryerson.ca/mforrest/printing/Job927-df-mf.prn In the -PCL- you don't have the ESC code to end the job.. shouldn't be a problem if the printer is set to auto personality, but I've always seen it there. If you just strip the zeros from the start of the file I'm guessing it will work fine. I haven't tried printing it 'cause I'm lazy right now and don't want to have to walk to the printer :) mATT * A neurotic worries about going crazy, but never will A psychotic IS crazy, but doesn't worry about it! ... Don't worry, be happy!!! :} * - 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. -
