New wildfire port for FreeBSD

Hi, folks. I’'ve created net-im/wildfire port, so now you can install it from FreeBSD ports collection.

If you have some questions or PR’'s please mail me. You can find my email on Makefile.

Have a nice day.

Do you have /usr/local/etc/rc.d/ scripts included for easy startup/shutdown/reloading of the wildfire server? I had to write these myself and I didn’'t like exerting the effort Thanks for doing this!

Yes. It’‘s included. It’'s a typical rc script that uses new generation rc.subr functionality.

Don’'t forget to spam rc.conf with “wildfire_enable=“YES”” string.

Also i want notice that you don’‘t need root privileges to run wildfire daemon any more. It’'s running with “wildfire” user privs by default.

Thank to Nikolay Pavlov for your wildfire for FreeBSD, but I did not find where to put the plugins

You can put them to /usr/local/share/java/wildfire/plugins

I have tried but the plugins did not work

Could you please be more specific on what are you trying to install? What plugins? Error messages?

On Linux, I only put the plugins (*.jar) into $WILDFIRE_HOME/plugins folder, Wildfire would extract and load into the system.

But on FreeBSD, Wildfire could not load the plugins.

Well. For officical plugins i am using “Plugins” menu on wildfire web interface:

For example let’'s install Asterisk-IM plugin:

You need to go to “Plugins” menu then click on “availabe plugins” and click on Install button.

For unofficial plugins.

You need to download plugin to /usr/local/share/java/wildfire/plugins

For example let’'s install IM Gateway plugin:

root@support:~# cd /usr/local/share/java/wildfire/plugins/

root@support:/usr/local/share/java/wildfire/plugins# fetch http://www.jivesoftware.org/wildfire/plugins-beta/gateway.jar

gateway.jar 100% of 559 kB 1492 kBps

root@support:/usr/local/share/java/wildfire/plugins# chown wildfire:wildfire gateway.jar

root@support:/usr/local/share/java/wildfire/plugins# ls -la

total 1004

drwx------ 12 wildfire wildfire 512 Nov 25 03:44 .

drwxr-xr-x 4 wildfire wildfire 512 Nov 12 14:10 …

drwxr-xr-x 3 wildfire wildfire 512 Nov 12 14:10 admin

drwxr-xr-x 3 wildfire wildfire 512 Nov 12 14:12 broadcast

-rw-rr 1 wildfire wildfire 9017 Nov 12 14:12 broadcast.jar

-rw-rr 1 wildfire wildfire 16965 Nov 12 14:12 contentFilter.jar

drwxr-xr-x 4 wildfire wildfire 512 Nov 12 14:12 contentfilter

-rw-rr 1 wildfire wildfire 573271 Nov 10 16:52 gateway.jar

drwxr-xr-x 4 wildfire wildfire 512 Nov 12 14:12 presence

-rw-rr 1 wildfire wildfire 16958 Nov 12 14:12 presence.jar

drwxr-xr-x 4 wildfire wildfire 512 Nov 12 14:12 registration

-rw-rr 1 wildfire wildfire 18314 Nov 12 14:12 registration.jar

drwxr-xr-x 4 wildfire wildfire 512 Nov 12 14:12 search

-rw-rr 1 wildfire wildfire 24099 Nov 12 14:12 search.jar

drwxr-xr-x 4 wildfire wildfire 512 Nov 12 14:12 subscription

-rw-rr 1 wildfire wildfire 14270 Nov 12 14:12 subscription.jar

-rw-rr 1 wildfire wildfire 278092 Nov 12 14:12 userImportExport.jar

drwxr-xr-x 5 wildfire wildfire 512 Nov 12 14:12 userimportexport

drwxr-xr-x 4 wildfire wildfire 512 Nov 12 14:12 userservice

-rw-rr 1 wildfire wildfire 13269 Nov 12 14:12 userservice.jar

Then go to “Plugins” menu on wildfire and you’'ll see new IM Gateway Plugin,

