bv@wjv.comREMOVE (Bill Vermillion) wrote in message
news:<Hrn94F.rAr@wjv.com>...
> In article <6c2fdba7.0401170806.70722bb8@posting.google.com >,
> Greg Ennis <PoMec@PoMec.Net> wrote:
> >Scott McMillan <smcm@usa.net> wrote in message
news:<m3sd00l5qv931n23f98il0ccf2i9avih6a@4ax.com>. ..
> >> (Follow-up posted to comp.unix.sco.misc as well)
> >>
> >> On 15 Jan 2004 10:27:25 -0800, PoMec@PoMec.Net (Greg Ennis) wrote:
> >>
> >> >Everyone,
> >> >
> >> >I have a SCO OpenServer(TM) Release 3.2v5.0.5 machine that keeps
> >> >giving me errors related to the printing process. I have included
> >> >some of them below
> >> >---------------------------------------------------
> >> >Your request lpt2-509301 destined for lpt2
> >> >encountered an error while printing on printer lpt2.
> >> >
> >> >Reason for failure:
> >> >
> >> >/usr/spool/lp/admins/lp/interfaces/lpt2: 4614 Memory fault - core
> >> >dumped
> >> >---------------------------------------------------
> >> >Other messages include the following:
> >> >
> >> >/usr/spool/lp/admins/lp/interfaces/lpt2: 13665 Memory fault - core
> >> >dumped
> >> >/usr/spool/lp/admins/lp/interfaces/lpt2: 12988 Memory fault - core
> >> >dumped
> >> >
> >> >The output ``port'', a FIFO, was closed before all output was written.
> >> >/usr/spool/lp/admins/lp/interfaces/lpt5: 12820 Memory fault - core
> >> >dumped
> >> >/usr/spool/lp/admins/lp/interfaces/lpt5: 5347 Memory fault - core
> >> >dumped
> >> >
> >> >Can any of you give me a start on this problem.
> >> >
> >> >Thank you,
> >> >
> >> >Greg Ennis
> >>
> >> You have a problem in your interfaces files (lpt2, lpt5 from above) or
> >> they've become corrupted. Those files are simple shell scripts
> >> (usually), so looking through them should give you some idea.
> >>
> >> There are SCO-specific NGs where this question may solicit more
> >> responses, comp.unix.sco.misc being one.
> >>
> >>
> >> Scott McMillan
> >
> >Scott,
> >
> >Thanks for the suggestion of a different newsgroup, and thanks again
> >for moving my inquiry to the new group.
> >
> >Here is a copy of the lpt2 script that is causing the problem. the
> >lpt5 script is a copy of lpt2.
> >
> >If anyone can give me a starting point I would appreciate it.
>
> [standard script deleted].
>
> Are you calling the prints jobs with lp and no flags other than
> -d printername.
>
> If so you might try -c to make a copy of the file first.
>
> See Tony's site http://www.aplawrence.com and search for
> the articles on printing.
>
> Didn't I mention this in comp.unix.admin?
>
> Bill

------------------------------------------------------------

Bill,

Thanks for your response. The command line syntax that the system is
using is:

lpr -oraw -d $PTR

Where $PTR is the name of the printer i.e. lpt2 or lpt5 etc

Most of the time the scripts work perfectly and there is no problem.
In fact the users have not ever reported any lost print jobs. I am
only getting e-mail notices of the problem, and it only seems to
occurr when the system is busy.

Also, I have not stipulated before that these printers are network
printers that are used by Windows Desktops as well as 2 Linux boxes.
The other systems have not been reporting any errros.

I'll modify the above command to lpr -c -oraw -d $PTR to see if the
problem resolves.

Thanks again,

Greg Ennis
------------------------------------------------------------------

Bill,

Putting the '-c' switch in place resolved the core dump with my printers.
Thanks very much. I still have a problem. I thought that the problem below
was related to the core dump errors, but obviously not. The core dump erros
are gone, but this one remains.

Do you have any suggestions?

Thanks again,

Greg


Your request lpt3-510730 destined for lpt3
encountered an error while printing on printer lpt3.

Reason for failure:

The output ``port'', a FIFO, was closed before all output was written.
The output ``port'', a FIFO, was closed before all output was written.
The output ``port'', a FIFO, was closed before all output was written.
The output ``port'', a FIFO, was closed before all output was written.

In article <PCEGIMGBDCOHKDDEMDNFEEKMCFAA.PoMec@PoMec.Net>,
Greg Ennis <PoMec@PoMec.Net> wrote:
>bv@wjv.comREMOVE (Bill Vermillion) wrote in message
>news:<Hrn94F.rAr@wjv.com>...
>> In article <6c2fdba7.0401170806.70722bb8@posting.google.com >,
>> Greg Ennis <PoMec@PoMec.Net> wrote:
>> >Scott McMillan <smcm@usa.net> wrote in message
>news:<m3sd00l5qv931n23f98il0ccf2i9avih6a@4ax.com> ...
>> >> (Follow-up posted to comp.unix.sco.misc as well)
>> >>
>> >> On 15 Jan 2004 10:27:25 -0800, PoMec@PoMec.Net (Greg Ennis) wrote:

[lots deleted - wjv]

>> >> >I have a SCO OpenServer(TM) Release 3.2v5.0.5 machine that keeps
>> >> >giving me errors related to the printing process. I have included
>> >> >some of them below
>> >> >---------------------------------------------------
>> >> >Your request lpt2-509301 destined for lpt2
>> >> >encountered an error while printing on printer lpt2.

>> >> >Reason for failure:
>> >> >
>> >> >/usr/spool/lp/admins/lp/interfaces/lpt2: 4614 Memory fault - core
>> >> >dumped
>> >> >---------------------------------------------------
>> >> >Other messages include the following:

.....

>> >> >The output ``port'', a FIFO, was closed before all output was written.
>> >> >/usr/spool/lp/admins/lp/interfaces/lpt5: 12820 Memory fault - core
>> >> >dumped

.....

[I had said this]

>> Are you calling the prints jobs with lp and no flags other than
>> -d printername.

>> If so you might try -c to make a copy of the file first.

>> See Tony's site http://www.aplawrence.com and search for
>> the articles on printing.

.....

>Putting the '-c' switch in place resolved the core dump with my
>printers. Thanks very much. I still have a problem. I thought
>that the problem below was related to the core dump errors,
>but obviously not. The core dump erros are gone, but this one
>remains.

Well at least one problem has been fixed - but not the main one.

>Your request lpt3-510730 destined for lpt3
>encountered an error while printing on printer lpt3.

>Reason for failure:

>The output ``port'', a FIFO, was closed before all output was written.
>The output ``port'', a FIFO, was closed before all output was written.
>The output ``port'', a FIFO, was closed before all output was written.
>The output ``port'', a FIFO, was closed before all output was written.

Well I've never seen that error myself. Looking on Google I see
this question has come up before, and one person solved it by
making a change to the HP interface script. Search google using
that output error.

However I have a dwindling SCO customer base - but am using netcat
for everthing - and all my problems disappeared with that - except
for the time Netgear changed their firmware and broke things.

It can hurt to dl the binary for that [Jeff has it on his site and
so does Tony] - follow the directions - and give it a try.

I wound up putting netcat in place of some broken print server
drives at a former site I maintained and wound up with 72 printers
all running with netcat flawlessly.

Lots of luck.

Bill

--
Bill Vermillion - bv @ wjv . com