1
0

users 1.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475
  1. .TH USERS 6
  2. .SH NAME
  3. users \- file server user list format
  4. .SH DESCRIPTION
  5. The permanent file servers each maintain a private list of users
  6. and groups, in
  7. .B /adm/users
  8. by convention.
  9. Each line in the file has the format
  10. .IP
  11. .IB id : name : leader :\fImembers\fP
  12. .PP
  13. where
  14. .I name
  15. and
  16. .I leader
  17. are printable strings excluding the characters
  18. .LR ? ,
  19. .LR = ,
  20. .LR + ,
  21. .LR - ,
  22. .LR / ,
  23. and
  24. .LR : ,
  25. and
  26. .I members
  27. is a comma-separated list of such strings.
  28. Such a line defines a user and a group with the given
  29. .IR name ;
  30. the group has a group leader given by
  31. .I leader
  32. and group members given by the user names in
  33. .IR members .
  34. The
  35. .I leader
  36. field may be empty,
  37. in which case any group member is a group leader.
  38. The
  39. .I members
  40. field may be empty.
  41. .PP
  42. Lines beginning with
  43. .L #
  44. are ignored.
  45. .PP
  46. The
  47. .I id
  48. in a line is an identifier used in the on-disk structures maintained
  49. by a file server; there should be no duplicate
  50. .IR id s
  51. in the file.
  52. In
  53. .IR fossil (4),
  54. .IR id s
  55. are arbitrary text strings, typically the same as
  56. .IR name .
  57. In older Plan 9 file servers,
  58. .IR id s
  59. are small decimal numbers.
  60. In those,
  61. a negative
  62. .I id
  63. is special: a user with a negative
  64. .I id
  65. cannot attach to the file server.
  66. The file
  67. .B /adm/users
  68. itself is owned by user
  69. .I adm
  70. and write protected to others,
  71. so it can only be changed via console commands.
  72. .SH "SEE ALSO"
  73. .IR intro (5),
  74. .IR stat (5),
  75. .IR fossilcons (8)