Re: Errors building mysql55-client
On 06/27/13 03:13, C. L. Martinez wrote: On Thu, Jun 27, 2013 at 9:21 AM, Trond Endrestøl trond.endres...@fagskolen.gjovik.no wrote: On Thu, 27 Jun 2013 07:55-, C. L. Martinez wrote: Either the file named distinfo is messed up, or the maintainer has access to a different file than the rest of us. Maybe you should wait until the MySQL mirrors catches up. I'm going to confirm that this was a recent patch to the ports tree: http://svnweb.freebsd.org/ports/head/databases/mysql55-server/distinfo?r1=320671r2=321789 It's pretty clear the versions the port is trying to download -used- to match the distinfo file, but they no longer do. This cryptic comment: Distfile rerolled to make it clearer the license of this community edition (GPLv2). seems to be the source of these errors which are biting me too. It would be nice for some clearer documentation on why distinfo was changed, what the real issue is, and what we can do to build this correctly. Naively speaking, the version available for download off the mysql site matches the old distinfo SHA checksum so I'm not sure why this was changed at all. I've CC'd the ports list and the responsible committer on this. I'll file a PR too if I get no response to this message. :) -- Dave Hayes - Consultant - Altadena CA, USA - d...@jetcafe.org *The opinions expressed above are entirely my own* Genius may have its limitations, but stupidity is not thus handicapped. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: SIGPIPE and threaded servers
Dan Nelson [EMAIL PROTECTED] writes: In the last episode (Mar 23), Dave Hayes said: I have a relatively simple threaded TCP server that services high volumes of requests. Currently it appears to randomly crash receiving a SIGPIPE. Attempts to ignore SIGPIPE via the sigaction() semantic only prevent me from sending the signal with kill to test whether or not SIGPIPE is actually ignored. =/ Then it's being ignored and your job is done :) Heh, I have to remember to be excrutiatingly explicit when I ask these questions. =) What is going on here? From the signal manpage: NameDefault Action Description -- --- SIGPIPE terminate process write on a pipe with no reader It's doing just what it is supposed to. But it's not doing what I want it to do. I don't want my process with all it's threads to terminate if I write on a pipe with no reader. I want the write() to return EPIPE so I can handle it there. It's not doing that currently. Installing a signal handler doesn't work to get it to do that. Ignoring the signal doesn't work. I've used both signal() and sigaction() semantics to no avail. What do I have to do so that SIGPIPE does not terminate my process? -- Dave Hayes - Consultant - Altadena CA, USA - [EMAIL PROTECTED] The opinions expressed above are entirely my own If you want to shoot for the moon, aim for the sun To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
SIGPIPE and threaded servers
I have a relatively simple threaded TCP server that services high volumes of requests. Currently it appears to randomly crash receiving a SIGPIPE. Attempts to ignore SIGPIPE via the sigaction() semantic only prevent me from sending the signal with kill to test whether or not SIGPIPE is actually ignored. =/ What is going on here? -- Dave Hayes - Altadena CA, USA - [EMAIL PROTECTED] Opinions expressed above are entirely my own They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -Benjamin Franklin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
