SERVER.txt 1.9 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243
  1. By default, the jamulus binary can function as:
  2. - Client with GUI (default mode, X and jackd must be running)
  3. - Server with GUI (-s option, only X must be running)
  4. - Headless server (-s and -n options, neither X nor jackd required)
  5. Even though the headless mode doesn't require a running X server,
  6. it still requires the Qt5 shared libraries. There's no way to compile
  7. jamulus without these.
  8. You can launch jamulus as either a client or a server with GUI from
  9. the desktop start menu. If you want to run a headless server, you'll
  10. have to either run it from the command line, or create a different
  11. launcher/shortcut for jamulus as a headless server (with -n option).
  12. If you want to run a headless server that starts at boot time (like
  13. a regular daemon), currently the best way to do this is to call it
  14. from /etc/rc.d/rc.local. There's no "daemon" option, so you'll have to
  15. background it with &, and redirect stdout/stderr somewhere (see also
  16. the -l <logfile> option).
  17. Dedicated server only build
  18. ----------------------------
  19. If you *really* want to build a dedicated jamulus server, you can do so
  20. by setting SERVERONLY=yes in the SlackBuild's environment. In this case,
  21. you can ignore the REQUIRES="jack" line in the .info file.
  22. The resulting jamulus binary will work only as a dedicated server.
  23. It wont't make sound nor accept audio input from your instrument, and
  24. it won't require X11 shared libraries (though it still does require
  25. Qt5 shared libs). It'll only be useful as a server, and it'll have to
  26. be run from the command line, or a shell script (won't show up in your
  27. desktop start menu).
  28. The *only* reason to ever do this is if you really *really* don't want
  29. to install jack for some reason.
  30. For those who want to complain that I shouldn't have listed jack as
  31. required: It *is* required, for the *normal* use case. Building without
  32. JACK support is a very specialized thing, not useful to the general
  33. population of users.