Hi,

In the newsgroup history I see that this issue has already been talked
about, but I don't really get it.

When I send big print jobs to one of our network printers, it doesn't print
and I get this message in the universe spooler and the logs :
Error: usd child received SIGPIPE signal. - No child processes 12/27/2006
08:42:15

I'm running a Universe Version 9.4.1.3B on Sco openserver.
Do you know where does it come from and how can I resolve it so it doesn't
lock every time ?

Thanks !!

David

As I understand it, usd spawns child processes to perform functions or
when the printer device is unreachable for other processes. If one of
those processes is terminated because of a bad connection, the child
receives a SIGPIPE signal. So.. I would try sending a big print job
to one of these network printers, without going through Universe or
usd. See if the error still occurs. If not then it seems like normal
handshaking is somehow being interpreted by usd as a SIGPIPE signal (I
have no doubt it's getting that signal, the question is whether that's
really a signal coming from the connection to the network printer or
some other process in the middle.)

I'm not a Universe guy so I'm really on shaky ground here, but if
you're using a statement like:
usd | lp ...
then any error in the spooler could "break the pipe" and maybe that
could return the SIGPIPE error. Yes, I understand SIGPIPE doesn't
refer to the pipe symbol, but SIGPIPE is the signal that's received
when a remote connection is closed, and I'm guessing that's on stdout
as well as any other I/O channel.

The other side of the coin is that you're on SCO, probably OS5, I
really hope it's not 3.x. As I'm sure you're aware, that system is
seriously out of date, and if the problem exists in SCO then you
probably don't have a solution outside of migration to a different OS
(probably Linux) and relicensing of the DBMS (probably from IBM).

If you're facing migration and related costs, I recommend you look at
some of the DBMS alternatives to see if they fit your budget. I also
recommend you get full confirmation that the problem has actually been
resolved in the latest version of Universe, otherwise you're going to
take a big leap to solve a problem and you may find the ground is just
as shaky on the other side of the chasm.

That's all I know about this issue, sorry. HTH

Tony Gravagno
Nebula Research and Development
TG@ alwaysremovethispartNebula-RnD.com

"David Gernez" wrote:

Just to add to Tony's comments, the best solution is to upgrade to
Linux
and the problem will go away.

Without going into to much detail:

If you check the print spooler log files for SCO, you will find
references
to SIGSEGV errors, which in turn will cause the SIGPIPE errors in
UniVerse.

If you have to stick with SCO, check that all updates and patches are
installed, but really you are flogging a very dead horse.

Cheers, Barry

Tony Gravagno wrote:

David Gernez wrote:
David,

Hi. I ran into a similar problem years ago running D3 over OpenServer.
OpenServer has a default maximum print file size of 1 megabyte. You
can increase this max using the mx setting in /etc/printcap. Take a
look at this page (
http://aplawrence.com/SCOFAQ/FAQ_scotec7mxsetting.html ) on Tony
Lawrence's site. I don't know if the 1-meg max is causing the symptom
you describe or if adding mx#0 to your printcap file will cure your
problem but it's worth trying.

Hope this helps.

Steve Lancour