On Fri, Jul 21, 2017 at 03:22:11PM +0000, msuraev [REDMINE] wrote:
Note: we should also make and install .service for it to make sure that it's functional out of the box.
I'm not entirely sure this is what you want for osmo-bts-virtual.
For a physical BTS, of course it is likely that you will want to start
a single instance of the program at system boot time. But for a virtual BTS,
I think the use case is almost always some kind of testing, and you don't
know when the user wants to do that, and how many instances with which configuration
to start.
So if at all, you would probably want to have something similar to the openvpn@
integration, so you could have an entire series of configuration files in some
directory, causing a series of osmo-bts-virtual instances to be started, each with their
own config file - and of course not enable them by default but wait for the user
to decide when he wants to start his BTSs.
