-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pete Carah schreef:
| It would be very nice to those of us that install setiathome on remote
| servers to be able to build it without needing all of X and GL.
I know ;-)
| I'm not the only one since there *is* an option in configure
|
(Note: an HTML version of this report is available at
http://www.freebsd.org/cgi/query-pr-summary.cgi?category=ports .)
The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I'm running lighttpd 1.4.22 and PHP 5.2.9 on FreeBSD 7.2-RELEASE. When
uploading files 1 MB in size or so via PHP, the box then hard locks.
SSH and HTTP become unavailable, and apparently console logins don't
work; however, the box can still
We had issues when running lighttpd which indicated an issue with kqueue.
Disabling lightttpd's use of kqueue using the following prevented this.
server.event-handler = poll
In the logger term we have moved to nginx.
Regards
Steve
- Original Message -
From: Jacob Myers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steven Hartland wrote:
We had issues when running lighttpd which indicated an issue with kqueue.
After doing some experimentation of my own in VirtualBox, I've traced
the issue to sendfile(2). I changed server.network-backend to write
and writev and
Dmitry Marakasov píše v po 01. 06. 2009 v 20:02 +0400:
Thought we've switched to modular xorg more than a year ago, some
ports still define USE_XLIB and thus depend on all X libraries (even
when it's not really required). Which is even worse, USE_XLIB is
implicitely defined for ports that
As I wrote two weeks ago, the aqbanking-2.3.3 to 3.8.1 update took away
the command line banking client I use. Thus, I am eager to get 4.0.0,
which includes a new one.
I made a patch: http://www.freebsd.org/cgi/query-pr.cgi?pr=135161
I need someone using gnucash with aqbanking to check the
I hadn't heard anything back on this error yet. I've changed my
LOCALBASE back defaults, which as expected, made no different here.
Adding 'CONFIGURE_ARGS= --disable-warns-as-err', doesn't seem to have
an affect, or post-patch re-inplace command doesn't seem to be nuking
all the
