[
https://issues.apache.org/jira/browse/FELIX-3818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcelo Antonio Marotta updated FELIX-3818:
-------------------------------------------
Attachment: osgid
osgi
OSGi.service
OSGi.sh
The archives attached here may be organized as follows:
For all users:
% Put osgi file into /etc/conf.d directory
% This file must be customized before using next ones
For users that rely on initscripts:
% Put osgid on /etc/rc.d
% Then, put osgid in DAEMONS=(... osgid) inside /etc/rc.conf
For users that rely on systemd
% Put OSGi.sh into some directory, hereafter referred to as $OSGi_HOME
% After, edit osgi.service and make ExecStart points to your $OSGI_HOME/OSGi.sh
%Finally, get osgi.service and use the command # install -Dm 755 osgi.service
/usr/lib/systemd/system/osgi.service; systemctl enable osgi
Now your OSGi felix instance is starting with your OperationalSystem.
Best Regards
> Felix as a daemon
> -----------------
>
> Key: FELIX-3818
> URL: https://issues.apache.org/jira/browse/FELIX-3818
> Project: Felix
> Issue Type: New Feature
> Components: Installer, Remote Shell
> Environment: Linux, with initscripts and screen applications installed
> Reporter: Marcelo Antonio Marotta
> Labels: features
> Attachments: osgi, osgid, OSGi.service, OSGi.sh
>
>
> I created a script to daemonize a felix instance, being executed in
> background.
> My daemon script is based on linux initscripts and screen.
> After installing this daemon, you would access felix CLI by the command
> 'screen -r OSGi' or if you have installed remote shell for felix, telnet
> localhost 6666.
> Best regards,
> Marotta
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
