Diego de la Hera

why you want to do that and not just have two regular servers on two separate ports? In other words, why have a central server? Are you planning on registering more regular servers on the central server? We are a choir and we would like to have separate "rooms" (between 2 and 4 servers) to split our rehearsals by voice (bass, tenor, etc). So far we have been using the "solo" option, but separate servers would be better for a number of reasons. We would like to have servers registered on a central...

Hi, Jonathan. I do want two servers running on different port numbers: Primary server (both regular server and central server) on 22124, and Secondary server (regular server only) on 22125 (see above). Only I want them registered to the same central server (Primary server on port 22124).

I have a central server running, listening on default port 22124. Command is Jamulus -s -n -g -e "localhost" -o "Primary;BA;10". Let WANIP be the server's external IP address. Clients can use WANIP as their custom central server: they see the "Primary" server listed there, and they can connect to it. So far, so good. Now, enter a second server running on the same machine. The idea is to have this second instance listen on port 22125, and register on the Primary central server. Command is: Jamulus...

I have a central server running, listening on default port 22124. Command is Jamulus -s -n -g -e "localhost" -o "Primary;BA;10". Let WANIP be the server's external IP address. Clients can use WANIP as their custom central server: they see the "Primary" server listed there, and they can connect to it. So far, so good. Now, enter a second server running on the same machine. The idea is to have this second instance listen on port 22125, and register on the Primary central server. Command is: Jamulus...

Oh, this is amazing, Peter! Thank you very much!!

not a single mention of Jamulus Well, actually they did ;) justify constantly asking for donations Maybe at least this way they can help spread Jamulus ideas in the region and achieve their alleged goal of developing a web version. However, I definitely agree that it would have been fairer and better for the community to contribute to Jamulus rather than forking it. They have also failed to publish the source code for the latest version. They did, here. I think it is unfortunate that this comes from...

I get the jamulus[48780]: /usr/local/bin/Jamulus: Unknown option '&&' -- use '--help' for helperror when I use this ExecStart line: ExecStart=/usr/local/bin/Jamulus -s -n -g -u 20 -e 'localhost' -o 'UTDT;Buenos Aires;10' -R /tmp/jamulus && /bin/systemctl kill -s SIGUSR2 jamulus I get similar results if I use & or ; instead of &&; or if I use /usr/bin/kill -s SIGUSR2 $! as the second command. In all cases it complains as if I were providing extra arguments to Jamulus. Alternatively, I used this ExecStart...

Thanks, Gilgongo. I thought && would wait until the first process exits to run the second process. I tried it anyway, but it failed. Either with &, && or ; it fails because it seems to interpret the second command as an argument to the first command: jamulus[48780]: - server mode chosen jamulus[48780]: - no GUI mode chosen ... jamulus[48780]: /usr/local/bin/Jamulus: Unknown option '&&' -- use '--help' for help systemd[1]: jamulus.service: Main process exited, code=exited, status=1/FAILURE systemd[1]:...