Date: Wed, 22 Sep 2010 10:15:08 +0800 From: fengdreamer@126.com To: freebsd-questions@freebsd.org Subject: =?utf-8?b?5Zue5aSN77ya?= freebsd-questions Digest, Vol 329, Issue 2 Message-ID: <3BXxsfllH2Vg.dQN4YV04@smtp.126.com>
next in thread | raw e-mail | index | archive | help
=E5=8E=9F=E4=BF=A1=E6=81=AF =E4=B8=BB=E9=A2=98=EF=BC=9A freebsd-questions Digest, Vol 329, Issue = 2 =E5=8F=91=E4=BB=B6=E4=BA=BA=EF=BC=9A = freebsd-questions-request@freebsd.org =E6=97=A5=E6=9C=9F=EF=BC=9A 2010/09/21 14:22 Send freebsd-questions mailing list submissions to freebsd-questions@freebsd.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.freebsd.org/mailman/listinfo/freebsd-questions or, via email, send a message with subject or body 'help' to freebsd-questions-request@freebsd.org You can reach the person managing the list at freebsd-questions-owner@freebsd.org When replying, please edit your Subject line so it is more specific than "Re: Contents of freebsd-questions digest..." Today's Topics: 1. Re: The nightmarish problem of installing a printer (perryh@pluto.rain.com) 2. Re: apache22 and threads (Michael Powell) 3. dnsmasq, mfsBSD, status refused (Samuel Mart?n Moro) 4. Re: TCP Logs Why "Connection attempt to closed port" (Daniel = Bye) 5. Re: why is the PHP stuff line "off" by default in ports/lang/php5? (doug@safeport.com) 6. Re: Problem running custom startup script at proper time (Robert Bonomi) 7. Re: why is the PHP stuff line "off" by default in ports/lang/php5? (Michael Powell) 8. Re: The nightmarish problem of installing a printer (Robert Bonomi) 9. Re: Problems with upgrade - lost partition (Lokadamus) 10. RSS to email? (Chris Maness) 11. Re: RSS to email? (Glen Barber) 12. Re: RSS to email? (Chip Camden) 13. Re: RSS to email? (Glen Barber) 14. Re: why is the PHP stuff line "off" by default in ports/lang/php5? (Rob Farmer) 15. Re: RSS to email? (Michelle Konzack) 16. Re: why is the PHP stuff line "off" by default in ports/lang/php5? (Matthew Seaman) 17. Re: extra open ports in rkhunter (Carl Johnson) 18. Re: make buildkernel pre-build too long (Alexander Best) 19. Re: Problem running custom startup script at proper time = (Aaron) 20. Re: The nightmarish problem of installing a printer (C. P. = Ghost) 21. Zip file making issues (Ryan Coleman) 22. Re: Zip file making issues (Matt Emmerton) 23. Re: Zip file making issues (Ryan Coleman) 24. wireless networking (William Kindler) 25. Re: Zip file making issues (Michael Ross) 26. Re: Zip file making issues (Ryan Coleman) 27. Re: Zip file making issues (Matthew Seaman) 28. Re: Zip file making issues (Ryan Coleman) 29. Re: make buildkernel pre-build too long (David DEMELIER) ---------------------------------------------------------------------- Message: 1 Date: Mon, 20 Sep 2010 05:20:52 -0700 From: perryh@pluto.rain.com Subject: Re: The nightmarish problem of installing a printer To: FreeBSD@insightbb.com Cc: freebsd-questions@freebsd.org Message-ID: <4c9751a4.POuJNkjk++rGHEd0%perryh@pluto.rain.com> Content-Type: text/plain; charset=3Dus-ascii Steven Friedrich <FreeBSD@insightbb.com> wrote: > > "Common Unix Printing System" certainly sounds as if the intent > > was to be the "ONE thing that is used for printing". Whether > > they did a good job of it is another question entirely :( > > I think that you don't fully apreciate the task at hand. When > Unix was first invented, there were no laser printers, ink jets, > USB, etc. > > That no one can create a one-size fits all solution OWES to the > fact it's simply not always possible to unify disparate designs. > They weren't designed to be interoperable. Technology keeps > marchng forward. We need to discard all of it eventually. Back in the CP/M and early MS-DOS days, similar doubts were raised regarding display systems. Fortunately, those doubts did not stop some developers from doing what others thought impossible. The results included X11, which has been rather durable for a considerable time. ------------------------------ Message: 2 Date: Mon, 20 Sep 2010 08:19:37 -0400 From: Michael Powell <nightrecon@hotmail.com> Subject: Re: apache22 and threads To: freebsd-questions@freebsd.org Message-ID: <i77jch$cee$1@dough.gmane.org> Content-Type: text/plain; charset=3D"ISO-8859-1" Victor Sudakov wrote: > Colleagues, >=20 > When building apache22 from ports, would you recommend to enable or = to > disable threads support? >=20 > Even more confusing is the fact that for ports/www/apache22 the = default > is: "Enable threads support in APR is off" (WITHOUT_THREADS=3Dtrue) >=20 > while for ports/devel/apr1 the default is: > "Enable Threads in apr is on" (WITH_THREADS=3Dtrue). >=20 > Thank you in advance for any input. >=20 > PS ports/devel/apr1 will also be used for the subversion client. >=20 I wouldn't mind someone with more apache22-fu to elaborate, correcting the = following if necessary. My thoughts are this matters depending upon which mpm you choose to build = into apache. The default is prefork, and it handles incoming requests by = spawning child processes. The main shortcoming associated with this = approach=20 is resources such as database connections are not shareable between the = child processes, e.g. each must have its own. So each incoming request has = to fork a child, then build up, consume, and tear down the database = connection. The lifetime will exist during the keepalive period and just be = sitting there in memory idle most of the time following the task = completion. A threaded mpm such as worker or event, is designed to spawn threads within = a process to service incoming requests. One is a hybrid, in that it also = forks additional processes as well when a preset thread count is reached. = When all threads are contained within the same process each thread is able = to share and consume resources in a pool amongst other threads. So an idle = database connection which has finished serving a previous request can be = immediately reused by a new thread without a build up tear down = cycle. So my idea of the usage of WITH_THREADS is for the default prefork mpm it = would be "NO", while for the event mpm it would be "YES". An additional consideration might be what kind of backend is used. For = example, since not all of PHP is known to be thread safe it is not=20 recommended for use with a threaded server and mod_php. The way to get = around this situation is to separate PHP from Apache with something like = mod_fcgid which runs PHP as a FastCGI. This way you can safely run a = threaded Apache with non-thread safe PHP. As far as which is the better = approach I still am not really sure. Each has its set of pros and = cons. -Mike ------------------------------ Message: 3 Date: Mon, 20 Sep 2010 14:56:35 +0200 From: Samuel Mart?n Moro <faust64@gmail.com> Subject: dnsmasq, mfsBSD, status refused To: dnsmasq-discuss@lists.thekelleys.org.uk, freebsd-questions@freebsd.org Message-ID: <AANLkTim9wjDnBjXi-tV7mry_hPeSEFJYck1ZV_DKG1nz@mail.gmail.com> Content-Type: text/plain; charset=3DISO-8859-1 Hi I'm trying to replace my gate with a qnap ts-509. I installed mfsBSD, based on FreeBSD-8.1-RELEASE amd64. I just had to build some pre-configured packages, add ipfw, ipfw_nat = and libalias to boot modules. Everything's working just fine, except for the DNS = (dnsmasq-2.55,1.tbz, rebuilt with config files and ipfw startup script) DHCP works perfectly. But DNS does not... Even on the (soon-to-be) gateway, so I'm assuming ipfw is not related to = the problem (in doubt, I still send it) root@phi /real/tmp : ipfw list 00001 check-state 00002 allow ip from any to any via lo0 00003 allow tcp from any to any established 00500 allow ip from any to any via bge1 00666 allow tcp from me to any out via bge0 setup uid root keep-state 65535 deny ip from any to any (since bge0 is not plugged, it's quite empty...) root@phi /real/tmp : ./dig @localhost alpha.faust-network ; <<>> DiG 9.6.2-P2 <<>> alpha.faust-network ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 13068 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;alpha.faust-network. IN A ;; Query time: 13 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Mon Sep 20 13:41:15 2010 ;; MSG SIZE rcvd: 37 basically, my configuration is the following: cache-size=3D1024 local-ttl=3D15 log-dhcp interface=3Dbge1 bind-interfaces no-negcache dhcp-range=3D10.254.254.1,10.254.254.254,255.0.0.0,1h dhcp-boot=3Dpxelinux.0,omega,10.42.42.45 # PXE TFTP server = (omega) dhcp-option=3D3,10.242.42.254 # gateway dhcp-option=3D19,1 # option ip-forwarding = off dhcp-option=3D23,42 # TTL de 42 dhcp-option=3D44,10.242.42.254 # Wins Server dhcp-option=3D45,10.242.42.254 # NetBios DDS dhcp-option=3D46,8 # NetBios Node Type dhcp-option=3Doption:ntp-server,213.186.41.134,88.191.79.242,193.55.167.2,80= .65.235.4,194.57.191.1,91.121.45.45 dhcp-script=3D/usr/local/bin/dhcp_action domain=3Dfaust-network expand-hosts bogus-nxdomain=3D64.94.110.11 #get SSL certificate from another = CAServer localmx selfmx conf-file=3D/usr/local/etc/blocklist.conf # filter adds, shits, facebook, = ... my resolv.conf: nameserver 10.242.42.254 #localhost, priv addr nameserver 8.8.4.4 domain faust-network I already have a dnsmasq working perfectly on my current gate (ArchLinux-x86_64). I copied the configuration, making a few changes (192.168.0.0/24 -> 10.0.0.0/8). So, I don't understant what I'm doing wrong.... Any idea? Cheers, --- Samuel Mart=EF=BF=BDn Moro {EPITECH.} tek5 CamTrace S.A.S ------------------------------ Message: 4 Date: Mon, 20 Sep 2010 15:21:40 +0100 From: Daniel Bye <freebsd-questions@slightlystrange.org> Subject: Re: TCP Logs Why "Connection attempt to closed port" To: freebsd-questions@freebsd.org Message-ID: <20100920142140.GA12913@catflap.slightlystrange.org> Content-Type: text/plain; charset=3D"us-ascii" On Mon, Sep 20, 2010 at 11:58:38AM +0100, David Southwell wrote: >=20 > Large quantities of these errors constantly appear in = log/dmesg.today. >=20 > Can anyone explain what is going on and whether any action is needed. If = so=20 > how to go about tracing the cause. - - - = =EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD"=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD">"= =EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD"=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF= =BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD= =EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD - - -
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3BXxsfllH2Vg.dQN4YV04>