Actually I just realised I upgraded my ruby version
from: 1.8.60-p287
to: 1.8.7-p72

This might be why merb isn't crashing on "socket all ready in use"

On Mon, Jan 26, 2009 at 10:18 PM, Nicholas Orr <[email protected]> wrote:
> I spent the day setting up a new gentoo vmware vm on this new PC and I
> am now able to save models/controllers and merb will restart itself
> properly without getting stuck.
> Using 2.6.27-gentoo-r8 kernel.
> Another unusual occurance is now the "git-completion" script doesn't
> work either. Maybe I got a new version of bash or something...
> I don't really know what is going on. All i know is the issue of
> having to continually watch the console for merb to crash seems to be
> gone. I shall now copy this VM to my other two PCs :)
>
> On Wed, Dec 31, 2008 at 2:50 PM, Nicholas Orr <[email protected]> wrote:
>> Not fixed for me :(
>>
>> I still have to use my kick script to kill and restart merb :/
>>
>> On Wed, Dec 31, 2008 at 6:56 AM, Jon Hancock <[email protected]> wrote:
>>>
>>> at least his new bug is offset by the "killing merb bug" (didn't
>>> always let go of the listener socket) seems to be fixed.  I can kill
>>> merb more regularly without having to find the process and manually
>>> kill it ;).
>>>
>>> On Dec 30, 3:52 am, cult hero <[email protected]> wrote:
>>> > I just upgraded to 1.0.7 and updated a project. Unless I missed
>>> > something, all I did was change the version number in the dependancies
>>> > file.
>>> >
>>> > Now, while working in development mode, if I make a change to a
>>> > template I have to manually restart merb for the changes to show up. I
>>> > didn't have to do this under 1.0.6.1.
>>> >>>
>>
>>
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"merb" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [email protected]
For more options, visit this group at http://groups.google.com/group/merb?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to