Cherokee Web Server version in ports tree
dschulz at gmail.com
Thu Mar 11 23:48:46 UTC 2010
On Tue, Mar 9, 2010 at 7:34 PM, wen heping <wenheping at gmail.com> wrote:
> On Wed, Mar 10, 2010 at 6:02 AM, Diego Schulz <dschulz at gmail.com> wrote:
>> Can I help maintaining Cherokee port? The current available version
> Welcome to maintain this unmaintained port.
> I will take it.
>> (0.99.38) has various bugs fixed in the latest upstream version.
>> Here's the distinfo diff:
>> < MD5 (cherokee-0.99.38.tar.gz) = 67be28eda0673598fbb5b1cbd70de455
>> < SHA256 (cherokee-0.99.38.tar.gz) =
>> < SIZE (cherokee-0.99.38.tar.gz) = 4821574
>>> MD5 (cherokee-0.99.43.tar.gz) = ec7d92a26d606e6606e61125cf77d37d
>>> SHA256 (cherokee-0.99.43.tar.gz) = 7a5fc9d2acb54391cefd13e21618be114c7eb5698451944978b71995ffc5179e
>>> SIZE (cherokee-0.99.38.tar.gz) = 5690332
>> In Makefile:
>> < PORTVERSION= 0.99.38
>>> PORTVERSION= 0.99.43
>> freebsd-ports at freebsd.org mailing list
>> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"
Yesterday I sent an updated port. miwi corrected and commited the
changes a few hours later (thanks miwi!).
My main reason for updating from 0.99.38 to 0.99.43 was an extrange
behavior: cherokee daemon doesn't respond to TERM signals sent with
kill(1) (or whatever command you prefer). As a result, it is not
possible to stop the daemon properly with the rc script nor using the
admin interface, you'll need -9.
Bad news is that the problem persists in 0.99.43.
Cherokee 0.99.43 doesn't show this problem running on linux (debian).
More information about the freebsd-ports