|
51.
|
|
|

The mount command mounts the given source onto the given destination path, 
provided that the snap has a plug for the mount-control interface which allows 
this operation.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
overlord/hookstate/ctlcmd/mount.go:39
|
|
52.
|
|
|
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
cmd/snap/cmd_warnings.go:60
|
|
53.
|
|
|

The pack command packs the given snap-dir as a snap and writes the result to 
target-dir. If target-dir is omitted, the result is written to current 
directory. If both source-dir and target-dir are omitted, the pack command packs 
the current directory.

The default file name for a snap can be derived entirely from its snap.yaml, but 
in some situations it's simpler for a script to feed the filename in. In those 
cases, --filename can be given to override the default. If this filename is 
not absolute it will be taken as relative to target-dir.

When used with --check-skeleton, pack only checks whether snap-dir contains 
valid snap metadata and raises an error otherwise. Application commands listed 
in snap metadata file, but appearing with incorrect permission bits result in an 
error. Commands that are missing from snap-dir are listed in diagnostic 
messages.

When used with --append-integrity-data, pack will append dm-verity data at the end 
of the snap to be used with snapd's snap integrity verification mechanism.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
cmd/snap/cmd_pack.go:49
|
|
58.
|
|
|

The publisher of snap %q has indicated that they do not consider this revision 
to be of production quality and that it is only meant for development or testing 
at this point. As a consequence this snap will not refresh automatically and may 
perform arbitrary system changes outside of the security sandbox snaps are 
generally confined to, which may put your system at risk.

If you understand and want to proceed repeat the command including --devmode; 
if instead you want to install the snap forcing it into strict confinement 
repeat the command including --jailmode.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
cmd/snap/error.go:181
|
|
59.
|
|
|

The quota command shows information about a quota group, including the set of 
snaps and any sub-groups it contains, as well as its resource constraints and 
the current usage of those constrained resources.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
cmd/snap/cmd_quota.go:39
|
|
60.
|
|
|

The quotas command shows all quota groups.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
cmd/snap/cmd_quota.go:46
|
|
61.
|
|
|
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
overlord/hookstate/ctlcmd/reboot.go:31
|
|
62.
|
|
|
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
cmd/snap/cmd_reboot.go:43
|
|
64.
|
|
|

The refresh command prints pending refreshes of the calling snap and can hold 
back disruptive refreshes of other snaps, such as refreshes of the kernel or 
base snaps that can trigger a restart. This command can be used from the 
gate-auto-refresh hook which is only run during auto-refresh.

Snap can query pending refreshes with:
$ snapctl refresh --pending
pending: ready
channel: stable
version: 2
revision: 2
base: false
restart: false

The 'pending' flag can be "ready", "none" or "inhibited". It is set to "none" 
when a snap has no pending refreshes. It is set to "ready" when there are 
pending refreshes and to ”inhibited” when pending refreshes are being 
held back because more or more snap applications are running with the 
“refresh app awareness” feature enabled.

The "base" and "restart" flags indicate whether the base snap is going to be 
updated and/or if a restart will occur, both of which are disruptive. A base 
snap update can temporarily disrupt the starting of applications or hooks from 
the snap.

To tell snapd to proceed with pending refreshes:
$ snapctl refresh --pending --proceed

Note, a snap using --proceed cannot assume that the updates will occur as they 
might be held back by other snaps.

To hold refresh for up to 90 days for the calling snap:
$ snapctl refresh --pending --hold
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
overlord/hookstate/ctlcmd/refresh.go:56
|
|
65.
|
|
|
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
cmd/snap/cmd_snap_op.go:88
|