1
0

execnet 1.0 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667
  1. .TH EXECNET 4
  2. .SH NAME
  3. execnet \- network interface to program execution
  4. .SH SYNOPSIS
  5. .B execnet
  6. [
  7. .B -n
  8. .I name
  9. ]
  10. [
  11. .B netdir
  12. ]
  13. .SH DESCRIPTION
  14. .I Execnet
  15. presents a network protocol directory
  16. (see, for example,
  17. .IR ip (3))
  18. called
  19. .IB netdir / name
  20. (default
  21. .BR /net/exec ).
  22. .PP
  23. Once the protocol directory exists, dialing
  24. (see
  25. .IR dial (2))
  26. strings of
  27. the form
  28. .IB name ! cmd
  29. will connect to a newly executed instance of
  30. .IR cmd .
  31. .SH EXAMPLE
  32. .I Execnet
  33. can be used to connect to instances of
  34. .IR u9fs (4)
  35. running on other hosts:
  36. .EX
  37. g% execnet
  38. g% srv -m 'exec!ssh ny start-u9fs' ny /n/ny
  39. .EE
  40. This example assumes that the remote command
  41. .B start-u9fs
  42. executed on
  43. .B ny
  44. will start
  45. .I u9fs
  46. appropriately.
  47. For example, it might be:
  48. .EX
  49. ny% cat start-u9fs
  50. #!/bin/sh
  51. u9fs -na none -u $USER -l $HOME/tmp/u9fs.log
  52. ny%
  53. .EE
  54. See the
  55. .IR u9fs (4)
  56. man page for more information.
  57. .SH SOURCE
  58. .B /sys/src/cmd/execnet
  59. .SH "SEE ALSO
  60. .IR dial (2),
  61. .IR ip (3),
  62. .IR u9fs (4)
  63. .SH BUGS
  64. Almost certainly:
  65. .IR execnet
  66. has only been tested as in the example shown.