Dear Forrest, I don't know how this could _not_ work, but it's certainly not an issue with the MHD library. If you're using one of our demos, our use of 'getchar()' to wait for a signal to terminate might be the cause. In this case, you could just replace 'getchar()' with while(1) sleep(1); to ensure that the process continues after stdin is closed.
My 2 cents Christian On 09/22/2018 04:25 PM, lingweicai wrote: > Dear, > > I am to run my program with libmicrohttpd in background on Linux, with > nohup myprogram end with ‘&’. > > But it always fails. > > How can I solve this problem? > > Thank you > > Forrest > > -------原始邮件------- > > *发件人:* > Christian Grothoff<[email protected]> > *时 间:* 2018/09/18 20:43:58 > *收件人:* > <[email protected]> > *抄 送:* > undefined > *主 题:* > Re: [libmicrohttpd] Regarding Flow control > > On 09/18/2018 02:35 PM, Santos Das wrote: >> Thanks Christian. >> >> I have a question on "MHD_OPTION_CONNECTION_MEMORY_LIMIT" . I went >> through the manual. How does this affect the send/recv buffer size per >> client connection. What does it eventually translate to? > > It does not directly translate. Basically, the send/recv buffer for the > application payload is whatever is left after MHD allocated storage for > the HTTP header. So if you have a 32k buffer and a 1k header, you may > have 30+ kb for send/recv of payload, but if you have a 32k buffer and > an 8k HTTP header, you might have only 24k for the send/recv buffer. > > 发自搜狐邮箱客户端 > > > > > <https://a.app.qq.com/o/simple.jsp?pkgname=com.sohu.mail.client.cordova> > > >
signature.asc
Description: OpenPGP digital signature
