uyuni/docs administration manager-5.0 — Czech @ openSUSE Weblate: Action Chains

Zen

	English	Czech	Actions
	[guimenu]``Hourly:`` Type the minute of each hour.
	For example, [parameter]``15`` runs the action at fifteen minutes past every hour.
	[guimenu]``Daily:`` Select the time of each day.
	For example, [parameter]``01:00`` runs the action at 0100 every day, in the timezone of the {productname} Server.
	[guimenu]``Weekly:`` Select the day of the week and the time of the day, to execute the action every week at the specified time.
	[guimenu]``Monthly:`` Select the day of the month and the time of the day, to execute the action every month at the specified time.
	[guimenu]``Custom Quartz format:`` For more detailed options, enter a custom quartz string.
	For example, to run a recurring action at 0215 every Saturday of every month, enter:
	0 15 2 ? * 7
	OPTIONAL: Toggle the [guimenu]``Test mode`` switch on to run the schedule in test mode.
	For actions of type [parameter]``Custom state``, select the states from the list of available states and click btn:[Save Changes]. This will only save the current state selection and not the schedule.
	In the next pane, drag and drop the selected states to put them in the execution order and click btn:[Confirm].
	Click btn:[Create Schedule] to save, and see the complete list of existing schedules.
	Organization Administrators can set and edit recurring actions for all clients in the organization. Navigate to menu:Home[My Organization > Recurring Actions] to see all recurring actions that apply to the entire organization.
	{productname} Administrators can set and edit recurring actions for all clients in all organizations. Navigate to menu:Admin[Organizations], select the organization to manage, and navigate to the menu:States[Recurring Actions] tab.
	Action Chains	Akční řetězce (řetězce akcí)
	If you need to perform a number of sequential actions on your clients, you can create an action chain to ensure the order is respected.
	By default, most clients execute an action as soon as the command is issued. In some case, actions take a long time, which could mean that actions issued afterwards fail. For example, if you instruct a client to reboot, then issue a second command, the second action could fail because the reboot is still occurring. To ensure that actions occur in the correct order, use action chains.
	For transactional update systems, an action chain is executed inside a single snapshot, until there is a reboot action. This can cause some limitations.
	For more information, see xref:client-configuration:clients-slemicro.adoc[] and xref:client-configuration:clients-opensuseleapmicro.adoc[].	Další informace o importovaných certifikátech najdete na stránce xref:administration:ssl-certs-imported.adoc[].
	For more information, see xref:client-configuration:clients-slemicro.adoc[].	Další informace o monitorování viz xref:administration:monitoring.adoc[].
	You can use action chains on all clients. Action chains can include any number of these actions, in any order:
	menu:System Details[Remote Command]
	menu:System Details[Schedule System Reboot]
	menu:System Details[States > Highstate]
	menu:System Details[Software > Packages > List/Remove]
	menu:System Details[Software > Packages > Install]
	menu:System Details[Software > Packages > Upgrade]
	menu:System Details[Software > Patches]
	menu:System Details[Software > Software Channels]
	menu:System Details[Configuration]

Loading…

None

String added in the repository

English

Czech 28 characters edited Current translation Translated

2 weeks ago

Browse all string changes

Things to check

Consecutive duplicated words

Text contains the same word twice in a row: řetězce

Reset

Glossary

English	Czech
No related strings found in the glossary.

String information

Source string description

type: Title ==

Flags

no-wrap

Source string location

modules/administration/pages/actions.adoc:37

String age

2 weeks ago

Last updated

2 weeks ago

Source string age

2 weeks ago

Translation file

l10n-weblate/administration/cs.po, string 123