It works!

sl256 — Wed, 04 Apr 2007 22:09:24 +0000

legoscia wrote:

There was a change to the listener API after I wrote that module. I didn't bother to change it, since it seems to work fine anyway, and a new proxy65 is already present in ejabberd SVN.

Thanks for the pointer. Tried the version from SVN, and it works!

--
SL

Probably doesn't matter

legoscia — Tue, 03 Apr 2007 11:41:18 +0000

sl256 wrote:

=SUPERVISOR REPORT==== 3-Apr-2007::08:56:54 ===
     Supervisor: {local,ejabberd_listeners}
     Context:    child_terminated
     Reason:     {undef,[{proxy65_listener,become_controller,[<0.428.0>]},
                         {ejabberd_listener,accept,3},
                         {proc_lib,init_p,5}]}
     Offender:   [{pid,<0.419.0>},
                  {name,7777},
                  {mfa,{ejabberd_listener,
                           start,
                           [7777,proxy65_listener,[{shaper,c2s_shaper}]]}},
                  {restart_type,transient},
                  {shutdown,brutal_kill},
                  {child_type,worker}]

There was a change to the listener API after I wrote that module. I didn't bother to change it, since it seems to work fine anyway, and a new proxy65 is already present in ejabberd SVN.

ejabberd - Comments for "mod_proxy65 errors"

It works!

Probably doesn't matter