gnunet-uri.1 1.4 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849
  1. .TH GNUNET-URI 1 "June 26, 2012" "GNUnet"
  2. .SH NAME
  3. gnunet\-uri \- invoke default handler for GNUnet URIs
  4. .SH SYNOPSIS
  5. .B gnunet\-uri
  6. .RI URI
  7. .SH DESCRIPTION
  8. \fBgnunet\-uri\fP can be used to invoke the correct tool to handle a
  9. GNUnet URI. GNUnet URIs have the format "gnunet://SUBSYSTEM/DETAILS"
  10. and thus the specific tool to handle the URI depends on the subsystem.
  11. gnunet\-uri will determine the correct tool (by looking for SUBSYSTEM
  12. in the configuration section "uri") and invoke it.
  13. .SH OPTIONS
  14. .B
  15. .IP "\-c FILENAME, \-\-config=FILENAME"
  16. Use the configuration file FILENAME.
  17. .B
  18. .IP "\-h, \-\-help"
  19. Print short help on options.
  20. .B
  21. .IP "\-L LOGLEVEL, \-\-loglevel=LOGLEVEL"
  22. Use LOGLEVEL for logging. Valid values are DEBUG, INFO, WARNING and ERROR.
  23. .B
  24. .IP "\-v, \-\-version"
  25. Print GNUnet version number.
  26. .SH BUGS
  27. Report bugs by using Mantis <https://bugs.gnunet.org/> or by sending
  28. electronic mail to <gnunet\-developers@gnu.org>
  29. .SH SEE ALSO
  30. The full documentation for
  31. .B gnunet
  32. is maintained as a Texinfo manual.
  33. If the
  34. .B info
  35. and
  36. .B gnunet
  37. programs are properly installed at your site, the command
  38. .IP
  39. .B info gnunet
  40. .PP
  41. should give you access to the complete handbook,
  42. .IP
  43. .B info gnunet-c-tutorial
  44. .PP
  45. will give you access to a tutorial for developers.
  46. .PP
  47. Depending on your installation, this information is also
  48. available in
  49. \fBgnunet\fP(7) and \fBgnunet-c-tutorial\fP(7).