GNU Mailman/Mailman Core — Czech @ Hosted Weblate: The master lock could not be acquired because it appears …

Translation

Context The master lock could not be acquired because it appears as though another master is already running.

English

Czech

Needs editing

Skip

Context	English	Czech
Your confirmation is needed to leave the ${event.mlist.fqdn_listname} mailing list.	Your confirmation is needed to leave the ${event.mlist.fqdn_listname} mailing list.	Musíte potvrdit odhlášení odběru mailing-listu ${event.mlist.fqdn_listname}.
Your confirmation is needed to join the ${event.mlist.fqdn_listname} mailing list.	Your confirmation is needed to join the ${event.mlist.fqdn_listname} mailing list.	Musíte potvrdit přihlášení k odběru mailing-listu ${event.mlist.fqdn_listname}.
Configuration file to use. If not given, the environment variable MAILMAN_CONFIG_FILE is consulted and used if set. If neither are given, a default configuration file is loaded.	Configuration file to use. If not given, the environment variable MAILMAN_CONFIG_FILE is consulted and used if set. If neither are given, a default configuration file is loaded.	Který konfigurační soubor se má použít. Pokud není k dispozici, bude využita systémová proměnná MAILMAN_CONFIG_FILE. Pokud není k dispozici ani ta, bude načtena výchozí konfigurace.
Running mailman commands as root is not recommended and mailman will refuse to run as root unless this option is specified.	Running mailman commands as root is not recommended and mailman will refuse to run as root unless this option is specified.	Spouštět příkazy mailman pod root uživatelem je nedoporučeno a pokud nebude specifikováno jinak, mailman odmítne pod root uživatelem nastartovat.
If you are sure you want to run as root, specify --run-as-root.	If you are sure you want to run as root, specify --run-as-root.	Pokud jste si jisti, že má běžet jako root, specifikujte --run-as-root.
The master lock could not be acquired because it appears as though another master is already running.	The master lock could not be acquired because it appears as though another master is already running.	Zámek "master" nemohl být získán, protože to vypadá, že jiný "master" už běží.
The master lock could not be acquired. It appears as though there is a stale master lock. Try re-running ${program} with the --force flag.	The master lock could not be acquired. It appears as though there is a stale master lock. Try re-running ${program} with the --force flag.
The master lock could not be acquired, because it appears as if some process on some other host may have acquired it. We can't test for stale locks across host boundaries, so you'll have to clean this up manually. Lock file: ${config.LOCK_FILE} Lock host: ${hostname} Exiting.	The master lock could not be acquired, because it appears as if some process on some other host may have acquired it. We can't test for stale locks across host boundaries, so you'll have to clean this up manually. Lock file: ${config.LOCK_FILE} Lock host: ${hostname} Exiting.
For unknown reasons, the master lock could not be acquired. Lock file: ${config.LOCK_FILE} Lock host: ${hostname} Exiting.	For unknown reasons, the master lock could not be acquired. Lock file: ${config.LOCK_FILE} Lock host: ${hostname} Exiting.
Master subprocess watcher. Start and watch the configured runners, ensuring that they stay alive and kicking. Each runner is forked and exec'd in turn, with the master waiting on their process ids. When it detects a child runner has exited, it may restart it. The runners respond to SIGINT, SIGTERM, SIGUSR1 and SIGHUP. SIGINT, SIGTERM and SIGUSR1 all cause a runner to exit cleanly. The master will restart runners that have exited due to a SIGUSR1 or some kind of other exit condition (say because of an uncaught exception). SIGHUP causes the master and the runners to close their log files, and reopen then upon the next printed message. The master also responds to SIGINT, SIGTERM, SIGUSR1 and SIGHUP, which it simply passes on to the runners. Note that the master will close and reopen its own log files on receipt of a SIGHUP. The master also leaves its own process id in the file specified in the configuration file but you normally don't need to use this PID directly.	Master subprocess watcher. Start and watch the configured runners, ensuring that they stay alive and kicking. Each runner is forked and exec'd in turn, with the master waiting on their process ids. When it detects a child runner has exited, it may restart it. The runners respond to SIGINT, SIGTERM, SIGUSR1 and SIGHUP. SIGINT, SIGTERM and SIGUSR1 all cause a runner to exit cleanly. The master will restart runners that have exited due to a SIGUSR1 or some kind of other exit condition (say because of an uncaught exception). SIGHUP causes the master and the runners to close their log files, and reopen then upon the next printed message. The master also responds to SIGINT, SIGTERM, SIGUSR1 and SIGHUP, which it simply passes on to the runners. Note that the master will close and reopen its own log files on receipt of a SIGHUP. The master also leaves its own process id in the file specified in the configuration file but you normally don't need to use this PID directly.
Don't restart the runners when they exit because of an error or a SIGUSR1. Use this only for debugging.	Don't restart the runners when they exit because of an error or a SIGUSR1. Use this only for debugging.

Context	English	Czech
The {} list has {} moderation requests waiting.	The {} list has {} moderation requests waiting.	Mailing-list {} má {} čekajících požadavků na moderování.
The list to operate on. Required unless --fromall is specified.	The list to operate on. Required unless --fromall is specified.
The mailing list is in emergency hold and this message was not pre-approved by the list administrator.	The mailing list is in emergency hold and this message was not pre-approved by the list administrator.
The Mailman Replybot	The Mailman Replybot	Bot pro autoodpovědi Mailman
The master lock could not be acquired, because it appears as if some process on some other host may have acquired it. We can't test for stale locks across host boundaries, so you'll have to clean this up manually. Lock file: ${config.LOCK_FILE} Lock host: ${hostname} Exiting.	The master lock could not be acquired, because it appears as if some process on some other host may have acquired it. We can't test for stale locks across host boundaries, so you'll have to clean this up manually. Lock file: ${config.LOCK_FILE} Lock host: ${hostname} Exiting.
The master lock could not be acquired because it appears as though another master is already running.	The master lock could not be acquired because it appears as though another master is already running.	Zámek "master" nemohl být získán, protože to vypadá, že jiný "master" už běží.
The master lock could not be acquired. It appears as though there is a stale master lock. Try re-running ${program} with the --force flag.	The master lock could not be acquired. It appears as though there is a stale master lock. Try re-running ${program} with the --force flag.
The message comes from a moderated member	The message comes from a moderated member
The message has a matching Approve or Approved header.	The message has a matching Approve or Approved header.	Tato zpráva má odpovídající Approve nebo Approved-Header.
The message has no valid senders	The message has no valid senders	Zpráva nemá žádné platné odesílatele

Loading…

sonscr

Translation added

English

Czech 78 characters edited Current translation Translated

a year ago

smachat

Translation changed

English

Czech 78 characters edited Empty

2 years ago

smachat

Translation added

English

Czech 78 characters edited Current translation Translated

2 years ago

Browse all string changes

Things to check

Mismatching line breaks

Number of new lines in translation does not match source

Reset

Glossary

English	Czech
No related strings found in the glossary.

String information

Context

The master lock could not be acquired because it appears as though another
master is already running.

Source string location

src/mailman/bin/master.py:182

String age

2 years ago

Last updated

11 months ago

Source string age

4 years ago

Translation file

src/mailman/messages/cs/LC_MESSAGES/mailman.po, string 30