Skip to Content.
Sympa Menu

freetds - RE: [freetds] Further complications in compiling latest snapshot

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Lowden, James K" <LowdenJK AT bernstein.com>
  • To: "FreeTDS Development Group" <freetds AT lists.ibiblio.org>
  • Subject: RE: [freetds] Further complications in compiling latest snapshot
  • Date: Wed, 15 Dec 2004 14:07:22 -0500

> From: Brian Bruns
> Sent: Wednesday, December 15, 2004 9:34 AM
>
> Anybody know the portable way to do this? I was getting SIGPIPE on
> dead sockets and using signal(SIGPIPE, SIG_IGN) to ignore it wasn't
> working on my Linux box.
>
> I suppose we could use autoconf to detect it and fall back to the old
> (broken) method.

http://www.opengroup.org/onlinepubs/009695399/functions/xsh_chap02_04.ht
ml
http://www.opengroup.org/onlinepubs/009695399/functions/signal.html
http://www.opengroup.org/onlinepubs/007908799/xns/send.html

What's broken, exactly? I don't see what's "old" or "broken" about
signal(3). How is it being superseded?

The standard says send() signals SIGPIPE on EPIPE, and (implicitly) that
signal() may be used to ignore SIGPIPE. AIUI, that's expected to work
in all implementations. Is it known not to work in Linux?

I see the preprocessor conditionals in net.c, but it's not clear to me
what published behavior it's aimed at.

--jkl


-----------------------------------------
The information contained in this transmission may contain privileged and
confidential information and is intended only for the use of the person(s)
named above. If you are not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, any
review, dissemination, distribution or duplication of this communication is
strictly prohibited. If you are not the intended recipient, please contact
the sender immediately by reply e-mail and destroy all copies of the original
message. Please note that we do not accept account orders and/or instructions
by e-mail, and therefore will not be responsible for carrying out such orders
and/or instructions.
If you, as the intended recipient of this message, the purpose of which is to
inform and update our clients, prospects and consultants of developments
relating to our services and products, would not like to receive further
e-mail correspondence from the sender, please "reply" to the sender
indicating your wishes. In the U.S.: 1345 Avenue of the Americas, New York,
NY 10105.






Archive powered by MHonArc 2.6.24.

Top of Page