I think you should file that in Lighthouse under the 1.1 series so the rest of us can learn from it. Then we can all try to reproduce it.
On Tue, Nov 24, 2009 at 5:59 AM, MarkMT <[email protected]> wrote: > I'm having some problems getting merb to shut down all its running > processes using 'bin/merb -K all' . If I start merb with 'bin/merb -c > 2' I get four merb processes created, a master, a spawner and two > workers. When I run 'bin/merb -K all' the master and spawner processes > get killed, but the two worker processes remain. > > The problem seems to have existed since I moved to merb edge from > 1.0.11 (until now I've just been running in the console and shutting > down with ctrl-c), initially using the version committed on October 6 > - > http://github.com/wycats/merb/commit/219eebf07582a2143336bbac6ac2f9d828897d23 > . But I have now updated to the latest version and see the same issue. > > Is there something that has changed in the way this is meant to work, > or is this an issue I should file on lighthouse? > > -- > > 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] <merb%[email protected]>. > For more options, visit this group at > http://groups.google.com/group/merb?hl=en. > > > -- Dylan Clendenin 831.331.1484 -- 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.
