Vegar Westerlund wrote:
Richard S. Hall:
Felix itself doesn't make any attempt to use stdin, but the simple
launcher does (i.e., it assumes it can ask for a profile if one doesn't
exist and is configured to autoload the shell.tui), but it is
configurable to avoid doing these things.
«the simple laucher does...»? Is felix normally run from another
application (like I guess it is when running Eclipse)? I would like to
run Felix on a server to be a backend for business logic. And then I
only want to start the Felix server.
Well, we didn't expect there to be a single launcher that worked for
everyone, so we figured people might create their own launchers or embed
Felix into their own applications, see:
http://cwiki.apache.org/FELIX/launching-and-embedding-apache-felix.html
How would you like it to be cleaner? Do you mean having it set up as a
daemon automatically?
Most programs designed to run as a daemon will ensure that stdout and
stderr are redirected to syslog (or a logfile) and stdout are closed
before forking a process to run in the background. And possibly a debug
mode where the console are kept as output. Thats what I was expecting,
but didn't find.
Well, for the most part, Felix uses the log service if a bundle is
installed that provides one, then you can control where the log messages
go via which log service you install.
We have some work started on an installer that will automatically
install Felix as a daemon, but unfortunately that has stalled.
Yeah, I read about something in the archive from November 07 about using
Java wrapper. I tried it out and it seems to work on our Linux server.
Cool. Well, it would be nice if we could find a volunteer to polish this
up. I created an issue for it on our "contributing" page:
http://cwiki.apache.org/FELIX/contributing.html
:-)
-> richard
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
