mirror of
https://github.com/xen-project/xen.git
synced 2026-10-28 18:21:39 +01:00
Juergen Gross
c65687ed16
The Xenstore access commands (xenstore-*) have the possibility to limit connection to Xenstore to a local socket (option "-s"). This is an option making no sense at all, as either there is only a socket, so the option would be a nop, or there is no socket at all (in case Xenstore is running in a stubdom or the client is called in a domU), so specifying the option would just lead to failure. So drop that option completely. Signed-off-by: Juergen Gross <jgross@suse.com> Acked-by: Wei Liu <wl@xen.org>
59 lines
1010 B
INI
59 lines
1010 B
INI
=head1 NAME
|
|
|
|
xenstore-chmod - set the permissions of a Xenstore key
|
|
|
|
=head1 SYNOPSIS
|
|
|
|
B<xenstore-chmod> [I<OPTION>]... [I<KEY>] [I<PERM>]...
|
|
|
|
=head1 DESCRIPTION
|
|
|
|
Sets the permissions of the Xenstore I<KEY>.
|
|
|
|
I<PERM> has the format I<LD>, where I<L> is a letter for the type of
|
|
permission and I<D> is the corresponding domain ID.
|
|
|
|
The types of permission are:
|
|
|
|
=over
|
|
|
|
=item B<r>
|
|
|
|
read
|
|
|
|
=item B<w>
|
|
|
|
write
|
|
|
|
=item B<b>
|
|
|
|
read and write (both)
|
|
|
|
=item B<n>
|
|
|
|
no access
|
|
|
|
=back
|
|
|
|
The first permission entry is the domain owning the key (the owner)
|
|
I<and> the permissions for any domain not explicitly listed in
|
|
subsequent entries. The key owner always has full access (read,
|
|
write, and set permissions).
|
|
|
|
=over
|
|
|
|
=item B<-r>
|
|
|
|
Apply the permissions to the key and all its I<children>.
|
|
|
|
=item B<-u>
|
|
|
|
Apply the permissions to the key and all its I<parents>.
|
|
|
|
=back
|
|
|
|
=head1 BUGS
|
|
|
|
Send bugs to xen-devel@lists.xenproject.org, see
|
|
https://wiki.xenproject.org/wiki/Reporting_Bugs_against_Xen_Project on how to send bug reports.
|