GNU Mailman/Mailman Core — Korean @ 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 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.

English

Korean

Needs editing

Skip

Context	English	Korean
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.
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.
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로 인해 종료 할 때 러너를 다시 시작하지 마십시오. ····디버깅에만 사용하십시오.
If the master watcher finds an existing master lock, it will normally exit with an error message. With this option,the master will perform an extra level of checking. If a process matching the host/pid described in the lock file is running, the master will still exit, requiring you to manually clean up the lock. But if no matching process is found, the master will remove the apparently stale lock and make another attempt to claim the master lock.	If the master watcher finds an existing master lock, it will normally exit with an error message. With this option,the master will perform an extra level of checking. If a process matching the host/pid described in the lock file is running, the master will still exit, requiring you to manually clean up the lock. But if no matching process is found, the master will remove the apparently stale lock and make another attempt to claim the master lock.	···마스터 감시자가 존재하는 마스터 잠금을 찾으면, 일반적으로 에러 메세지와 함께 종료됩니다. ···이 옵션을 사용하면 마스터가 추가 작업을 수행합니다. ···잠금 파일에 설명 된 호스트 / pid와 일치하는 프로세스가 실행중인 경우 마스터가 여전히 종료되므로 잠금을 수동으로 정리해야합니다. ···그러나 일치하는 프로세스를 찾지 못하면, 마스터는 오래된 잠금을 제거하고 마스터 잠금을 다시 시도합니다.
Override the default set of runners that the master will invoke, which is typically defined in the configuration file. Multiple -r options may be given. The values for -r are passed straight through to bin/runner.	Override the default set of runners that the master will invoke, which is typically defined in the configuration file. Multiple -r options may be given. The values for -r are passed straight through to bin/runner.	···마스터가 호출할 기본 실행자 세트(일반적으로 구성 파일에 정의됩니다)를 우선합니다. 여러 개의 -r 옵션이 제공 될 수 있습니다. -r의 값은 bin / runner로 바로 전달됩니다.

Context	English	Korean
The gatenews command is run periodically by the nntp runner. If you are running it via cron, you should remove it from the crontab. If you want to run it manually, set _MAILMAN_GATENEWS_NNTP in the environment.	The gatenews command is run periodically by the nntp runner. If you are running it via cron, you should remove it from the crontab. If you want to run it manually, set _MAILMAN_GATENEWS_NNTP in the environment.
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.
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	우체부 Replybot
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.	메시지에 일치하는 승인 또는 승인 헤더가 있습니다.

Loading…

None

String updated in the repository

English

Korean 160 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	Korean
No related strings found in the glossary.

String information

Context

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.

Flags

python-brace-format

Source string location

src/mailman/bin/master.py:194

String age

2 years ago

Last updated

11 months ago

Source string age

2 years ago

Translation file

src/mailman/messages/ko/LC_MESSAGES/mailman.po, string 32