snapd

Browsing Afrikaans translation

  1. Series trunk
  2. Template “snappy”
  3. Afrikaans (af)
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.

83 → 92 of 925 results First • • • Last
83.

The set command changes the provided configuration options as requested.

$ snap set snap-name username=frank password=$PASSWORD

All configuration changes are persisted at once, and only after the
snap's configuration hook returns successfully.

Nested values may be modified via a dotted path:

$ snap set snap-name author.name=frank

Configuration option may be unset with exclamation mark:
$ snap set snap-name author!
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 stel bevel verander die verskaf konfigurasie opsies soos versoek.

$ snap set snap-name username=frank password=$PASSWORD

Alle konfigurasie veranderings word presisted by eens, en slegs na die
snap's konfigurasie haak terugkeer suksesvol.

Geneste waardes mag wees gemodifiseerde via 'n kolletjies pad:

$ snap set snap-name author.name=frank

Konfigurasie opsies mag wees ongestel met uitroepteken:
$ snap set snap-name author!
Translated and reviewed by Bernard Stafford
Located in cmd/snap/cmd_set.go:33
84.

The set command sets the provided configuration options as requested.

$ snapctl set username=frank password=$PASSWORD

All configuration changes are persisted at once, and only after the hook
returns successfully.

Nested values may be modified via a dotted path:

$ snapctl set author.name=frank

Configuration option may be unset with exclamation mark:
$ snapctl set author!

Plug and slot attributes may be set in the respective prepare and connect hooks
by naming the respective plug or slot:

$ snapctl set :myplug path=/dev/ttyS0
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 stel opdrag stel die verskafde konfigurasie opsies soos versoek.

$ snapctl set username=frank password=$PASSWORD

Alle konfigurasieveranderinge word gelyktydig volgehou, en slegs na die haak
terugkeer suksesvol.

Geneste waardes kan verander word via 'n stippelpad:

$ snapctl set author.name=frank

Konfigurasie opsie kan wees unset met uitroepteken:
$ snapctl set author!

Prop en gleuf kenmerke kan in die onderskeie voorbereiding- en koppelhake gestel word
deur die onderskeie prop of gleuf te noem:

$ snapctl set :myplug path=/dev/ttyS0
Translated and reviewed by Bernard Stafford
Located in overlord/hookstate/ctlcmd/set.go:47
85.

The set-health command is called from within a snap to inform the system of the
snap's overall health.

It can be called from any hook, and even from the apps themselves. A snap can
optionally provide a 'check-health' hook to better manage these calls, which is
then called periodically and with increased frequency while the snap is
"unhealthy". Any health regression will issue a warning to the user.

Note: the health is of the snap only, not of the apps it contains; it’s up to
the snap developer to determine how the health of the individual apps is
reflected in the overall health of the snap.

status can be one of:

- okay: the snap is healthy. This status takes no message and no code.

- waiting: a resource needed by the snap (e.g. a device, network, or service) is
not ready and the user will need to wait. The message must explain what
resource is being waited for.

- blocked: something needs doing to unblock the snap (e.g. a service needs to be
configured); the message must be sufficient to point the user in the right
direction.

- error: something is broken; the message must explain what.
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 stel-gesondheid bevel is geroep vanaf binne 'n snap om stelsel van die
snap's algehele gesondheid.

Dit kan wees uit enige haak geroep, en selfs vanaf die apps proself. 'N snap kan
opsioneel verskaf 'n 'check-health' haak om beter hierdie oproepe te bestuur, watter is
dan periodiek genoem en met verhoogde frekwensie terwyl die snap is
"unhealthy". Enige gesondheid regressie sal 'n waarskuwing aan die gebruiker uit te reik.

Let wel: die gesondheid is van die snap- enigste, nie van die apps dit bevat; dit is up om
die ontwikkelaar om vas te stel hoe die gesondheid van die individuele apps is
weerspieël in die algemene gesondheid van die snap.

status kan wees een van:

-okay: die snap is gesond. Hierdie status neem geen boodskap en geen kode nie.

-wag: 'n hulpbron wat benodig word deur die snap (Bv 'n toestel, 'n netwerk, of diens) is
nie gereed nie en die gebruiker sal moet wag. Die boodskap moet verduidelik wat
hulpbron is synde gewag vir.

-geblokkeer: iets nodig doen om ontblokkeer die snap (bv. 'n diens moet om wees
gekonfigureer is); die boodskap moet voldoende wees om die gebruiker te point in die regte wees
rigting.

- fout: iets is gebreek; die boodskap moet verduidelik wat.
Translated and reviewed by Bernard Stafford
Located in overlord/hookstate/ctlcmd/health.go:35
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
83 → 92 of 925 results First • • • Last

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.