Serviio

Doesn't make much sense.
1) You can stop the server from the console, so obviously the console can run when the server isn't running, so why can't the console be started when the server isn't running.
2) Starting the console and then starting the server from the console would be convenient, but now it's impossible for some design reason that eludes me.

YOu have to differentiate between UPnP server (one of Serviio's components) and Serviio server / service (the process itself). The console text clearly says that clicking on Start/Stop buttons only operates the UPnP server, i.e. manages visibility of the server on the network.


It's a standard client-server architecture. Console is just a thin client that doesn't implement any business logic, but only invokes the server's operations remotely. That's why the server must be started first.

That being the case, I would just as soon have a robust standard linux script for /etc/init.d that would start the service without my intervention, and could happily ignore the superfluous console.

you can do that (some on the forum poster theirs), you only need the console for setting shared folders up etc, it's not necessary for streaming.

I haven't found documentation. "start" and "stop" seem to work as arguments to the class. That's something, anyway.

I guess Unix and Linux users are spoiled, and expect too much compared to people that aren't used to such luxuries.

"help" does not work as an argument. It is expected with all software on Unix or Linux.

If the there is no documentation or users don't know where to find it, and "help" doesn't work as an argument, consequently one doesn't know which arguments will work.

That makes for software which is barely usable.

Just to be clear:

If a program accepts arguments, at the very least it should print a usage statement if the argument is missing or garbled.

Acceptance of "help" as an argument is also very much appreciated.

fill in a ticket on bitbucket.org