Lines Matching refs:of

13 API takes both the role of what
23 records may be dropped in number of drop-in directories as files where they are
29 subset of the Varlink functionality.
33 The API described in this document is based on a simple subset of the
34 mechanisms described by [Varlink](https://varlink.org/). The choice of
49    D-Bus is not suitable, as any such streaming of messages would be considered
50    flooding in D-Bus' logic, and thus possibly result in termination of
52    enumerating potentially large numbers of users and groups, D-Bus is simply
66 queries on behalf of the client, drastically simplifying client
73 make look-ups efficient, and the simple rule of "first successful lookup wins"
81 the various subsystems that want to offer user and group records to the rest of
83 collide with those of other services. Clients are not expected to merge
104    one service instead of all of them in parallel. Note that it is not available
112 Note that these services currently implement a subset of Varlink only. For
156 ## Caching of User Records
203 `userName` parameter is set it specifies the name of the user to search
204 for. Typically, only one of the two parameters are set, depending whether a
207 one exists that matches one of the two parameters but not the other an error of
208 `ConflictingRecordFound` is returned. If neither of the two parameters are set
216 of multiple services on the same socket (which is used by
219 The method call returns one or more user records, depending which type of query is
222 user record lookup should only pass the `privileged` section of user records to
239 about existence or non-existence of a record can be returned nor any user
241 of daemons that provide multiple distinct user/group services over the same
249 suggests. If one of the two is specified all matching memberships are returned,
250 if neither is specified all known memberships of any user and any group are
251 returned. The return value is a pair of user name and group name, where the
252 user is a member of the group. If both arguments are specified the specified
257 member of). As with `GetUserRecord` and `GetGroupRecord` the `service`
258 parameter needs to contain the name of the service being talked to, in order to
259 allow implementation of multiple services within the same IPC socket. In case no
264 Unlike with `GetUserRecord` and `GetGroupRecord` the lists of memberships
269 Note that only the `GetMemberships` call is authoritative about memberships of
271 `memberOf` field of user records and the `members` field of group records to
272 acquire the full list of memberships. The full list can only be determined by
273 `GetMemberships`, and as mentioned requires merging of these lists of all local
274 services. Result of this is that it can be one service that defines a user A,
276 that A is a member of B.