Re: lp5250d crashing

I think I fixed the bug with the tracefile...  Or at least, I found a
really serious error in the code, which is now fixed in CVS :)

(This bug actually should've affected tn5250, gtk-5250, gnome-5250, the
python version, the windows version, etc, as well as just lp5250d... it's
just sheer dumb luck that it hasn't cropped up before)

Please grab a fresh copy from CVS and try again.   One caution however.
don't specify "trace=tracefile" because lp5250d is a daemon process. When
it goes into the background and becomes a daemon, it changes it's current
directory to /

So, instead, do something like lp5250d trace=/home/james/tracefile

I could not get outputcommand to fail... I tried it like this:

lp5250d env.DEVNAME=PRTTOUNIX "outputcommand=scs2ascii>/tmp/testme.txt" as400

If a fresh checkout from CVS doesn't solve your problem, please send me
the exact outputcommand that you're using, so I can try that.

Oh, BTW, scs2pdf doesn't work, and isn't finished.  Use scs2ps instead,
and pipe that to ps2pdf or similar...


On Fri, 1 Mar 2002, James Rich wrote:
>
> Not much here.  I set most things up on the command line since I'm still
> testing.  So I did this:
>
> lp5250d env.DEVNAME=PRTTOUNIX trace=tracefile myas400.fqdn~com
>
> Using the above lp5250d exits immediately without writing a tracefile.
> Interestingly the following works fine:
>
> lp5250d env.DEVNAME=PRTTOUNIX myas400.fqdn~com
>