Am Dienstag, den 29.07.2008, 10:11 +0400 schrieb Sergei Golovan: > On 7/29/08, Michael Flaig <[EMAIL PROTECTED]> wrote: > > okay, I'll watch for the update > > Then purge and reinstall, to see what happens. > > If you don't want to wait then you can grab erlang-base and erlang-nox > packages from here: > http://ftp.de.debian.org/debian/pool/main/e/erlang/ (be sure to fetch > version 12.b.3-dfsg-4 for your architecture).
Late night hours are good for testing things, so I did for this bugreport, too :-) [...] > No. The opposite. epmd is Erlang portmapepr daemon. Beam is an Erlang > virtual machine (with ejabberd inside). Uh, my mistake mixed that up then. Sorry. > Multiple epmd is something which must not happen. [...] > I never saw the multiple epmd, so let's try to understand what happens > in your environment. I stripped down the email to be more readable, After the upgrade of erlang-base and erlang-nox ejabberd installes fine on i386 I installed ejabberd without epmd running One beam Process and One epmd running. ejabberdctl working right away Then I purged, left epmd, so it's still running and installed again. One beam Process and One epmd running, so far so good. ejabberctl working, too. I think that with 12.b.3-dfsg-4 of erlang-base and erlang-nox this issue is fixed for lenny as soon as the new packages arrive! Thanks for the help! > > epmd still running and responding after purging. Not good either. > > All seems OK to me (I think that after upgrading erlang-base and > erlang-nox you'll not have to restart ejabberd after apt-get > finishes). Epmd shouldn't stop. You are right, this is not an issue, since I mistakenly assumed that epmd is ejabberd. However it would be nice if epmd would be stopped if no other service is using it, but that's not a topic for this bug report anyway. -- Michael Flaig <[EMAIL PROTECTED]> PROLinux.de
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
