Browsing Afrikaans translation

Don't show this notice anymore
Before translating, be sure to go through Ubuntu Translators instructions and Afrikaans guidelines.

These translations are shared with snapd in Ubuntu Mantic template snappy.

8695 of 925 results
86.

The set-quota command updates or creates a quota group with the specified set of
snaps.

A quota group sets resource limits on the set of snaps or snap services it contains.
Snaps can be at most in one quota group but quota groups can be nested. Nested quota
groups are subject to the restriction that the total sum of each existing quota
in sub-groups cannot exceed that of the parent group the nested groups are part of.

All provided snaps are appended to the group; to remove a snap from a
quota group, the entire group must be removed with remove-quota and recreated
without the snap. To remove a sub-group from the quota group, the
sub-group must be removed directly with the remove-quota command.

To set limits on individual services, one or more services can be placed into a
sub-group. The respective snap for each service must belong to the sub-group's
parent group. These sub-groups will have the same limitations as nested groups
which means their combined resource usage cannot exceed the resource limits set
for the parent group. Sub-groups which contain services cannot have their own
journal quotas set, and instead automatically inherit any journal quota their
parent quota group may have.

The memory limit for a quota group can be increased but not decreased. To
decrease the memory limit for a quota group, the entire group must be removed
with the remove-quota command and recreated with a lower limit. Increasing the
memory limit for a quota group does not restart any services associated with
snaps in the quota group.

The CPU limit for a quota group can be both increased and decreased after being
set on a quota group. The CPU limit can be specified as a single percentage which
means that the quota group is allowed an overall percentage of the CPU resources. Setting
it to 50% means that the quota group is allowed to use up to 50% of all CPU cores
in the allowed CPU set. Setting the percentage to 2x100% means that the quota group
is allowed up to 100% on two cpu cores.

The CPU set limit for a quota group can be modified to include new cpus, or to remove
existing cpus from the quota already set.

The threads limit for a quota group can be increased but not decreased. To
decrease the threads limit for a quota group, the entire group must be removed
with the remove-quota command and recreated with a lower limit.

The journal limits can be increased and decreased after being set on a group.
Setting a journal limit will cause the snaps in the group to be put into the same
journal namespace. This will affect the behaviour of the log command.

New quotas can be set on existing quota groups, but existing quotas cannot be removed
from a quota group, without removing and recreating the entire group.

Adding new snaps to a quota group will result in all non-disabled services in
that snap being restarted.

An existing sub group cannot be moved from one parent to another.
There are line breaks here. Each one represents a line break. Start a new line in the equivalent position in the translation.
There are leading/trailing spaces here. Each one represents a space character. Enter a space in the equivalent position in the translation.

The set-quota command updates or creates a quota group with the specified set of
snaps.

A quota group sets resource limits on the set of snaps or snap services it contains.
Snaps can be at most in one quota group but quota groups can be nested. Nested quota
groups are subject to the restriction that the total sum of each existing quota
in sub-groups cannot exceed that of the parent group the nested groups are part of.

All provided snaps are appended to the group; to remove a snap from a
quota group, the entire group must be removed with remove-quota and recreated
without the snap. To remove a sub-group from the quota group, the
sub-group must be removed directly with the remove-quota command.

To set limits on individual services, one or more services can be placed into a
sub-group. The respective snap for each service must belong to the sub-group's
parent group. These sub-groups will have the same limitations as nested groups
which means their combined resource usage cannot exceed the resource limits set
for the parent group. Sub-groups which contain services cannot have their own
journal quotas set, and instead automatically inherit any journal quota their
parent quota group may have.

The memory limit for a quota group can be increased but not decreased. To
decrease the memory limit for a quota group, the entire group must be removed
with the remove-quota command and recreated with a lower limit. Increasing the
memory limit for a quota group does not restart any services associated with
snaps in the quota group.

The CPU limit for a quota group can be both increased and decreased after being
set on a quota group. The CPU limit can be specified as a single percentage which
means that the quota group is allowed an overall percentage of the CPU resources. Setting
it to 50% means that the quota group is allowed to use up to 50% of all CPU cores
in the allowed CPU set. Setting the percentage to 2x100% means that the quota group
is allowed up to 100% on two cpu cores.

The CPU set limit for a quota group can be modified to include new cpus, or to remove
existing cpus from the quota already set.

The threads limit for a quota group can be increased but not decreased. To
decrease the threads limit for a quota group, the entire group must be removed
with the remove-quota command and recreated with a lower limit.

The journal limits can be increased and decreased after being set on a group.
Setting a journal limit will cause the snaps in the group to be put into the same
journal namespace. This will affect the behaviour of the log command.

New quotas can be set on existing quota groups, but existing quotas cannot be removed
from a quota group, without removing and recreating the entire group.

Adding new snaps to a quota group will result in all non-disabled services in
that snap being restarted.

An existing sub group cannot be moved from one parent to another.
Translated and reviewed by Bernard Stafford
Located in cmd/snap/cmd_quota.go:60
87.

The sign command signs an assertion using the specified key, using the
input for headers from a JSON mapping provided through stdin. The body
of the assertion can be specified through a "body" pseudo-header.
There are line breaks here. Each one represents a line break. Start a new line in the equivalent position in the translation.

