GNU Mailman

Mailman Core

Chinese (Simplified)

Translate

Zen

Translation

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

English

Chinese (Simplified)

Needs editing

Sign in to save the translation.

Skip

	Context	English	Chinese (Simplified)	Actions
	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.	你需要确认离开 ${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.	你需要确认加入 ${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.	要使用的配置文件。如果没有给定，会查找是否设置了 MAILMAN_CONFIG_FILE 环境变量并使用。如果都没有，加载默认配置文件。
	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.	不建议以 root 身份运行 mailman 命令，而且 mailman 将拒绝以 root 运行除非此选项被指定。
	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.	如果你确定要以 root 身份运行，请指定 --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.	无法获取主程序锁因为另外一个主程序已经在运行。
	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.	无法获取主程序锁。似乎有一个过时的主程序锁。可以尝试用 --force 选项重新运行 ${program}。
	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.	无法获取主程序锁，因为似乎其他主机上的某个进程可能已获取了主程序锁。我们无法跨主机边界测试过时的锁定，因此你必须手动清理。锁定的文件：${config.LOCK_FILE} 锁定的主机：${hostname} 正在退出。
	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.	由于某些未知原因，无法获取主程序锁。锁定的文件：${config.LOCK_FILE} 锁定的主机：${hostname} 正在退出。
	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.	主程序子进程监视器。启动并监视配置的运行器，确保它们持续运作。每个运行器都是复制进程并依次执行，主程序则等待它们的进程 ID。当检测子运行器退出时，主程序会重新启动它。运行器会对 SIGINT、SIGTERM、SIGUSR1 和 SIGHUP 做出响应。SIGINT、SIGTERM 和 SIGUSR1 都会使运行器彻底退出。主程序将重新启动由 SIGUSR1 或其他退出条件（例如未捕获的异常）而退出的运行器。 SIGHUP 导致主程序和运行器关闭它们的日志文件，然后在下一条消息打印时重新打开。主程序也会响应 SIGINT、SIGTERM、SIGUSR1 和 SIGHUP，但只是将简单地传递信号给运行器。注意主程序在收到 SIGHUP 后将关闭并重新打开它自己的日志文件。主程序也会按照配置文件指定的文件留下它自己的进程 ID，但你通常不需要直接使用这个 PID。
	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.	当运行器由于错误或 SIGUSR1 而退出时，不重新启动它们。仅将此用于调试。

	Context	English	Chinese (Simplified)	Actions
	The {} list has {} moderation requests waiting.	The {} list has {} moderation requests waiting.	{} 列表中有 {} 个等待审核的请求。
	The list to operate on. Required unless --fromall is specified.	The list to operate on. Required unless --fromall is specified.	要操作的列表。除非指定 --fromall，否则为必需参数。
	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	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.	无法获取主程序锁，因为似乎其他主机上的某个进程可能已获取了主程序锁。我们无法跨主机边界测试过时的锁定，因此你必须手动清理。锁定的文件：${config.LOCK_FILE} 锁定的主机：${hostname} 正在退出。
	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.	无法获取主程序锁因为另外一个主程序已经在运行。
	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.	无法获取主程序锁。似乎有一个过时的主程序锁。可以尝试用 --force 选项重新运行 ${program}。
	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.	该消息有匹配的 Approve 或 Approved 首部。
	The message has no valid senders	The message has no valid senders	该消息没有有效的发件人

Loading…

wsxy162 Translation uploaded GNU Mailman Mailman Core Chinese (Simplified)	English The master lock could not be acquired because it appears as though another master is already running. Chinese (Simplified) 5 characters edited Current translation 无法获取主机程序锁因为另外一个主机主程序已经在运行。 2 years ago
AK88_ Translation changed GNU Mailman Mailman Core Chinese (Simplified)	English The master lock could not be acquired because it appears as though another master is already running. Chinese (Simplified) 1 character edited 无法获取主机锁因为另外一个主机已经在运行。 3 years ago
AK88_ Translation changed GNU Mailman Mailman Core Chinese (Simplified)	English The master lock could not be acquired because it appears as though another master is already running. Chinese (Simplified) 1 character edited 无法获取主机锁因为另外一个主机已经在运行 3 years ago
AK88_ Translation added GNU Mailman Mailman Core Chinese (Simplified)	English The master lock could not be acquired because it appears as though another master is already running. Chinese (Simplified) 20 characters edited 无法获取主机锁因为另外一个主机已经在运行 3 years ago

Browse all string changes

Things to check

Mismatching line breaks

Number of new lines in translation does not match source

Glossary

English	Chinese (Simplified)
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

3 years ago

Last updated

11 months ago

Source string age

4 years ago

Translation file

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