Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 15 Mar 2016 13:29:28 +0100
From:      Marko =?UTF-8?B?Q3VwYcSH?= <marko.cupac@mimar.rs>
To:        freebsd-ports@freebsd.org
Subject:   Re: [CFT] net-im/ejabberd to 16.01
Message-ID:  <20160315132928.4b2ec0a0@mephala>
In-Reply-To: <86h9gs26l0.fsf@chateau.d.if>
References:  <86h9gs26l0.fsf@chateau.d.if>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi,

thanks for new port. I've upgraded to 16.02_1 from ports without any
problems:
https://xmpp.net/result.php?domain=3Dmimar.rs&type=3Dclient#general

It took me some time to get used to the fact that I need to stop
ejabberd service, kill epmd process, and restart ejabberd service to
pick up new version. Without killing epmd, ejabberd after upgrade does
not start, but also does not write anything to logs. From my point of
view It would be great if simple 'service ejabberd restart' took care
of restarting corresponding empd process. If this is actually a
terrible idea because of some other implications that don't affect me,
perhaps a line similar to "don't forget to kill epmd process when
upgrading" in pkg-message would be informative.

Regards,
--=20
Before enlightenment - chop wood, draw water.
After  enlightenment - chop wood, draw water.

Marko Cupa=C4=87
https://www.mimar.rs/



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160315132928.4b2ec0a0>