Re: PHP segmentation faults
Try using xdebug (another php module) it will produce a stack trace when it segfaults. On 09/29/2011 10:29 AM, Moggie wrote: Hi, Unfortunately, for some time now, PHP scripts have been producing segmentation faults when executed on one of our systems :( Various posts found via google suggested reinstalling all the PHP ports and/or using a script to re-order the PHP extension modules, but all so far without success. The output of php -m is as follows: [PHP Modules] apc bz2 Core ctype date dom ereg filter gd hash iconv json libxml mbstring mcrypt mhash mysql mysqli mysqlnd openssl pcre PDO pdo_mysql pdo_sqlite posix Reflection session SimpleXML snmp sockets SPL sqlite3 standard tokenizer xml zip zlib I'm using this simple test to reproduce the problem: /tmp/test.php ?php Print Hello, World!; ? /usr/local/bin/php /tmp/test.php Hello, World!Segmentation fault (core dumped) All this makes me sad, especially since my Cacti graphs aren't being updated any more :( Any help or advise on how I might go about resolving this please would be very much appreciated. Thank you in advance for your time and consideration. Kind regards, moggie ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org -- Mark D. Foster m...@foster.cc http://mark.foster.cc/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD Port: subversion-1.6.15
In the case of this port, it explains to send the report directly to the maintainer. (I did that about 4 days ago and haven't heard any reply). I guess the answer is, when in doubt open a pr. Still, it's annoying to be misled in another direction. configure: error: no suitable apr found === Script configure failed unexpectedly. Please report the problem to l...@freebsd.org [maintainer] and attach the /usr/ports/devel/subversion/work/subversion-1.6.15/config.log including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. an `ls /var/db/pkg`). *** Error code 1 -- Mark D. Foster m...@foster.cc http://mark.foster.cc/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: sysutils/puppet: disabling freebsd ports package provider
On 04/06/2010 01:40 PM, Russell Jackson wrote: Is there any objection to the ports provider being disabled on FreeBSD systems since it mostly just causes puppet to hang anyway? I've had no luck in fixing it. The problem is that portupgrade and script don't interact well when running non-interactively. I've been running it this way in a local port, and I'm thinking of disabling it in the official port as well. I'd post a patch for upstream as well. If there are no objections, I'll submit a PR for the change by the end of the week. Thanks, Has this broken behavior been confirmed by anyone else? I'd like to see the ports provider fixed, if possible. Is portmaster a more suitable back-end? -- I hate racists. Mark D. Fosterm...@foster.cc http://mark.foster.cc/ | http://www.freegeekseattle.org/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: new port dns/dns-audit review
Sevan / Venture37 wrote: Hiya I've created a basic port to install the dns-audit perl script posted on the Sun Bigadmin site: http://www.sun.com/bigadmin/scripts/submittedScripts/dns-audit.pl.txt I'd appreciate some feedback about if you think it's worth submitting for inclusion to ports or not. Not to dissuade you but this is what the dns/scavenge port does (perhaps better?). You might want to check it out. http://conshell.net/wiki/index.php/Scavenge -- I hate racists. Mark D. Foster m...@foster.cc http://mark.foster.cc/ | http://www.freegeekseattle.org/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [RFC] New category proposal, i18n
Thomas Abthorpe wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On June 25, 2009 08:51:43 pm Carlos A. M. dos Santos wrote: Guys, you have been discussing the category *name* for eight days now without reaching a consensus. This is becoming somewhat boring. Please do not reinvent the wheel. Whether you like it or not, i18n is a well established and widely accepted acronym. Here endeth the debate http://www.freebsd.org/cgi/query-pr.cgi?pr=136072 - From here it is yay or nay. Most of the respondents like i18n best. There were 25 votes, 16 of them for i18n. http://www.micropoll.com/akira/mpresult/615850-178803 -- I hate racists. Mark D. Foster m...@foster.cc http://mark.foster.cc/ | http://conshell.net/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [RFC] New category proposal, i18n
per...@pluto.rain.com wrote: If i18n is too cryptic or too alphanumeric, and internationalization is too long, why not go with nls? I personally think that nls is equally as cryptic as i18n or l10n. Anyone care for intlzn? It's short, should still tab-complete from in, and it may be a bit less cryptic than nls, i18n, or l10n. If I may be so bold as to present a democratic outcome. To help settle the matter please vote on this issue within 48 hours. http://www.micropoll.com/akira/mpview/615850-178803 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: ports/132800: vuxml submission for net-im/ejabberd
I'm following up regarding this apparent maintainer timeout. It's not my intention to place blame, but to me it is unacceptable that important security (vuxml) updates are sometimes blocked by unresponsive maintainers. It is not in the best interest of the users or FreeBSD to let these things slip. The vuxml updates should be reviewed committed without waiting on the maintainer of the port. Perhaps a simple non-blocking heads-up (Cc:) to the maintainer is more appropriate. Once publicized, the security notifications (via portaudit) become known to a wider, targetted audience. This establishes an important feedback loop as opposed to keeping the problem a secret, since the users are more likely to either nudge the maintainer for an update to the port or submit one (via send-pr) themselves. -- I hate rascists. Mark D. Foster m...@foster.cc http://mark.foster.cc/ | http://conshell.net/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
ffmpeg vulnerability
(Resending, I did not see it posted earlier) ffmpeg has 3 announced vulnerabilities in this past month. Here is the latest... 09.6.23 CVE: Not Available Platform: Cross Platform Title: FFmpeg libavformat/4xm.c Remote Code Execution Description: FFmpeg is an application used to record, convert, and stream audio and video. The application is exposed to a remote code execution issue because it fails to adequately validate user-supplied input. This issue occurs in the libavformat/4xm.c source file, and occurs because of a NULL pointer dereference error. FFmpeg trunk revision versions prior to 16846 are vulnerable. Ref: http://www.trapkit.de/advisories/TKADV2009-004.txt http://www.trapkit.de/advisories/TKADV2009-004.txt Normally I would submit a vuxml entry, but not sure how to indicate the proper fixed versiona since the port uses 2008.07.07_7 while the fixed version is revision 16846. -- Realization #2031: That the meaning of life is now just another Google search. Mark D. Foster m...@foster.cc http://mark.foster.cc/ | http://conshell.net/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: exim 4.69 won't build
Alex Kozlov wrote:
Remove NO_NIS/WITHOUT_NIS from make.conf/src.conf
I do have WITHOUT_NIS in /etc/make.conf
or add this to make.conf:
.if ${.CURDIR:N*/ports/mail/exim} ==
WITHOUT_PERL=yes
WITHOUT_NIS=yes
.endif
This one fixed it, thanks a lot!
--
The more stuff you have, the less it all means.
Mark D. Foster [EMAIL PROTECTED]
http://mark.foster.cc/ | http://conshell.net/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
exim 4.69 won't build
I'm getting this error when trying to compile (via make) the mail/exim port (v4.69). ... cc -o exim lookups/lookups.a(nis.o)(.text+0x33): In function `nis0_find': : undefined reference to `yp_match' lookups/lookups.a(nis.o)(.text+0xa0): In function `nis_find': : undefined reference to `yp_match' lookups/lookups.a(nis.o)(.text+0xed): In function `nis_open': : undefined reference to `yp_get_default_domain' *** Error code 1 I'd use send-pr to report this, but exim is broken, so a catch-22. -- The more stuff you have, the less it all means. Mark D. Foster [EMAIL PROTECTED] http://mark.foster.cc/ | http://conshell.net/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
6.2-RELEASE packages are where?
In limbo-land it seems. Not here: ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/old-releases/i386/6.2-RELEASE/packages/ Or here: ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/6.2-RELEASE/packages/ Thanks. -- Some days it's just not worth chewing through the restraints... Mark D. Foster, CISSP [EMAIL PROTECTED] http://mark.foster.cc/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports Request: OpenNMS
Paul Schmehl wrote: If you're really serious that you want OpenNMS ported, then it's time to make your contribution to FreeBSD. :-) Solicit help from other FreeBSD users who use/want OpenNMS, and work together to distribute the load and get the job done. There's plenty of people on this list who can help you when you run into problems. I couldn't agree more! But for the last statement. I have to say I've been underwhelmed with the amount of maintainership support I have received from this ([EMAIL PROTECTED]) list. Perhaps it's just me, I know the ports-mgr are also very busy. Or in other cases the answer is just unknown. So, as a maintainer I tend to ask google before bugging the list. Is a dedicated maintainer-support list something discussed before? -- Some days it's just not worth chewing through the restraints... Mark D. Foster, CISSP [EMAIL PROTECTED] http://mark.foster.cc/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How do you require Xorg?
Paul Schmehl wrote: I'm working on porting the open-vm-tools, and the software builds, makes and installs fine, but it obviously won't work without Xorg being installed. The Xorg components should, if possible, be optional, IMO. Anyway, thanks for working on this. Have you looked at the NetBSD implementation as reference? http://pkgsrc.se/sysutils/open-vm-tools -- Some days it's just not worth chewing through the restraints... Mark D. Foster, CISSP [EMAIL PROTECTED] http://mark.foster.cc/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
field notes - dansguardian and tinyproxy
Just completed a setup of dansguardian w/ tinyproxy on 5.5-RELEASE-p11 and it works pretty well. Performance is a bit lackluster, but acceptable. I noticed that dansguardian requires squid via RUN_DEPENDS but that is a bit inflexible isn't it. I just commented out that line in the Makefile before make install. Dunno if that's the right way but it would be nice to have the option of toggling in tinyproxy (or whatever) instead of squid. Also, tinyproxy wasn't working for me on sparc64, it built/installed fine but using a mostly default config seemed to munge the IP address of the client, making the Allow ACLs in tinyproxy.conf useless. Is than an big vs. little-endian issue? e.g. 192.168.1.9 was being seen as 48.55.32.49 -- Said one park ranger, 'There is considerable overlap between the intelligence of the smartest bears and the dumbest tourists.' Mark D. Foster, CISSP [EMAIL PROTECTED] http://mark.foster.cc/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: can we use disk device for iscsi-target port?
Patrick Dung wrote: It would be great if disk device can be used directly. BTW, I have not yet test netbsd with raw disk. seems someone test on openbsd and it seems working: http://www.freebsdforums.org/forums/showthread.php?t=43960 Whole disk or slice? I don't think either works at this point but can't say I've tried. Can you please test an individual slice and report your findings? -- Said one park ranger, 'There is considerable overlap between the intelligence of the smartest bears and the dumbest tourists.' Mark D. Foster, CISSP [EMAIL PROTECTED] http://mark.foster.cc/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
gmake compile error
Is this a problem with the gmake port (a dependency of qt4) or should I
go ahead and submit the bug report to GNU gcc?
...
cd doc ; make install
./../etc/mkinstalldirs /usr/local/man/man1 /usr/local/info
install -o root -g wheel -m 444 ./screen.1 /usr/local/man/man1/screen.1
make screen.info
makeinfo --no-split ./screen.texinfo -o screen.info
./screen.texinfo:2891: warning: Accent command `@'' must not be followed
by whitespace.
if test -f screen.info; then d=.; else d=.; fi; if test -f
$d/screen.info; then for f in $d/screen.info*; do install -o root -g
wheel -m 444 $f /usr/local/info;done; if /bin/sh -c 'install-info
--version' /dev/null 21; then install-info --info- -DQT_NO_THREAD
-DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQMAKE_OPENSOURCE_EDITION -c
/usr/ports/devel/qmake4/work/qt-x11-opensource-src-4.2.3/qmake/generators/mac/pbuilder_pbx.cpp
c++: Internal error: Killed: 9 (program cc1plus)
Please submit a full bug report.
See URL:http://gcc.gnu.org/bugs.html for instructions.
*** Error code 1
Stop in /usr/ports/devel/qmake4/work/qt-x11-opensource-src-4.2.3/qmake.
*** Error code 1
Stop in /usr/ports/devel/qmake4.
{standard input}: Assembler messages:
{standard input}:26701: Warning: end of file not at end of a line;
newline inserted
{standard input}:27666: Error: unknown pseudo-op: `.l1'
*** Error code 1
FreeBSD zeus.foster.dmz 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Jan 12
10:40:27 UTC 2007
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386
--
Said one park ranger, 'There is considerable overlap between the
intelligence of the smartest bears and the dumbest tourists.'
Mark D. Foster, CISSP [EMAIL PROTECTED] http://mark.foster.cc/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: qmake compile error
Lowell Gilbert wrote:
qmake, not gmake; I corrected the subject line
Er, ah, yes thanks.
...
cd doc ; make install
./../etc/mkinstalldirs /usr/local/man/man1 /usr/local/info
install -o root -g wheel -m 444 ./screen.1 /usr/local/man/man1/screen.1
make screen.info
makeinfo --no-split ./screen.texinfo -o screen.info
./screen.texinfo:2891: warning: Accent command `@'' must not be followed
by whitespace.
if test -f screen.info; then d=.; else d=.; fi; if test -f
$d/screen.info; then for f in $d/screen.info*; do install -o root -g
wheel -m 444 $f /usr/local/info;done; if /bin/sh -c 'install-info
--version' /dev/null 21; then install-info --info- -DQT_NO_THREAD
-DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQMAKE_OPENSOURCE_EDITION -c
/usr/ports/devel/qmake4/work/qt-x11-opensource-src-4.2.3/qmake/generators/mac/pbuilder_pbx.cpp
c++: Internal error: Killed: 9 (program cc1plus)
Please submit a full bug report.
See URL:http://gcc.gnu.org/bugs.html for instructions.
*** Error code 1
Stop in /usr/ports/devel/qmake4/work/qt-x11-opensource-src-4.2.3/qmake.
*** Error code 1
Stop in /usr/ports/devel/qmake4.
{standard input}: Assembler messages:
{standard input}:26701: Warning: end of file not at end of a line;
newline inserted
{standard input}:27666: Error: unknown pseudo-op: `.l1'
*** Error code 1
This trace doesn't make sense to me. Are you using parallel building
of some sort? If so, turn it off; even though it's probably not
causing the problem, it's obscuring debug information.
Not that I'm aware of. The only anomaly I can think of on this host is
that it's running as a guest under vmware-server.
FreeBSD zeus.foster.dmz 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Jan 12
10:40:27 UTC 2007
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386
Are your ports the same age?
Yes, I just recently did a cvsup.
What else can I try? pkg_add -r qmake4 would only sidestep the problem.
--
Said one park ranger, 'There is considerable overlap between the
intelligence of the smartest bears and the dumbest tourists.'
Mark D. Foster, CISSP [EMAIL PROTECTED] http://mark.foster.cc/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
python 2.4
So is python-2.4.3_2 (just committed) STILL vulnerable? It won't let me upgrade from python-2.4.3 # make === python-2.4.3 has known vulnerabilities: = python -- buffer overrun in repr() for unicode strings. Reference: http://www.FreeBSD.org/ports/portaudit/fe83eb5b-55e1-11db-a5ae-00508d6a62df.html = Please update your ports tree and try again. *** Error code 1 Stop in /usr/ports/lang/python. -- Said one park ranger, 'There is considerable overlap between the intelligence of the smartest bears and the dumbest tourists.' Mark D. Foster, CISSP [EMAIL PROTECTED] http://mark.foster.cc/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: python 2.4
Jose Alonso Cardenas Marquez wrote: The lang/python port was updated, please update your port tree and try again. you don't forget to read of ports/UPDATING note. Regarding the recent python changes... UPDATING states: After upgrading of lang/python, you must rebuild all its consumer ports to make them get ready to Python 2.5. To do this, you will need to: pkgdb -uf cd /usr/ports/lang/python make upgrade-site-packages Please correct me if I'm wrong, but don't these instructions rely on pkgdb which is a component of portupgrade which I do not use. # pkgdb -uf cd /usr/ports/lang/python make upgrade-site-packages pkgdb: Command not found. So must I install portupgrade? Or should I just ignore the error run make upgrade-site-packages ? -- Said one park ranger, 'There is considerable overlap between the intelligence of the smartest bears and the dumbest tourists.' Mark D. Foster, CISSP [EMAIL PROTECTED] http://mark.foster.cc/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
