Instead of filing another bug i'd better follow this.

In some old-style init systems, the networking init.d script does 
effectively nothing. Everything is done by network-manager, which starts 
only on runlevel 2 with:

/etc/init.d/S26network-manager

While ejabberd is installing with

update-rc.d default...

so it is starting with:

/etc/init.d/S20ejabbed

Reprioritizing ejabberd after networn-manager fixes the issue.



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to