Lines Matching refs:which
4 Xenstore implements a database which maps filename-like pathnames
19 A separate specification will detail the keys and values which are
26 We can speak of two paths being <child> and <parent>, which is the
35 to store nonempty values at nodes which also have children.
64 xenstored, which is usually catastrophic from the client's point of
65 view. Clients (particularly domains, which cannot just reconnect)
84 <foo|> Binary data (which may contain zero or more nul bytes)
114 <path> is allowed not to start with /, in which case the
183 events which are invented by xenstored:
197 on being sent a watch when a path which it _is_ able to read
200 are changed so as to make it unreadable, in which case future
211 <wpath> (rather than the actual path which was removed). So
243 which changed paths which were read or written in the
259 decimal), on which xenstored will call bind_interdomain.