also after that you’'ll see gateway directory on /usr/local/share/java/wildfire/plugins

root@support:/usr/local/share/java/wildfire/plugins# ls -la

total 1004

drwx------ 12 wildfire wildfire 512 Nov 25 03:44 .

drwxr-xr-x 4 wildfire wildfire 512 Nov 12 14:10 …

drwxr-xr-x 3 wildfire wildfire 512 Nov 12 14:10 admin

drwxr-xr-x 3 wildfire wildfire 512 Nov 12 14:12 broadcast

-rw-rr 1 wildfire wildfire 9017 Nov 12 14:12 broadcast.jar

-rw-rr 1 wildfire wildfire 16965 Nov 12 14:12 contentFilter.jar

drwxr-xr-x 4 wildfire wildfire 512 Nov 12 14:12 contentfilter

drwxr-xr-x 6 wildfire wildfire 512 Nov 25 03:44 gateway

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

-rw-rr 1 wildfire wildfire 573271 Nov 10 16:52 gateway.jar

drwxr-xr-x 4 wildfire wildfire 512 Nov 12 14:12 presence

-rw-rr 1 wildfire wildfire 16958 Nov 12 14:12 presence.jar

drwxr-xr-x 4 wildfire wildfire 512 Nov 12 14:12 registration

-rw-rr 1 wildfire wildfire 18314 Nov 12 14:12 registration.jar

drwxr-xr-x 4 wildfire wildfire 512 Nov 12 14:12 search

-rw-rr 1 wildfire wildfire 24099 Nov 12 14:12 search.jar

drwxr-xr-x 4 wildfire wildfire 512 Nov 12 14:12 subscription

-rw-rr 1 wildfire wildfire 14270 Nov 12 14:12 subscription.jar

-rw-rr 1 wildfire wildfire 278092 Nov 12 14:12 userImportExport.jar

drwxr-xr-x 5 wildfire wildfire 512 Nov 12 14:12 userimportexport

drwxr-xr-x 4 wildfire wildfire 512 Nov 12 14:12 userservice

-rw-rr 1 wildfire wildfire 13269 Nov 12 14:12 userservice.jar

Hi everyone!

I am new to Jabber and Wildfire. I installed Wildifre from ports but don’'t know how to run(start) it. Please help me.

To automatically launch the daemon after the system is started you need to add line “wildfire_enable=“yes”” to the /etc/rc.conf file.

Then reboot you system or start it with:

  1. /usr/local/etc/rc.d/wildfire start

After that go to http://yourhostnamehere:9090 and configure wildfire server.

Thanks to Nikolay for your reply.

Hi, Nikolay, thanks for the port. Starting Wildfire with rc.d script goes fine, but I’'m unable to stop it or check wildfire status:

  1. /usr/local/etc/rc.d/wildfire status

wildfire not running? (check /var/run/wildfire.pid).

Of course, Wildfire is running and wildfire.pid is there, but the startup script seems unable to find it, so I have to kill the process to stop. Any ideas?

Could you please send me output from:

ps -o ucomm= cat /var/run/wildfire.pid

It looks like check_pidfile function in rc script couldn’'t verify that the process with PID from /var/run/wildfire.pid is running and its first argument matches procname.

No problem; it’'s here:

  1. ps -o ucomm= cat /var/run/wildfire.pid

java

i can’'t get wildfire to start and i have no clue as to where to look to figure out why

any suggestions?

my java appears to have installed

  1. java -version

java version “1.5.0”

Java™ 2 Runtime Environment, Standard Edition (build diablo-1.5.0-b01)

Java HotSpot™ Client VM (build diablo-1.5.0_07-b01, mixed mode)

never mind i figured it out you have to have this wildfire_enable=“yes” in rc.conf as well as run the wildfire.sh script in order to start it up

It looks normal for me.

Could you please modify shbang in wildfire rc script as follows:

#!/bin/sh -x

and send me output from ./wildfire status command.

Also please send me output from

ps awwxu | grep java

command

Thanks.