Re: Nginx, FCGI and C programs [SOLVED]
On 6 October 2012 05:55, Artturi Alm artturi@gmail.com wrote: I'm not sure what you're exactly trying to do, is it cgi or fastcgi you want to use? Sorry for not being enough clear and thanks for having crystal ball near you, you read my intention :) i managed to get cgi working with fcgi-cgi, yet i didn't figure out how to make use of fastcgi. atleast under chroot i was receiving error about prematurely closed connection while reading response header from upstream. this was through unix socket. i launched the 'fastcgi processes' by hand with spawn-fcgi, and saw them die one after another when trying to access it via browser, to be clear, 1 process died per request, and i had launched multiple w/-F arg for spawn-fcgi. i'm not going to try debugging it any further, plain cgi is what i was after. Yes, thanks in a thousand for everyone involved! This solved my problem. Case closed and sorry for the noise. -- Ville
The new queueing subsystem
Hello Misc, Henning, As a fresh OpenBSD user, i'd like to learn the release date of new queueing subsystem. Is there any date on your mind or any updates? I guess it will be a part of OpenBSD 5.2 or 5.3? Please forgive my curiosity. I really want to use new queueing subsystem in production. Thanks. -- Theron
代_开_发_栗,QQ:2586801282
Ö£º¹ó¹«Ë¾¸ºÔðÈË£¨²Æ_Îñ£¬¾_Àí£©
ÄãÃǺ㬱¾¹«Ë¾ÏÖÓУ¨½¨Öþ£¬¹ã¸æ£¬·þÎñ£¬ÔËÊ䣬ÉÌÆ·ÏúÊÛ£¬×âÁÞ£©µÈ·¢Àõ´ú¿ª¡£»ú´ò£¬°üÕ棬ÑéÍ긶¿î¡£Èç¹ó¹«Ë¾ÓÐÐèÒª,»¶ÓÀ´µç×Éѯ¡£±¾¹«Ë¾ËùÓÃÀõ¾Ý¾ùΪ¸÷µ¥Î»ÔÚË°Îñ¾ÖËùÉêÁ죬¿ÉÉÏÍø²éѯ»òµ½Ë°Îñ¾ÖµÖ¿ÛÑéÖ¤
ÊÖ»ú£º13590208936 ÕÅС±ø
QQ£º2586801282
try{parent.JS.modules[window.name].content.setHeight();}catch(e){}
¨
Re: Bibliography on IPv6
I intend to get my hands on an IPv6 book to deal with some of the issues I'm having - which are mainly my lack of knowledge and expertise on the subject. I've seen IPv6 Essentials, from O'Rilley mentioned a lot, and I've heard it has a BSD-related section too. Probably not what your after but this was fired across this list a while back and the site may be useful. http://www.hackingipv6networks.com/past-trainings/hip2011-hacking-ipv6-networks.pdf -- ___ 'Write programs that do one thing and do it well. Write programs to work together. Write programs to handle text streams, because that is a universal interface' (Doug McIlroy) ___
OpenBSD 5.2 song - and pre-orders for 5.2!
We have made available the song that will come out with the 5.2 release. The song and details of it are linked from: http://openbsd.org/lyrics.html Go have a look and a listen! The details for the upcoming 5.2 release are available at http://www.openbsd.org/52.html A reminder to you all that Pre-orders for 5.2 are can be made by starting from: http://openbsd.org/orders.html Please consider buying a CD or three. Sales of CD's and merchandise are vital to OpenBSD's continued existence. It is only this revenue stream that keeps the power and air conditionong on, and keeps us all hacking. Thanks!
Re: OpenBSD 5.2 song - and pre-orders for 5.2!
Bob Beck wrote: We have made available the song that will come out with the 5.2 release. The song and details of it are linked from: http://openbsd.org/lyrics.html http://www.openbsd.org/lyrics.html is more interesting at present. (it has actual lyrics and commentary) Go have a look and a listen! The details for the upcoming 5.2 release are available at http://www.openbsd.org/52.html A reminder to you all that Pre-orders for 5.2 are can be made by starting from: http://openbsd.org/orders.html Is http://www.openbsd.org/orders.html preferred here as well ? Please consider buying a CD or three. Sales of CD's and merchandise are vital to OpenBSD's continued existence. It is only this revenue stream that keeps the power and air conditionong on, and keeps us all hacking. Thanks!
Re: 5.2 PRE-ORDERS
Great! I'll push my management to place an order. On 5 okt 2012, at 12:15, OpenBSD Europe m...@openbsdeurope.com wrote: We will be making the shipment from Canada soon. If you would like your 5.2 on time we request the orders ASAP :-) Thanks folks!
Re: Recommended new laptop under US$800 for OpenBSD
On Fri, Oct 05, 2012 at 10:00:11PM -0500, Francisco Valladolid H. wrote: I'm currently using a old Thinkpad T61p, good machine and OpenBSD 5.1 work fine. And I am very satisfied with my ThinkPad T500 (September 2008 model, or August 2009, I'm not sure...) which my nephew gave to me since the company he works for considered it outdated. I'm running current and everything works except for bluetooth and the fingerprint sensor. Excellent battery time and silent performance. (The built in Ericsson mobile broadband adapter gets recognized as cdce0/umodem0, but I'm not sure how to configure it.. :-) Anyway: Unix means typing and you should focus on the quality of the keyboard. And the keyboard on the ThinkPad is IMHO simply the best.
Re: Recommended new laptop under US$800 for OpenBSD
On Sat, Oct 06, 2012 at 08:46:28PM +0200, Erling Westenvik wrote: And I am very satisfied with my ThinkPad T500 (September 2008 model, or August 2009, I'm not sure...) which my nephew gave to me since the company he works for considered it outdated. I'm running current and everything works except for bluetooth and the fingerprint sensor. Excellent battery time and silent performance. (The built in Ericsson mobile broadband adapter gets recognized as cdce0/umodem0, but I'm not sure how to configure it.. :-) With crypto softraid it was slow, I just put inside OCZ Vertex 3 and it is much better ;) j.
Re: Recommended new laptop under US$800 for OpenBSD
On Sat, Oct 6, 2012 at 8:46 PM, Erling Westenvik erling.westen...@gmail.com wrote: On Fri, Oct 05, 2012 at 10:00:11PM -0500, Francisco Valladolid H. wrote: I'm currently using a old Thinkpad T61p, good machine and OpenBSD 5.1 work fine. And I am very satisfied with my ThinkPad T500 (September 2008 model, or August 2009, I'm not sure...) which my nephew gave to me since the company he works for considered it outdated. I'm running current and everything works except for bluetooth and the fingerprint sensor. Have you tried sysutils/login_fingerprint and security/libfprint ? ciao, David
Re: Recommended new laptop under US$800 for OpenBSD
I use a gen2 Intel ThinkPad X220 (for now) with FreeBSD. When I got it I tried to install OpenBSD and it worked for a day and I wiped it. I use FreeBSD because of the KMS support at this time. Battery time is about 1 hour less than on Windows. If you want guranteed support for almost all devices, get a T61/X61 and maybe a T*00/X200 series. My main concern was battery life as I get about 8 hours with WiFi on right now so I went for gen2 Intel series. Also this is the last serious with the good old keyboard. -- Lyubomir Grigorov (bgalakazam)
Question about the code
Hi, it's about src/usr.sbin/unbound/ldns/drill/work.c at line 184: What is the 'fp' FILE used for ? Here - if I'm not mistaken - we fopen() filename, and that's it. We don't use the 'fp' variable, and we never fclose() it. Am I wrong ? Thanks
Re: Question about the code
On Sat, Oct 06, 2012 at 10:11:20PM +0200, rustyBSD wrote: Hi, it's about src/usr.sbin/unbound/ldns/drill/work.c at line 184: What is the 'fp' FILE used for ? Here - if I'm not mistaken - we fopen() filename, and that's it. We don't use the 'fp' variable, and we never fclose() it. Am I wrong ? Thanks Good catch. There's obviously some unfinished refactoring. The file handling got into packetbufffromfile, all other callers got it... This one was left stranded out. What's funny, though, is that the code in packetbufffromfile is worse than the code you're talking about, especially the error message doesn't mention the filename...
man 2 sigprocmask
It seems the sigprocmask syscall takes different arguments than the libc stub for sigprocmask(2). Though the differences are easily understood by browsing source, there don't appear to be any man pages describing the syscall interface, and wonder if this is an intentional or accidental oversight. Thanks. --david
Re: man 2 sigprocmask
On Sat, Oct 6, 2012 at 4:06 PM, David Higgs hig...@gmail.com wrote: It seems the sigprocmask syscall takes different arguments than the libc stub for sigprocmask(2). Though the differences are easily understood by browsing source, there don't appear to be any man pages describing the syscall interface, and wonder if this is an intentional or accidental oversight. The only places this should possibly be documented, IMO, are kdump(1) and syscall(2), and in the latter it should be at most a warning and _not_ specific info about the affected calls. The syscall ABI is only supported for the calls that the system libraries actually use, and even there the guarantee is only for a couple releases. For example, the sigreturn() in the OpenBSD 5.0 amd64 libc will not work against a 5.2 kernel. Philip Guenther
Re: Recommended new laptop under US$800 for OpenBSD
On Sat, Oct 06, 2012 at 09:04:58PM +0200, David Coppa wrote: On Sat, Oct 6, 2012 at 8:46 PM, Erling Westenvik erling.westen...@gmail.com wrote: On Fri, Oct 05, 2012 at 10:00:11PM -0500, Francisco Valladolid H. wrote: I'm currently using a old Thinkpad T61p, good machine and OpenBSD 5.1 work fine. And I am very satisfied with my ThinkPad T500 (September 2008 model, or August 2009, I'm not sure...) which my nephew gave to me since the company he works for considered it outdated. I'm running current and everything works except for bluetooth and the fingerprint sensor. Have you tried sysutils/login_fingerprint and security/libfprint ? Not really. The device shows up as ugen1 at uhub3 port 1 AuthenTec Fingerprint Sensor rev 2.00/17.03 addr 2 but when I install the package and try to run # enroll_fingerprint -f (I'm not telling you which finger ;-) I get No devices detected! According to the homepage of libfprint, the AuthenTec devices are not (yet) supported?
Re: man 2 sigprocmask
On Sat, Oct 6, 2012 at 7:48 PM, Philip Guenther guent...@gmail.com wrote: On Sat, Oct 6, 2012 at 4:06 PM, David Higgs hig...@gmail.com wrote: It seems the sigprocmask syscall takes different arguments than the libc stub for sigprocmask(2). Though the differences are easily understood by browsing source, there don't appear to be any man pages describing the syscall interface, and wonder if this is an intentional or accidental oversight. The only places this should possibly be documented, IMO, are kdump(1) and syscall(2), and in the latter it should be at most a warning and _not_ specific info about the affected calls. The syscall ABI is only supported for the calls that the system libraries actually use, and even there the guarantee is only for a couple releases. For example, the sigreturn() in the OpenBSD 5.0 amd64 libc will not work against a 5.2 kernel. To reiterate for personal clarity, section 2 manpages for syscalls actually refers to the corresponding libc interfaces? That makes sense in that no userland code would be using syscalls directly due to complications like errno handling. Thanks. --david
Re: man 2 sigprocmask
On Sat, Oct 6, 2012 at 8:25 PM, David Higgs hig...@gmail.com wrote: To reiterate for personal clarity, section 2 manpages for syscalls actually refers to the corresponding libc interfaces? That makes sense in that no userland code would be using syscalls directly due to complications like errno handling. Yes, exactly. Philip Guenther
