prosody
"Filip Hajny" <[email protected]>
| Newsgroups | gmane.os.netbsd.devel.pkgsrc.wip.review |
|---|---|
| Message-ID | <[email protected]> |
Hi guys,
I just commited wip/prosody (with wip/lua-filesystem as dependency), and ideally I'd like to import into pkgsrc before the 2010Q2 freeze. It builds/runs nicely on my Solaris systems, but on NetBSD, I'm seeing this odd thing when I try to enable prosody's POSIX functionality (daemonize, PID file, logging):
bash-4.0# prosodyctl start
/usr/pkg/bin/lua: /usr/pkg/lib/prosody/util/prosodyctl.lua:99: attempt to call field 'kill' (a nil value)
stack traceback:
/usr/pkg/lib/prosody/util/prosodyctl.lua:99: in function 'isrunning'
/usr/pkg/bin/prosodyctl:345: in function '?'
/usr/pkg/bin/prosodyctl:577: in main chunk
[C]: ?
bash-4.0#
I'm not very familiar with (Net)BSD in this context - am I hitting some known limitation? I thought to have the POSIX functionality enabled by default, as it made sense to me, but the source default is actually off, so if there's something NetBSD specific here, I'm fine accepting that as default too.
To test Prosody, 'prosodyctl start' is all you should need to do to get a working XMPP daemon. Obviously putting some real values into ${PKG_SYSCONFBASE}/prosody/prosody.cfg.lua is needed for full operation.
-F
------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit. See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo