I wait for the updated port :)
Original Message
Subject: Re: [Cherokee] Cherokee Web Server version in ports tree
From: Diego Schulz
To: Michiel van Es
Date: 03/12/2010 02:52 PM
On Fri, Mar 12, 2010 at 10:35 AM, Michiel van Es wrote:
Original Message
On Fri, Mar 12, 2010 at 10:35 AM, Michiel van Es wrote:
>
>
> Original Message
> Subject: Re: [Cherokee] Cherokee Web Server version in ports tree
> From: Diego Schulz
> To: Michiel van Es
> Date: 03/12/2010 02:33 PM
>
>> On Fri, Mar 12, 2
Original Message
Subject: Re: [Cherokee] Cherokee Web Server version in ports tree
From: Diego Schulz
To: Michiel van Es
Date: 03/12/2010 02:33 PM
On Fri, Mar 12, 2010 at 9:53 AM, Michiel van Es wrote:
Hi,
I don't know if it is a problem but I also found out tha
On Fri, Mar 12, 2010 at 9:53 AM, Michiel van Es wrote:
> Hi,
>
> I don't know if it is a problem but I also found out that the install does
> not create a cherokee user on freebsd and that cherokee is running as root
> default on freebsd...
Yes, I noticed that too. I also changed the user manuall
would be nice that the installer
installs the cherokee user and set the permissions right and then
startup as cherokee user).
Kind regards,
Michiel
Original Message
Subject: Re: [Cherokee] Cherokee Web Server version in ports tree
From: Alvaro Lopez Ortega
To: Diego Schulz
On 12/03/2010, at 13:30, Diego Schulz wrote:
>>> Bad news is that the problem persists in 0.99.43.
>>> Cherokee 0.99.43 doesn't show this problem running on linux (debian).
>>
>> Could you please log a bug for it?
>> http://bugs.cherokee-project.com/new
>
> Done, issue #170.
>
>> It's kind of
On Fri, Mar 12, 2010 at 3:21 AM, Alvaro Lopez Ortega
wrote:
> Hello Diego,
>
> On 12/03/2010, at 00:48, Diego Schulz wrote:
>
>> 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 comm
Hello Diego,
On 12/03/2010, at 00:48, Diego Schulz wrote:
> 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
On Tue, Mar 9, 2010 at 7:34 PM, wen heping wrote:
> On Wed, Mar 10, 2010 at 6:02 AM, Diego Schulz wrote:
>> Can I help maintaining Cherokee port? The current available version
>
> Welcome to maintain this unmaintained port.
> I will take it.
>
> wen
>
>
>> (0.99.38) has various bugs fixed in the
On Wed, Mar 10, 2010 at 6:02 AM, Diego Schulz wrote:
> Can I help maintaining Cherokee port? The current available version
Welcome to maintain this unmaintained port.
I will take it.
wen
> (0.99.38) has various bugs fixed in the latest upstream version.
>
> Here's the distinfo diff:
>
> 1,3c1,
Can I help maintaining Cherokee port? The current available version
(0.99.38) has various bugs fixed in the latest upstream version.
Here's the distinfo diff:
1,3c1,3
< MD5 (cherokee-0.99.38.tar.gz) = 67be28eda0673598fbb5b1cbd70de455
< SHA256 (cherokee-0.99.38.tar.gz) =
217bb708c8cc637570d07b335d
11 matches
Mail list logo
