ports/sysutils/aaccli
Hello, Why aaccli is marked only for arch i386 ? :) It's a binary package build for i386, but it work perfect on amd64. Is there any other reason for this? -- Best Wishes, Stefan Lambrev ICQ# 24134177 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
problem with mod_proxy_ajp
Sorry if this is posted to the wrong list - it is about a port that gives problems after updating from 6.2_beta2 to 6.2_rc1. Also posted this in -stable, -apache, and -questions but no replies yet. Yesterday I upgraded a test server from FreeBSD 6.2_beta2 amd64 to 6.2_rc1 amd64. I am using apache 2.2.3 with mod_proxy and mod_proxy_ajp to connect to Tomcat 5.5.20. The ajp proxy worked well on 6.2 beta2, but after the upgrade to 6.2 RC1, connections via the ajp proxy are extremely slow. It seems as if something is timing out, as it takes several minutes until apache returns data. After some time, this seems to improve a bit, but when connecting from another browser or machine it all starts over. Connecting directly to Tomcat Coyote ports works well. There is nothing in the httpd error logs or the tomcat logs, nor in the system message log indicating what is going wrong. When using mod_jk, all works fine. Below is an excerpt of my httpd.conf: LoadModule proxy_module libexec/apache22/mod_proxy.so LoadModule proxy_ajp_module libexec/apache22/mod_proxy_ajp.so IfModule proxy_module ProxyRequests Off Proxy * Order Deny,Allow Deny from all Allow from [my ip] /Proxy IfModule proxy_ajp_module Location /[mylocation]/ ProxyPass ajp://localhost:8009/ SSLrequireSSL /Location /IfModule /IfModule ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ftp/proftpd - Need some advice
Quoting Beech Rintoul [EMAIL PROTECTED]: On Wednesday 15 November 2006 10:38, Shaun Amott wrote: On Wed, Nov 15, 2006 at 10:12:49AM -0900, Beech Rintoul wrote: Yesterday, I approved a patch rolled by Alex Samorukov [EMAIL PROTECTED] which fixes a buffer overflow vulnerability (ports/105510). I tested the patch in 5.4, 6-STABLE and -CURRENT and didn't see any problems. This morning I had a couple of emails from people telling me that after upgrade they can't connect and the port is exiting with signal 11. How should I proceed with this? as I said I can't duplicate the problem. I got a number of messages too, since I committed the patch. I was able to determine the cause of the problem, so I went ahead and fixed it. I was seeing the same thing so when I saw this I upgraded ports and just rebuilt with: # $FreeBSD: ports/ftp/proftpd/Makefile,v 1.92 2006/11/15 19:22:23 shaun Exp $ I restarted proftpd and am still seeing the same problem. A few lines from my log file follow: Nov 15 17:07:33 conejoblanco.info proftpd[2108] 189.141.53.49: ProFTPD killed (signal 15) Nov 15 17:07:33 conejoblanco.info proftpd[2108] 189.141.53.49: ProFTPD 1.3.0 standalone mode SHUTDOWN Nov 15 17:07:37 conejoblanco.info proftpd[21839] 189.141.53.49: ProFTPD 1.3.0 (stable) (built Wed Nov 15 09:21:44 CST 2006) standalone mode STARTUP Nov 15 17:08:21 conejoblanco.info proftpd[21855] 189.141.53.49 (189.141.53.49[189.141.53.49]): FTP session opened. Nov 15 17:08:30 conejoblanco.info proftpd[21855] 189.141.53.49 (189.141.53.49[189.141.53.49]): ProFTPD terminating (signal 11) Nov 15 17:08:30 conejoblanco.info proftpd[21855] 189.141.53.49 (189.141.53.49[189.141.53.49]): FTP session closed. Hopefully this is still the old port but if not, is anyone else still seeing this? I'm using ldap for auth and running FreeBSD 6.2-PRERELEASE up to date and no old librariesI'm running or includes. Any suggestions appreciated, Thanks, ed ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
ports/courier Problem imapd.core and upgrade
Forwarded from courier users list. Quoting Edwin L. Culp W. [EMAIL PROTECTED]: Quoting Milan Obuch [EMAIL PROTECTED]: On Wednesday 15 November 2006 12:26, you wrote: Hi, I was not able to force that GAMIN called sendmsg which was defined in libc.so. Then, I modified COURIER-IMAP, instead of GAMIN. -- HIROSHI OOTA Great, I tested this and it works. I used it as basis for upgrade patch. If anybody would like to try 0.53.3 with this patch, look for ports/105573 in FreeBSD PR database. I would like to get as much feedback as possible. I downloaded the pr patch and applied it manually and it broke the complilation with fam but since I'm not sure if this should be fam based or gamin based with the change. I would also appreciate your attaching an empty mail/courier port with your changes, if you could, just to be sure that my manual application was ok although they were very simple but sometimes that is worse. On a side note, I would like to know which add-ons are people using with courier. I have good experience with clamcour (security/clamcour in FreeBSD ports) and a bit with pythonfilter (mail/courier-pythonfilter in ports). I am only using spamassassin and clamcour, that I agree works great. What else is being used? I'm also thinking that maybe this should probably be on the [EMAIL PROTECTED] rather than courier-users unless other os's have the gamin/fam conflicts. I was just looking at my different courier installations and I see that there isn't a gamin/fam standard. On some I'm still running /usr/local/bin/fam -T 0 and newer ones, I'm not and they all work although one is complaining about fam in the log file. I guess that what I'm suggesting is that a best or recommended method be added to the courier port. Life was easier before gamin but . . . Thanks to all, ed P.S. This may not show up in ports because I'm not suscribed with this email address but maybe ;) - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports/sysutils/aaccli
On Wed, Nov 22, 2006 at 11:45:47AM +0200, Stefan Lambrev wrote: Why aaccli is marked only for arch i386 ? :) It's a binary package build for i386, but it work perfect on amd64. Is there any other reason for this? I've updated the port, thanks. -- Shaun Amott // PGP: 0x6B387A9A A foolish consistency is the hobgoblin of little minds. - Ralph Waldo Emerson pgpOPYajnytBy.pgp Description: PGP signature
Re: FreeBSD 6.1-R-p10 and PHP 5.2.0
On Fri, Nov 17, 2006 at 05:32:07AM -0600, [EMAIL PROTECTED] wrote: I just tried sessions at the beginning and : pid 8311 (httpd), uid 0: exited on signal 11 (core dumped) darn it :( Out of desperation, I tried several combinations but no cigar :( If anyone else has a winning combination, I'd love to try it. Thanks, ed Can you find the corefile and run gdb on it and do bt? E.g. $ gdb /usr/local/bin/php /path/to/php.core ... (gdb) bt This might tell us which module is crashing php. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networkinghttp://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.1-R-p10 and PHP 5.2.0
Quoting Jeremy Chadwick [EMAIL PROTECTED]: On Fri, Nov 17, 2006 at 05:32:07AM -0600, [EMAIL PROTECTED] wrote: I just tried sessions at the beginning and : pid 8311 (httpd), uid 0: exited on signal 11 (core dumped) darn it :( Out of desperation, I tried several combinations but no cigar :( If anyone else has a winning combination, I'd love to try it. Thanks, ed Can you find the corefile and run gdb on it and do bt? E.g. $ gdb /usr/local/bin/php /path/to/php.core ... (gdb) bt This might tell us which module is crashing php. Jeremy, Thanks for the suggestion. First I apologize for the noise because I sent this on the 17th and it just got to the list. In the meantime I recompiled all with a portupgrade -rRf and that solved the problem and I erased all the core files. But the problem was probably one of my prior upgrades didn't compile something that was causing the problem. Again thanks, ed -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networkinghttp://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD ports that you maintain which are currently marked broken
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we are attempting to notify maintainers of ports that are marked as broken in their Makefiles. In many cases these ports are failing to compile on some subset of the FreeBSD build environments. The most common problem is that recent versions of -CURRENT include gcc3.4, which is much stricter about such things as function declarations, literal strings constants that continue over several physical lines, and forcing the deprecation of antique header files such as varargs.h (we should now be using stdargs.h). The next most common problem is that compiles succeed on the i386 architecture (e.g. the common Intel PC), but fail on one or more of the other architectures due to assumptions about things such as size of various types, byte-alignment issues, and so forth. In occasional cases we see that the same port may have different errors in different build environments. The script that runs on the build cluster uses heuristics to try to 'guess' the error type to help you isolate problems, but it is only a rough guide. If you need help in one or more build environments that you do not have access to, please ask for help on the freebsd-ports mailing list. One more note: on occasion, there are transient build errors seen on the build farm. Unfortunately, there is not yet any way for this algorithm to tell the difference (humans are much, much better at this kind of thing.) The errors are listed below. In the case where the same problem exists on more than one build environment, the URL points to the latest errorlog for that type. (By 'build environment' here we mean 'combination of 4.x/5.x/6.x with target architecture'.) (Note: the dates are included to help you to gauge whether or not the error still applies to the latest version. The program that generates this report is not yet able to determine this automatically.) portname: audio/mbrolavox broken because: Size mismatch build errors: http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.6.2006103118/mbrolavox-3.0.1.log.bz2 (Oct 15 15:27:05 UTC 2006) overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=mbrolavox portname: audio/spiralloops broken because: Does not compile (bad C++ code) build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.5.2006100420/spiralloops-2.0.0.log.bz2 (Sep 24 07:13:35 UTC 2006) overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=spiralloops portname: chinese/gbfs broken because: fails to patch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=gbfs portname: chinese/iiimf-le-chewing broken because: fails to install (dependency problem) build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=iiimf-le-chewing portname: chinese/xemacs broken because: Does not build even with fix for -lxpg4 build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.5.2006100420/zh-xemacs-20.4_2.log (Oct 9 00:49:31 UTC 2006) overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=xemacs portname: devel/cl-asdf-cmucl broken because: does not build build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.5.200606/cl-asdf-cmucl-2003.05.16.log.bz2 (Sep 26 05:10:12 UTC 2006) http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.4.2006110307/cl-asdf-cmucl-2003.05.16.log.bz2 (Jul 14 12:12:35 GMT 2006) overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=cl-asdf-cmucl portname: devel/clint broken because: Does not compile on FreeBSD = 5.x build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=clint portname: devel/gcvs broken because: Does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=gcvs portname: devel/ixlib broken because: Does not compile on !i386 or on FreeBSD = 5.x build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.4.2006110307/ixlib-0.96.2_3.log (Nov 5 20:59:01 GMT 2006) overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=ixlib portname: devel/pear-apd broken because: Does not compile build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.7.2006110700/pear-apd-1.0.1,1.log (Nov 12 01:03:15 UTC 2006) overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=pear-apd portname: devel/php-dbg broken because: Does not compile build errors:
FreeBSD ports which are currently scheduled for deletion
As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on the existing port. In some cases, ports are marked for removal because they fail to build and install correctly from their sources, or otherwise fail in operation. The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems, the ports will be deleted. The goal of this posting is to make this process much more visible to the wider FreeBSD community. portname: audio/alsaplayer description:Audio player with pitch control and a GNOME GUI maintainer: [EMAIL PROTECTED] status: FORBIDDEN deprecated because: Remote code execution: http://vuxml.FreeBSD.org/9855ac8e-2aec-11db-a6e2-000e0c2e438a.html expiration date:2006-12-01 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=alsaplayer portname: audio/gdesklets-xmms description:Compact desklet that allows you to control your XMMS from your desktop maintainer: [EMAIL PROTECTED] deprecated because: Disappeared from the internet expiration date:2006-12-07 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=gdesklets-xmms portname: audio/xmms-rateplug description:Add song rating control to the XMMS playlist maintainer: [EMAIL PROTECTED] deprecated because: Project disappeared from the internet expiration date:2006-12-01 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=xmms-rateplug portname: biology/biojava description:Open-source java tools for processing biological data maintainer: [EMAIL PROTECTED] status: BROKEN deprecated because: Does not compile expiration date:2006-12-01 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=biologyportname=biojava portname: chinese/iiimf-le-chewing description:IIIMF Chewing engine, an intelligent Chinese phonetic input method maintainer: [EMAIL PROTECTED] status: BROKEN deprecated because: fails to install (dependency problem) expiration date:2006-12-01 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=iiimf-le-chewing portname: comms/vpb-driver description:Device-driver for the Voicetronix OpenLine4 PCI telephony cards maintainer: [EMAIL PROTECTED] status: BROKEN deprecated because: leaves files behind on deinstall expiration date:2006-12-01 build errors: http://pointyhat.freebsd.org/errorlogs/ia64-errorlogs/e.7.2006072809/vpb-driver-2.4.9_2.log.bz2 (Aug 31 06:37:51 UTC 2006) http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.5.2006100420/vpb-driver-2.4.9_2.log.bz2 (Sep 24 06:02:47 UTC 2006) overview: http://portsmon.FreeBSD.org/portoverview.py?category=commsportname=vpb-driver portname: deskutils/mhc-xemacs21-mule description:Message Harmonized Calendaring system maintainer: [EMAIL PROTECTED] status: IGNORE deprecated because: hangs during build expiration date:2006-12-01 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=deskutilsportname=mhc-xemacs21-mule portname: devel/alleyoop description:A graphical front-end to Valgrind memory checker maintainer: [EMAIL PROTECTED] status: BROKEN deprecated because: Does not compile expiration date:2006-12-01 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=alleyoop portname: devel/callgrind description:Valgrind skin for cache simulation and call tracing maintainer: [EMAIL PROTECTED] status: IGNORE deprecated because: Dumps core \(SIGBUS\). \(Also v. 0.9.10\!\) expiration date:2006-12-01 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=callgrind portname: devel/cl-asdf-cmucl description:A system definition facility for Common Lisp maintainer: [EMAIL PROTECTED] status: BROKEN deprecated because: does not build expiration date:2006-12-01 build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.5.200606/cl-asdf-cmucl-2003.05.16.log.bz2 (Sep 26 05:10:12 UTC 2006)
Re: FreeBSD 6.1-R-p10 and PHP 5.2.0
On Wed, 2006-11-22 at 12:38 -0600, [EMAIL PROTECTED] wrote: I just tried sessions at the beginning and : pid 8311 (httpd), uid 0: exited on signal 11 (core dumped) darn it :( [...] In the meantime I recompiled all with a portupgrade -rRf and that solved the problem and I erased all the core files. But the problem was probably one of my prior upgrades didn't compile something that was causing the problem. The problem IS with php modules order - check links posted earlier. You just happen to have working order in your extensions.ini now. Save it for future reference :) M. -- Miroslaw Psyborg Jaworski GCS/IT d- s+:+ a C++$ UBI$ P+++$ L- E--- W++(+++)$ N++ o+ K- w-- O- M- V- PS+ PE++ Y+ PGP t 5? X+ R++ !tv b++(+++) DI++ D+ G e* h++ r+++ y? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Fwd: [Jackit-devel] Jack still unusable on FreeBSD
Hello. I'm currently in dialogue with the developers of Jack (audio/jackit) with a view to getting better Jack support on FreeBSD. We've come up against an obstacle, however... -- Forwarded message -- From: Jack O'Quin [EMAIL PROTECTED] Date: 22-Nov-2006 01:16 Subject: Re: [Jackit-devel] Jack still unusable on FreeBSD To: mal content [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] On 10/24/06, mal content [EMAIL PROTECTED] wrote: Hello. Whenever any client disconnects from jackd on FreeBSD (6.1), the following occurs: cannot read request from client (0/2100/Resource temporarily unavailable) could not handle external client request Getting the handle on this will probably require some hands-on debugging. Does anyone have a net-accessible FreeBSD 6.1 system that would provide me (temporarily) with a guest login? I think most of these config and startup problems can likely be debugged without needing direct access to the sound card. -- joq Please contact Jack O'Quin directly if you can help! cheers, MC ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
problem with adocbook-xml xmlcatmgr
I'm reinstalling ports after a panic, and while reinstalling textproc/sdocbook-xml get: install -o root -g wheel -m 444 /usr/ports/textproc/sdocbook-xml/work/catalog.xml /usr/local/share/xml/sdocbook/1.1 /usr/local/bin/xmlcatmgr -sc /usr/local/share/sgml/catalog.ports add CATALOG /usr/local/share/xml/sdocbook/1.1/catalog xmlcatmgr: entry already exists for `/usr/local/share/xml/sdocbook/1.1/catalog' of type `CATALOG' *** Error code 1 Stop in /usr/ports/textproc/sdocbook-xml. I know _nothing_ about xmlcatmgr. (Even after reading the man page.) Someone want to smack me with some clue? Please? Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Request to remove www/emp from ports
Hello, Is it possible that someone could remove www/emp from the ports collection? I won't be supporting it anymore, and the ftp site will be offline permanently at the end of this month. Thanks! --Allan Bowhill Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail beta. http://new.mail.yahoo.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fwd: [Jackit-devel] Jack still unusable on FreeBSD
On Thu, 23 Nov 2006 03:44:20 + mal content [EMAIL PROTECTED] wrote: Hello. I'm currently in dialogue with the developers of Jack (audio/jackit) with a view to getting better Jack support on FreeBSD. We've come up against an obstacle, however... I have a poor man workaround for this: http://people.freebsd.org/~ariff/ports/audio_jack/ There will be a major fixup for the sound driver with respect to latency, and I'm taking jack issues into account as well. For other applications, see http://people.freebsd.org/~ariff/ports/ . -- Forwarded message -- From: Jack O'Quin [EMAIL PROTECTED] Date: 22-Nov-2006 01:16 Subject: Re: [Jackit-devel] Jack still unusable on FreeBSD To: mal content [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] On 10/24/06, mal content [EMAIL PROTECTED] wrote: Hello. Whenever any client disconnects from jackd on FreeBSD (6.1), the following occurs: cannot read request from client (0/2100/Resource temporarily unavailable) could not handle external client request Getting the handle on this will probably require some hands-on debugging. Does anyone have a net-accessible FreeBSD 6.1 system that would provide me (temporarily) with a guest login? I think most of these config and startup problems can likely be debugged without needing direct access to the sound card. -- joq Please contact Jack O'Quin directly if you can help! cheers, MC ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED] -- Ariff Abdullah FreeBSD ... Recording in stereo is obviously too advanced and confusing for us idiot * users :P pgpBT4LsXXWhC.pgp Description: PGP signature
denyhosts config reference
The command args section of /usr/local/etc/rc.d/denyhosts specifies an incorrect location of the config file. Looks like this was reported awhile ago, http://lists.freebsd.org/pipermail/freebsd-ports/2006-July/033699.html. Also, for those who want to run this as a daemon, may I suggest you add the necessary rc.conf mod to the message that displays when make install is done. Brian ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
