Did you open PRs for the ports that don’t compile for you?
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
On 04/07/15 16:37, Cristiano Deana wrote:
> Hi,
>
> please help me understand.
>
> In /usr/ports/UPDATING we have:
>
> ---
> # grep -A11 ^20150220 /usr/ports/UPDATING | more
> 20150220:
> AFFECTS: users of PHP
>
> The default PHP version has been updated from 5.4 to 5.6.
>
> If you use b
On 04/07/2015 9:37 am, Cristiano Deana wrote:
Hi,
please help me understand.
In /usr/ports/UPDATING we have:
---
# grep -A11 ^20150220 /usr/ports/UPDATING | more
20150220:
AFFECTS: users of PHP
The default PHP version has been updated from 5.4 to 5.6.
If you use binary packages you sho
On Tue, Nov 25, 2008 at 6:40 AM, Ken Chen <[EMAIL PROTECTED]> wrote:
> Change to configuration to solve this problem:
>
> #server.network-backend = "freebsd-sendfile"
> server.network-backend = "writev"
>
> http://redmine.lighttpd.net/boards/2/topics/show/141
Maybe this patch is related?
http://r
Ken Chen wrote:
> Change to configuration to solve this problem:
>
> #server.network-backend = "freebsd-sendfile"
> server.network-backend = "writev"
>
> http://redmine.lighttpd.net/boards/2/topics/show/141
Good to know.
Please consider posting a PR.
signature.asc
Description: OpenPGP digita
Change to configuration to solve this problem:
#server.network-backend = "freebsd-sendfile"
server.network-backend = "writev"
http://redmine.lighttpd.net/boards/2/topics/show/141
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailm
Thank Jeremy, I will try.
2008/11/12 Jeremy Chadwick <[EMAIL PROTECTED]>
> On Tue, Nov 11, 2008 at 10:09:38PM +0800, Ken Chen wrote:
> > I think the parent php-cgi are very health. I have tried:
> >
> > There are total 49 php-cgi processes are running or frozen, the '1 wait'
> is
> > parent .
> >
On Tue, Nov 11, 2008 at 10:09:38PM +0800, Ken Chen wrote:
> I think the parent php-cgi are very health. I have tried:
>
> There are total 49 php-cgi processes are running or frozen, the '1 wait' is
> parent .
>
> web4# ps alx | grep php-cgi | grep -v grep | awk '{print $9}' | sort | uniq
> -c | s
The report from lighttpd looks fine:
cache.cached-itmes: 98293
cache.hitrate(%): 96
cache.memory-inuse(KB): 6143
fastcgi.active-requests: 16
fastcgi.backend.0.0.connected: 419008
fastcgi.backend.0.0.died: 0
fastcgi.backend.0.0.disabled: 0
fastcgi.backend.0.0.load: 16
fastcgi.backend.0.0.overloaded
I think the parent php-cgi are very health. I have tried:
There are total 49 php-cgi processes are running or frozen, the '1 wait' is
parent .
web4# ps alx | grep php-cgi | grep -v grep | awk '{print $9}' | sort | uniq
-c | sort -n
1 biowr
1 wait
15 sbwait
32 accept
Kill one of frozen
Anton - Valqk wrote:
> You can try taking look to lighttpd status and fcgi processes status
> like this:
> server.modules += ( "mod_status" )
> status.status-url = "/server-status"
> status.statistics-url = "/sstatus1"
>
> status.statistics-url gives info for each fastcgi like this:
>
> fastcgi
You can try taking look to lighttpd status and fcgi processes status
like this:
server.modules += ( "mod_status" )
status.status-url = "/server-status"
status.statistics-url = "/sstatus1"
status.statistics-url gives info for each fastcgi like this:
fastcgi.active-requests: 0
fastcgi.backend.bac
Ken Chen wrote:
> I capture something.
>
> Please check the PID 57776. It's CPU time never change since my previous
> mail here.
>
> web4# ps alx | grep php-cgi | grep -v grep | grep sbwait
> 65534 57776 47240 0 4 0 182328 84984 sbwait I ??2:02.12
> /usr/local/bin/php-cgi
You're rig
I capture something.
Please check the PID 57776. It's CPU time never change since my previous
mail here.
web4# ps alx | grep php-cgi | grep -v grep | grep sbwait
65534 57776 47240 0 4 0 182328 84984 sbwait I ??2:02.12
/usr/local/bin/php-cgi
65534 57801 47240 0 4 0 182328 82408 s
Ken Chen wrote:
> Oh.. sorry, I forgot to provide the information of my environment.
>
> web4# php-cgi -v
> PHP 5.2.6 (cgi-fcgi) (built: Nov 2 2008 11:16:30)
> Copyright (c) 1997-2008 The PHP Group
> Zend Engine v2.2.0, Copyright (c) 1998-2008 Zend Technologies
> with XCache v1.2.2, Copyright
Hi Jeremy,
A health FastCGI process have a lifetime, so the PIDs of all php-cgi
processes should in a short range.
There are some 'php-cgi' fall in 'sbwait' state, and stay there forever. The
frozen 'php-cgi' can't accept new request, so never retire.
Please forgive my poor English.
2008/11/7 J
On Fri, Nov 07, 2008 at 07:29:37PM +0800, Ken Chen wrote:
> Hello,
>
> I have 4 web servers with lighttpd to serve one web site with DNS load
> sharing. On the 2 SMP-enable web servers, there will be many php-cgi frozen
> in 'sbwait' state every day. It means the php-cgi stay in 'sbwait' state,
>
Oh.. sorry, I forgot to provide the information of my environment.
web4# php-cgi -v
PHP 5.2.6 (cgi-fcgi) (built: Nov 2 2008 11:16:30)
Copyright (c) 1997-2008 The PHP Group
Zend Engine v2.2.0, Copyright (c) 1998-2008 Zend Technologies
with XCache v1.2.2, Copyright (c) 2005-2007, by mOo
web4# /
Ken Chen wrote:
> Hello,
>
> I have 4 web servers with lighttpd to serve one web site with DNS load
> sharing. On the 2 SMP-enable web servers, there will be many php-cgi frozen
> in 'sbwait' state every day. It means the php-cgi stay in 'sbwait' state,
> and never be back to 'accept' or other st
Try commenting out the line for 'doc_root' in your php.ini
Matthew Herzog wrote:
When I load a file named php4.info I can see all my php build information.
If I change that same file's name to phpinfo.php, I get a "premature
end of script headers"
error. The file contains this text only:
an
Matthew Herzog wrote:
When I load a file named php4.info I can see all my php build
information.
If I change that same file's name to phpinfo.php, I get a "premature
end of script headers"
error. The file contains this text only:
and is owned by apache.
This is purely a guess since I know
- Matthew Herzog <[EMAIL PROTECTED]> wrote:
> When I load a file named php4.info I can see all my php build
> information.
>
> If I change that same file's name to phpinfo.php, I get a "premature
> end of script headers"
> error. The file contains this text only:
>
> phpinfo();
> ?>
>
> a
On Thursday 23 November 2006 16:52, Ivan Voras wrote:
> Dominik Zalewski wrote:
> > Hi All,
> >
> > I'm using FreeBSD 6.1 release on i386. I have a problem with pear and
> > apache. Here is what I'm getting:
> >
> > [EMAIL PROTECTED] ~]# pear list
> > Installed packages, channel pear.php.net:
> > =
Dominik Zalewski wrote:
> Hi All,
>
> I'm using FreeBSD 6.1 release on i386. I have a problem with pear and apache.
> Here is what I'm getting:
>
> [EMAIL PROTECTED] ~]# pear list
> Installed packages, channel pear.php.net:
> =
> PackageVersion Sta
Dominik Zalewski wrote:
> I'm using FreeBSD 6.1 release on i386. I have a problem with pear and apache.
> Here is what I'm getting:
>
> [EMAIL PROTECTED] ~]# pear list
> Installed packages, channel pear.php.net:
> =
> PackageVersion State
> Archive_
You need to give the command 'bt' to gdb for some usefull output.
bt stands for backtrace.
Ronald.
On Wed, 01 Jun 2005 18:11:54 +0200, Steve Rieger
<[EMAIL PROTECTED]> wrote:
hi all am wondering is anybody else thats running fbsd 5.4 php4 apache1,
and about 10 php extensions, are noticing
Mark Andrews said:
>> Thanks a lot for your reply. If I understand things correctly, I need to
>> maintain two cvsup files - one that tracks security issues in the base
>> FreeBSD 5.3 system (tag=RELENG_5_3, src-all) and one for the ports
>> collection (tag=. , ports-all). Then every time I recei
On Wed, 22 Dec 2004 09:52:01 +0800,
Ladislav Bodnar <[EMAIL PROTECTED]> said:
> Thanks a lot for your reply. If I understand things correctly, I need to
> maintain two cvsup files - one that tracks security issues in the base
> FreeBSD 5.3 system (tag=RELENG_5_3, src-all) and one for the
> On Wednesday 22 December 2004 09:06, Mark Andrews wrote:
> > > Hello,
> > >
> > > Due to the recently discovered vulnerability in PHP versions older than
> > > 4.3.10 and 5.0.3, I decided to take a look at portupgrade to see if it
> > > is a good way to keep the ports collection up-to-date with
On Wednesday 22 December 2004 09:06, Mark Andrews wrote:
> > Hello,
> >
> > Due to the recently discovered vulnerability in PHP versions older than
> > 4.3.10 and 5.0.3, I decided to take a look at portupgrade to see if it
> > is a good way to keep the ports collection up-to-date with respect to
>
> Hello,
>
> Due to the recently discovered vulnerability in PHP versions older than
> 4.3.10 and 5.0.3, I decided to take a look at portupgrade to see if it is a
> good way to keep the ports collection up-to-date with respect to security
> issues. I ran cvsup on the security branch (tag=RELEN
On Track Technicial Support schrieb:
make config
thanks for that hint!
but what's the best way to upgrade (eg to 4.3.9)?
something like
pkg_info | grep ^php4- | awk '{ print $1}' | xargs portupgrade -b
???
Regards,
Thomas.
I do think that the whole new PHP ports system needs to be re-done. It seem
32 matches
Mail list logo
