Re: Working lp5250d last week, now refuses

["Mike" <mcravens@xxxxxxxxxxxxxx>]

Wow that's great stuff to know as one plans and charts their way forward
with this program.    However I seem for the moment to have answered my own
situation by checking the ENV I saw no path inclusion of   /usr/local/bin,
so I edited the  /root/.bash_profile added the /usr/local/bin to the path,
and my problem was resolved.

Hard to believe but it would seem that the path statement was there last
week but was lost this week...I know, can't happen theoretically.

Thanks for the prompt reply, now if you only had some answers on the subject
of Unix to Linux printing as well, we're sharing two hosts, and AS400 and an
HP9000.  The lp5250 took time and wasn't really 'easy', but it's  snap
compared to trying to get big brother HP to print to cousin Linux.

Thanks AGain

Mike
----- Original Message -----
From: Scott Klement <klemscot@klements.com>
To: <LINUX5250@midrange.com>
Sent: Wednesday, May 03, 2000 2:51 PM
Subject: Re: Working lp5250d last week, now refuses


> I've run into this problem several times before... it seems to relate to
> the sizes of the variables that are declared in lp5250d.c
>
> For example, if your "output command" is more than 30 chars long, it will
> cause problems because lp5250d only allocates 30 bytes to store it in.
> When the system goes to actually print something, it does a popen() to
> that output command, which causes it to assert or even segmentation fault.
>
>  "scs2ascii | lpr -Plinuxoptra"
>   123456789012345678901234567890
>
> This is cutting it close, but doesnt appear to overflow.  Is that the
> string your using, or is it a bit more complex?
>
> Also, the same problem exists with the hostname (20 chars), the
> session name (20 chars -- tho 10 is the AS/400's max so this shouldnt be
> too big of an issue), and the logfile's name (20 chars).
>
> Perhaps these parameters should be allocated with malloc(), based on
> the size of the arguments, so that we don't have this type of overflow?
> I could write up a patch if you'd like...
>
> Hope that helps...
>
>
>
> On Wed, 3 May 2000, Mike wrote:
>
> > to work.  The command prompt when issued creates the device, goes
active, but the moment a stored print job in the queue is released the
connection drops with a 'hardware error msg' on the qsysopr msgs and the
connection is lost.
> >
> > I can do a test print from printtool successfully and I can do a | to
lpr -Plinuxoptra successfully, but I can no longer get a test print from the
AS400.  The device will stay active if there is an alignment msg generated,
until I answer the msg.
> >
> > The only thing I did over the weekend was to try to make up some X
desktop icons to call the lp5250d program from the desktop, but I"m back to
trying the command line approach now, since none of them would work.
> >
> > Thanks
> >
> > Mike
> >
>
> +---
> | This is the LINUX5250 Mailing List!
> | To submit a new message, send your mail to LINUX5250@midrange.com.
> | To subscribe to this list send email to LINUX5250-SUB@midrange.com.
> | To unsubscribe from this list send email to
LINUX5250-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
david@midrange.com
> +---
>

+---
| This is the LINUX5250 Mailing List!
| To submit a new message, send your mail to LINUX5250@midrange.com.
| To subscribe to this list send email to LINUX5250-SUB@midrange.com.
| To unsubscribe from this list send email to LINUX5250-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---