Die teken bevel tekens 'n bewering met behulp van die gespesifiseerde sleutel, gebruik die
insette vir kop-er vanaf 'n JSON mapping voorsien deur middel stdin. Die liggaam
van die bewering kan gespesifiseer word deur middel 'n "body" pseudo-kop.
Translated and reviewed by Bernard Stafford
Located in cmd/snap/cmd_sign.go:35
88.

The sign-build command creates a snap-build assertion for the provided
snap file.
There are line breaks here. Each one represents a line break. Start a new line in the equivalent position in the translation.

Die teken-build bevel skep 'n snap-bou bewering vir die voorsien
snap lêer.
Translated and reviewed by Bernard Stafford
Located in cmd/snap/cmd_sign_build.go:49
89.

The snap command lets you install, configure, refresh and remove snaps.
Snaps are packages that work across many different Linux distributions,
enabling secure delivery and operation of the latest apps and utilities.
There are line breaks here. Each one represents a line break. Start a new line in the equivalent position in the translation.

Met die snap bevel kan jy installeer, instel, verfris en verwyder snaps.
Snaps is pakkette wat werk oor baie verskillende Linux verspreidings,
wat veilige aflewering en bedryf van die nuutste apps en hulpprogramme moontlik maak.
Translated and reviewed by Bernard Stafford
Located in cmd/snap/cmd_help.go:277
90.

The start command starts the given services of the snap. If executed from the
"configure" hook, the services will be started after the hook finishes.
There are line breaks here. Each one represents a line break. Start a new line in the equivalent position in the translation.

Die begin bevel begins die gegee dienste van die snap. As executed vanaf die
"configure" haak, die dienste sal begin word nadat die haak klaar is.
Translated and reviewed by Bernard Stafford
Located in overlord/hookstate/ctlcmd/start.go:30
91.

The start command starts, and optionally enables, the given services.
There are line breaks here. Each one represents a line break. Start a new line in the equivalent position in the translation.

Die begin opdrag begin, en opsioneel in staat te stel, die gegewe dienste.
Translated and reviewed by Bernard Stafford
Located in cmd/snap/cmd_services.go:63
92.

The stop command stops the given services of the snap. If executed from the
"configure" hook, the services will be stopped after the hook finishes.
There are line breaks here. Each one represents a line break. Start a new line in the equivalent position in the translation.

Die stop bevel stop die gegewe dienste van die snap. As executed vanaf die
"configure" haak, die dienste sal wees gestop nadat die haak afwerkings.
Translated and reviewed by Bernard Stafford
Located in overlord/hookstate/ctlcmd/stop.go:38
93.

The stop command stops, and optionally disables, the given services.
There are line breaks here. Each one represents a line break. Start a new line in the equivalent position in the translation.

Die stopopdrag stop, en deaktiveer opsioneel, die gegewe dienste.
Translated and reviewed by Bernard Stafford
Located in cmd/snap/cmd_services.go:67
94.

The switch command switches the given snap to a different channel without
doing a refresh. All available channels of a snap are listed in
its 'snap info' output.
There are line breaks here. Each one represents a line break. Start a new line in the equivalent position in the translation.

Die skakelopdrag skakel die gegewe snap na 'n ander kanaal sonder
doen 'n verfris. Alle beskikbare kanale van 'n snap is gelys in
its 'snap info' uitset.
Translated and reviewed by Bernard Stafford
Located in cmd/snap/cmd_snap_op.go:1190
95.

The system-mode command returns information about the device's current system mode.

This information includes the mode itself and whether the model snaps have been installed from the seed (seed-loaded). The system mode is either run, recover, or install.

Retrieved information can also include "factory mode" details: 'factory: true' declares whether the device booted an image flagged as for factory use. This flag can be set for convenience when building the image. No security sensitive decisions should be based on this bit alone.

The output is in YAML format. Example output:
$ snapctl system-mode
system-mode: install
seed-loaded: true
factory: true
There are line breaks here. Each one represents a line break. Start a new line in the equivalent position in the translation.
There are leading/trailing spaces here. Each one represents a space character. Enter a space in the equivalent position in the translation.

Die stelsel-modus opdrag gee inligting terug oor die toestel se huidige stelselmodus.

Hierdie inligting sluit die modus self in en of die model snaps het geweesuit die saad geïnstalleer (saad-gelaai). Die stelselmodus is óf hardloop, herstel óf installeer.

Opgespoorde inligting kan ook insluit "factory mode" besonderhede: 'factory: true' verklaar of die toestel 'n prent gelaai het wat as vir fabrieksgebruik gevlag is. Hierdie vlag kan gerieflikheidshalwe gestel word wanneer die beeld gebou word. Geen sekuriteitsensitiewe besluite moet op hierdie bietjie alleen gebaseer word nie.

Die uitset is in YAML formaat. Voorbeeld uitset:
$ snapctl system-mode
system-mode: install
seed-loaded: true
factory: true
Translated and reviewed by Bernard Stafford
Located in overlord/hookstate/ctlcmd/system_mode.go:36
8695 of 925 results

This translation is managed by Ubuntu Afrikaans Translators, assigned by Ubuntu Translators.

You are not logged in. Please log in to work on translations.

Contributors to this translation: Bernard Stafford, Jurgens J Schoeman.