[l10n-russian CVS] l10n/resolvconf debian_po_ru.po, NONE,
1.1 interface-order.5, NONE, 1.1 mans.pot, NONE,
1.1 mans_ru.po, NONE, 1.1 po4a.conf, NONE, 1.1 resolvconf.8,
NONE, 1.1 translator_russian.add, NONE, 1.1
Yuri Kozlov
yuray-guest at alioth.debian.org
Sun Jan 29 11:21:13 UTC 2006
Update of /cvsroot/l10n-russian/l10n/resolvconf
In directory haydn:/tmp/cvs-serv22064
Added Files:
debian_po_ru.po interface-order.5 mans.pot mans_ru.po
po4a.conf resolvconf.8 translator_russian.add
Log Message:
Adding new package
--- NEW FILE: interface-order.5 ---
.TH INTERFACE\-ORDER "5" "3 June 2004" "resolvconf" "resolvconf"
.SH NAME
interface-order \- resolvconf configuration file
.SH DESCRIPTION
The file
.I /etc/resolvconf/interface-order
is used to control the order
in which
resolvconf nameserver information records
are processed
by those resolvconf update scripts
that consult this file.
(The name of the file is apt because
a resolvconf nameserver information record
is named after the interface with which it is associated.)
.PP
The file contains a sequence of shell glob patterns,
one per line.
The position of a record in the order
is the point at which its name first matches a pattern.
.PP
Patterns may not contain whitespace, slashes or initial dots or tildes.
Blank lines and lines beginning with a '#' are ignored.
.PP
Resolvconf update scripts in
.I /etc/resolvconf/update.d/
that consult this file include the current default versions of
.IR bind ,
.IR dnsmasq ,
.IR pdnsd
and
.IR libc .
(Actually they don't read the file directly;
they call the utility program
.I /lib/resolvconf/list-records
which lists records in the specified order.)
.SH EXAMPLE
.nf
# /etc/resolvconf/interface-order
# Use nameservers on the loopback interface first.
lo*
# Next use records for Ethernet interfaces
eth*
# Next use records for Wi-Fi interfaces
wlan*
# Next use records for PPP interfaces
ppp*
# Last use other interfaces
*
.fi
.SH AUTHOR
Resolvconf was written by Thomas Hood <jdthood at yahoo.co.uk>.
.SH COPYRIGHT
Copyright \(co 2004 Thomas Hood
.br
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
.SH "SEE ALSO"
.BR resolvconf (8)
--- NEW FILE: po4a.conf ---
# first explain where are the transaltors input files
[po4a_paths] mans.pot ru:mans_ru.po
# Then list the documents to translate, their format, their translations
# (as well as the addendums to apply to the translations)
[type:man] interface-order.5 ru:out/interface-order.5 add_ru:translator_russian.add opt_ru:"-L KOI8-R"
[type:man] resolvconf.8 ru:out/resolvconf.8 add_ru:translator_russian.add opt_ru:"-L KOI8-R"
# Для отладки
#[type:man] interface-order.5 ru:out/interface-order.5
#[type:man] resolvconf.8 ru:out/resolvconf.8
--- NEW FILE: mans_ru.po ---
# translation of mans_ru.po to Russian
# SOME DESCRIPTIVE TITLE
# Copyright (C) 2006 Free Software Foundation, Inc.
# Yuri Kozlov <kozlov.y at gmail.com>, 2006.
#
msgid ""
msgstr ""
"Project-Id-Version: resolvconf-1.34\n"
"POT-Creation-Date: 2006-01-29 12:32+0300\n"
"PO-Revision-Date: 2006-01-29 14:10+0300\n"
"Last-Translator: Yuri Kozlov <kozlov.y at gmail.com>\n"
"Language-Team: Russian <debian-l10n-russian at lists.debian.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: KBabel 1.9.1\n"
# type: TH
#: interface-order.5:1
#, no-wrap
msgid "INTERFACE-ORDER"
msgstr "INTERFACE-ORDER"
# type: TH
#: interface-order.5:1
#, no-wrap
msgid "3 June 2004"
msgstr "3 июня 2004"
# type: TH
#: interface-order.5:1 interface-order.5:1 resolvconf.8:1 resolvconf.8:1
#, no-wrap
msgid "resolvconf"
msgstr "resolvconf"
# type: SH
#: interface-order.5:2 resolvconf.8:2
#, no-wrap
msgid "NAME"
msgstr "НАЗВАНИЕ"
# type: Plain text
#: interface-order.5:4
msgid "interface-order - resolvconf configuration file"
msgstr "interface-order - файл настройки resolvconf"
# type: SH
#: interface-order.5:4 resolvconf.8:14
#, no-wrap
msgid "DESCRIPTION"
msgstr "ОПИСАНИЕ"
# type: Plain text
#: interface-order.5:16
msgid ""
"The file I</etc/resolvconf/interface-order> is used to control the order in "
"which resolvconf nameserver information records are processed by those "
"resolvconf update scripts that consult this file. (The name of the file is "
"apt because a resolvconf nameserver information record is named after the "
"interface with which it is associated.)"
msgstr ""
"Файл I</etc/resolvconf/interface-order> используется для управления порядком, "
"в котором обрабатывается информация о серверах имён в сценариях обновления "
"resolvconf. (Имя файла настройки выбрано так, потому что порядок записей о серверах имён "
"зависит от названия интерфейсов с ними связанных.)"
# type: Plain text
#: interface-order.5:21
msgid ""
"The file contains a sequence of shell glob patterns, one per line. The "
"position of a record in the order is the point at which its name first "
"matches a pattern."
msgstr ""
"В файле описывается последовательность glob шаблонов оболочки, по одному на "
"строку. Позиция записи определяется местом, в котором название впервые "
"совпало с шаблоном."
# type: Plain text
#: interface-order.5:24
msgid ""
"Patterns may not contain whitespace, slashes or initial dots or tildes. "
"Blank lines and lines beginning with a '#' are ignored."
msgstr ""
"Шаблоны не должны содержать пробелов, символов косой черты или начинаться "
"с точки или тильды. "
"Пустые строки и строки, начинающиеся с '#', игнорируются."
# type: Plain text
#: interface-order.5:37
msgid ""
"Resolvconf update scripts in I</etc/resolvconf/update.d/> that consult this "
"file include the current default versions of I<bind>, I<dnsmasq>, I<pdnsd> "
"and I<libc>. (Actually they don't read the file directly; they call the "
"utility program I</lib/resolvconf/list-records> which lists records in the "
"specified order.)"
msgstr ""
"Resolvconf сценарии обновления в каталоге I</etc/resolvconf/update.d/>, которые "
"используют этот файл: I<bind>, I<dnsmasq>, I<pdnsd> и I<libc>. "
"(На самом деле они не читают этот файл самостоятельно; они вызывают вспомогательную "
"программу I</lib/resolvconf/list-records>, которая выдаёт записи в заданном порядке.)"
# type: SH
#: interface-order.5:37
#, no-wrap
msgid "EXAMPLE"
msgstr "ПРИМЕР"
# type: Plain text
#: interface-order.5:50
#, no-wrap
msgid ""
"# /etc/resolvconf/interface-order\n"
"# Use nameservers on the loopback interface first.\n"
"lo*\n"
"# Next use records for Ethernet interfaces\n"
"eth*\n"
"# Next use records for Wi-Fi interfaces\n"
"wlan*\n"
"# Next use records for PPP interfaces\n"
"ppp*\n"
"# Last use other interfaces\n"
"*\n"
msgstr ""
"# /etc/resolvconf/interface-order\n"
"# Сначала использовать сервера имён с loopback интерфейса.\n"
"lo*\n"
"# Затем использовать записи с Ethernet интерфейсов\n"
"eth*\n"
"# Затем использовать записи с Wi-Fi интерфейсов\n"
"wlan*\n"
"# Затем использовать записи с PPP iинтерфейсов\n"
"ppp*\n"
"# И в конце просмотреть остальные интерфейсы\n"
"*\n"
# type: SH
#: interface-order.5:52 resolvconf.8:139
#, no-wrap
msgid "AUTHOR"
msgstr "АВТОР"
# type: Plain text
#: interface-order.5:54
msgid "Resolvconf was written by Thomas Hood E<lt>jdthood at yahoo.co.ukE<gt>."
msgstr "Resolvconf написана Thomas Hood E<lt>jdthood at yahoo.co.ukE<gt>."
# type: SH
#: interface-order.5:54 resolvconf.8:141
#, no-wrap
msgid "COPYRIGHT"
msgstr "АВТОРСКОЕ ПРАВО"
# type: Plain text
#: interface-order.5:56 resolvconf.8:143
msgid "Copyright \\(co 2004 Thomas Hood"
msgstr "Copyright \\(co 2004 Thomas Hood"
# type: Plain text
#: interface-order.5:59 resolvconf.8:146
msgid ""
"This is free software; see the source for copying conditions. There is NO "
"warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE."
msgstr ""
"Это свободное программное обеспечение; условия копирования смотрите в "
"исходных текстах. Не даётся НИКАКИХ гарантий; даже КОММЕРЧЕСКОЙ ЦЕННОСТИ "
"или ПРИГОДНОСТИ ДЛЯ КОНКРЕТНОЙ ЦЕЛИ."
# type: SH
#: interface-order.5:59 resolvconf.8:146
#, no-wrap
msgid "SEE ALSO"
msgstr "СМОТРИТЕ ТАКЖЕ"
# type: Plain text
#: interface-order.5:60
msgid "B<resolvconf>(8)"
msgstr "B<resolvconf>(8)"
# type: TH
#: resolvconf.8:1
#, no-wrap
msgid "RESOLVCONF"
msgstr "RESOLVCONF"
# type: TH
#: resolvconf.8:1
#, no-wrap
msgid "April 2005"
msgstr "апрель 2005"
# type: Plain text
#: resolvconf.8:4
msgid "resolvconf - manage nameserver information"
msgstr "resolvconf - управляет информацией о серверах имён"
# type: SH
#: resolvconf.8:4
#, no-wrap
msgid "SYNOPSIS"
msgstr "СИНТАКСИС"
# type: Plain text
#: resolvconf.8:8
msgid "cat I<FILE> | B<resolvconf> B<-a> I<INTERFACE>"
msgstr "cat I<ФАЙЛ> | B<resolvconf> B<-a> I<ИНТЕРФЕЙС>"
# type: Plain text
#: resolvconf.8:11
msgid "B<resolvconf> B<-d> I<INTERFACE>"
msgstr "B<resolvconf> B<-d> I<ИНТЕРФЕЙС>"
# type: Plain text
#: resolvconf.8:14
msgid "B<resolvconf> B<-u>"
msgstr "B<resolvconf> B<-u>"
# type: Plain text
#: resolvconf.8:18
msgid ""
"Overwrite (B<-a>) or delete (B<-d>) the nameserver information record for "
"network interface I<INTERFACE> and run the update scripts in "
"I</etc/resolvconf/update.d/>."
msgstr ""
"При изменении (B<-a>) или удалении (B<-d>) записи о серверах имён для сетевого "
"интерфейса I<ИНТЕРФЕЙС> происходит запуск сценариев обновления из каталога "
"I</etc/resolvconf/update.d/>."
# type: Plain text
#: resolvconf.8:20
msgid "With B<-u>, just run the update scripts."
msgstr "При указании параметра B<-u> запускаются только сценарии обновления."
# type: SH
#: resolvconf.8:20
#, no-wrap
msgid "SERVERS"
msgstr "СЕРВЕРЫ"
# type: Plain text
#: resolvconf.8:40
msgid ""
"Normally B<resolvconf> is run only by hook scripts attached to network "
"interface configurers such as B<pppd>(8) (for ppp interfaces), to DHCP "
"clients such as B<dhclient3>(8), to B<ifup>(8) and B<ifdown>, and to DNS "
"caches such as B<dnsmasq>(8) (for the loopback interface). However, the "
"administrator can also run B<resolvconf> from the command line to add or "
"delete auxiliary nameserver information."
msgstr ""
"Обычно, B<resolvconf> запускается в виде обработчика настройщиками сетевых "
"интерфейсов, например, B<pppd>(8) (для ppp интерфейсов), DHCP клиентами "
"типа B<dhclient3>(8), B<ifup>(8) и B<ifdown>, кеширующими DNS "
"типа B<dnsmasq>(8) (для loopback интерфейса). Однако, администратор может "
"запустить B<resolvconf> из командной строки, чтобы добавить или удалить "
"дополнительную информацию о серверах имён."
# type: SH
#: resolvconf.8:40
#, no-wrap
msgid "CLIENTS"
msgstr "КЛИЕНТЫ"
# type: Plain text
#: resolvconf.8:53
msgid ""
"Nameserver information provided to B<resolvconf> is stored for use by "
"subscribers to B<resolvconf>'s notification service. Subscribers that need "
"to know when nameserver information has changed should install a script in "
"/etc/resolvconf/update.d/ (... or in /etc/resolvconf/update-libc.d/: see "
"below). For example, DNS caches such as B<dnsmasq>(8) and B<pdnsd>(8) "
"subscribe to the notification service so that they know whither to forward "
"queries."
msgstr ""
"Информация о серверах имён, предоставленная B<resolvconf>, сохраняется для "
"дальнейшего использования подписчикам сервиса уведомления B<resolvconf>. "
"Подписчикам, которым нужно знать, что информация о серверах имён изменилась, "
"должны установить сценарий в каталог /etc/resolvconf/update.d/ (... или "
"в /etc/resolvconf/update-libc.d/: смотрите ниже). Например, кеширующие DNS "
"типа B<dnsmasq>(8) и B<pdnsd>(8) подписываются на уведомление, чтобы знать "
"кому пересылать запросы."
# type: Plain text
#: resolvconf.8:68
msgid ""
"The most important piece of software that subscribes to the notification "
"service is the set of functions that make up the GNU C Library "
"B<resolver>(3). When nameserver information is updated the script "
"/etc/resolvconf/update.d/libc writes a new resolver configuration file to "
"/etc/resolvconf/run/resolv.conf and then runs the scripts in "
"/etc/resolvconf/update-libc.d/. To make the resolver use the dynamically "
"generated resolver configuration file the administrator should ensure that "
"/etc/resolv.conf is a symbolic link to /etc/resolvconf/run/resolv.conf. "
"This link is never modified by B</sbin/resolvconf>. If you find that "
"I</etc/resolv.conf> is not being updated, check to see that the link is "
"intact."
msgstr ""
"Наиболее важной частью программного обеспечения, которая использует подписку "
"на уведомление является набор функций, которые входят в библиотеку GNU C "
"B<resolver>(3). При обновлении информации о серверах имён сценарий "
"/etc/resolvconf/update.d/libc записывает новый файл настройки определителя имён "
"в /etc/resolvconf/run/resolv.conf и затем запускает сценарии из каталога "
"/etc/resolvconf/update-libc.d/. Чтобы определитель использовал динамически "
"создаваемый файл конфигурации администратор должен убедиться, что "
"/etc/resolv.conf является символической ссылкой на /etc/resolvconf/run/resolv.conf. "
"Эта ссылка никогда не изменяется B</sbin/resolvconf>. Если вы обнаружили, что "
"I</etc/resolv.conf> была обновлена, проверьте, что ссылка указывает на "
"/etc/resolvconf/run/resolv.conf."
# type: Plain text
#: resolvconf.8:74
msgid ""
"The GNU C Library resolver library isn't the only resolver library "
"available. However, any resolver library that reads /etc/resolv.conf (and "
"most of them do, in order to be compatible with the GNU C Library resolver) "
"should work with B<resolvconf>."
msgstr ""
"Библиотека GNU C Library resolver не является единственной реализацией "
"определителя имён. Однако, любая библиотека определителя, которая читает файл "
"/etc/resolv.conf (а большинство так и делает для совместимости с GNU C "
"Library resolver), должна работать с B<resolvconf>."
# type: Plain text
#: resolvconf.8:85
msgid ""
"Subscribers that need to know only when the resolver configuration file has "
"changed should install a script in /etc/resolvconf/update-libc.d/ rather "
"than in /etc/resolvconf/update.d/. (This is important for synchronization "
"purposes: scripts in update-libc.d/ are run I<after> resolv.conf has been "
"updated; the same is not necessarily true of scripts in update.d/.) "
"Examples of packages that do this are B<fetchmail>(1) and B<squid>(8)."
msgstr ""
"Подписчикам, которым только нужно знать, что файл настройки определителя изменился, "
"должны устанавливать сценарий в каталог /etc/resolvconf/update-libc.d/, а не в "
"/etc/resolvconf/update.d/. (Это важно из-за момента синхронизации: сценарии в update-libc.d/ "
"запускаются I<после> обновления resolv.conf; это необязательно верно для сценариев "
"из каталога update.d/.) "
"Примеры пакетов, которые это используют: B<fetchmail>(1) и B<squid>(8)."
# type: Plain text
#: resolvconf.8:88
msgid ""
"Hook scripts will find the files containing nameserver information in the "
"current directory."
msgstr ""
"Сценарии-обработчики найдут файлы, содержащие информацию о серверах имён, "
"в текущем каталоге."
# type: SH
#: resolvconf.8:88
#, no-wrap
msgid "OPTIONS"
msgstr "ПАРАМЕТРЫ"
# type: TP
#: resolvconf.8:89
#, no-wrap
msgid "B<-a> I<INTERFACE>"
msgstr "B<-a> I<ИНТЕРФЕЙС>"
# type: Plain text
#: resolvconf.8:98
msgid ""
"Add or overwrite the record for network interface I<INTERFACE>. When this "
"option is used the information must be provided to B<resolvconf> on its "
"standard input in the format of the B<resolv.conf>(5) file. Each line in "
"the file must be terminated by a newline."
msgstr ""
"Добавляет или изменяет запись для сетевого интерфейса I<ИНТЕРФЕЙС>. При "
"использовании данного параметра для B<resolvconf> должна быть предоставлена "
"информация на стандартный ввод в формате B<resolv.conf>(5) файла. Каждая строка "
"в файле должна заканчиваться символом новой строки."
# type: TP
#: resolvconf.8:98
#, no-wrap
msgid "B<-d> I<INTERFACE>"
msgstr "B<-d> I<ИНТЕРФЕЙС>"
# type: Plain text
#: resolvconf.8:101
msgid "Delete the record for network interface I<INTERFACE>."
msgstr "Удаляет запись для сетевого интерфейса I<ИНТЕРФЕЙС>."
# type: Plain text
#: resolvconf.8:104
msgid ""
"The I<INTERFACE> name may not contain spaces, slashes or initial dots, "
"hyphens or tildes."
msgstr ""
"В имени I<ИНТЕРФЕЙСА> не должно быть пробелов, символов косой черты и оно не "
"должно начинаться с точки, переноса или тильды."
# type: Plain text
#: resolvconf.8:107
msgid ""
"Following the addition or deletion of the record, resolvconf runs the update "
"scripts as described in the CLIENTS section."
msgstr ""
"После добавления или удаления записи, resolvconf запускает сценарии "
"обновления как описано в разделе КЛИЕНТЫ."
# type: TP
#: resolvconf.8:107
#, no-wrap
msgid "B<-u>"
msgstr "B<-u>"
# type: Plain text
#: resolvconf.8:110
msgid "Just run the update scripts."
msgstr "Только запускает сценарии обновления."
# type: SH
#: resolvconf.8:110
#, no-wrap
msgid "FILES"
msgstr "ФАЙЛЫ"
# type: TP
#: resolvconf.8:111
#, no-wrap
msgid "I</etc/resolvconf/run>"
msgstr "I</etc/resolvconf/run>"
# type: Plain text
#: resolvconf.8:117
msgid ""
"This is either a directory where nameserver information can be stored or a "
"symbolic link to such a directory. Clients should not make any assumptions "
"about the canonical location of this directory or the hierarchy that is "
"constructed under it."
msgstr ""
"Это или каталог, в котором может храниться информация о серверах имён или "
"символическая ссылка на такой каталог. Клиенты не должны делать предположения "
"о размещении этого каталога и его внутреннем содержимом."
# type: TP
#: resolvconf.8:117
#, no-wrap
msgid "I</etc/resolvconf/interface-order>"
msgstr "I</etc/resolvconf/interface-order>"
# type: Plain text
#: resolvconf.8:122
msgid ""
"Determines the order in which nameserver information records are processed. "
"See B<interface-order>(5)."
msgstr ""
"Определяет порядок, в котором будет обрабатываться информация о серверах имён. "
"Смотрите B<interface-order>(5)."
# type: TP
#: resolvconf.8:122
#, no-wrap
msgid "I</etc/resolvconf/resolv.conf.d/base>"
msgstr "I</etc/resolvconf/resolv.conf.d/base>"
# type: Plain text
#: resolvconf.8:127
msgid ""
"File containing basic resolver information. The lines in this file are "
"included in the resolver configuration file even when no interfaces are "
"configured."
msgstr ""
"В файле хранится основная информация определителя имён. Строки в этом файле "
"включаются в файл настройки определителя даже когда не настроено ни одного "
"интерфейса."
# type: TP
#: resolvconf.8:127
#, no-wrap
msgid "I</etc/resolvconf/resolv.conf.d/head>"
msgstr "I</etc/resolvconf/resolv.conf.d/head>"
# type: Plain text
#: resolvconf.8:131
msgid ""
"File to be prepended to the dynamically generated resolver configuration "
"file. Normally this is just a comment line."
msgstr ""
"В файле хранится информация, которая вставляется до динамически создаваемой "
"конфигурации. Обычно, это просто строки комментария."
# type: TP
#: resolvconf.8:131
#, no-wrap
msgid "I</etc/resolvconf/resolv.conf.d/tail>"
msgstr "I</etc/resolvconf/resolv.conf.d/tail>"
# type: Plain text
#: resolvconf.8:135
msgid ""
"File to be appended to the dynamically generated resolver configuration "
"file. To append nothing, make this an empty file."
msgstr ""
"В файле хранится информация, которая вставляется после динамически создаваемой "
"конфигурации. Если добавлять нечего, создайте пустой файл."
# type: SH
#: resolvconf.8:135
#, no-wrap
msgid "BUGS"
msgstr "БАГИ"
# type: Plain text
#: resolvconf.8:139
msgid ""
"Currently B<resolvconf> does not check the sanity of the information "
"provided to it."
msgstr ""
"В настоящий момент B<resolvconf> не проверяет правильность информации, которая "
"к ней поступает."
# type: Plain text
#: resolvconf.8:141
msgid "Written by Thomas Hood E<lt>jdthood at yahoo.co.ukE<gt>."
msgstr "Написана Thomas Hood E<lt>jdthood at yahoo.co.ukE<gt>."
# type: Plain text
#: resolvconf.8:149
msgid "B<interface-order>(5), B<resolv.conf>(5), B<resolver>(3)."
msgstr "B<interface-order>(5), B<resolv.conf>(5), B<resolver>(3)."
--- NEW FILE: debian_po_ru.po ---
# translation of ru.po to Russian
#
# Translators, if you are not familiar with the PO format, gettext
# documentation is worth reading, especially sections dedicated to
# this format, e.g. by running:
# info -n '(gettext)PO Files'
# info -n '(gettext)Header Entry'
# Some information specific to po-debconf are available at
# /usr/share/doc/po-debconf/README-trans
# or http://www.debian.org/intl/l10n/po-debconf/README-trans#
# Developers do not need to manually edit POT or PO files.
# Yuri Kozlov <kozlov.y at gmail.com>, 2006.
#
msgid ""
msgstr ""
"Project-Id-Version: resolvconf-1.34\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2005-07-30 16:33+0200\n"
"PO-Revision-Date: 2006-01-29 11:28+0300\n"
"Last-Translator: Yuri Kozlov <kozlov.y at gmail.com>\n"
"Language-Team: Russian <debian-l10n-russian at lists.debian.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: KBabel 1.9.1\n"
#. Type: note
#. Description
#: ../templates:3
msgid "A rogue pppconfig PPP hook script is present"
msgstr "Обнаружен неконтролируемый обработчик pppconfig PPP"
#. Type: note
#. Description
#: ../templates:3
msgid ""
"Certain versions of the pppconfig package contain scripts /etc/ppp/ip-up."
"d/0dns-up and /etc/ppp/ip-down.d/0dns-down (run by pppd after a PPP "
"interface is brought up or down) that overwrite /etc/resolv.conf. These "
"scripts must be modified, disabled or deleted so that they will not "
"interfere with the operation of resolvconf."
msgstr ""
"Некоторые версии пакета pppconfig содержат сценарии /etc/ppp/ip-up.d/0dns-up и /etc/ppp/ip-down.d/0dns-down (запускаемые pppd после активации "
"или деактивации PPP интерфейса), которые перезаписывают /etc/resolv.conf. "
"Эти сценарии должны быть изменены, выключены или удалены для того, чтобы "
"не мешать работе resolvconf."
#. Type: note
#. Description
#: ../templates:3
msgid ""
"A non-empty executable script /etc/ppp/ip-up.d/0dns-up and/or /etc/ppp/ip-"
"down.d/0dns-down has been detected that appears to overwrite /etc/resolv."
"conf. Each one that does so must be modified, disabled or deleted. The best "
"way to disable it is to remove its execute permission. The best way to "
"delete it is to purge the pppconfig package."
msgstr ""
"Обнаружен не пустой исполняемый сценарий /etc/ppp/ip-up.d/0dns-up и/или /etc/ppp/ip-"
"down.d/0dns-down, который вероятно перезаписывает /etc/resolv.conf. Если это "
"так, то его нужно изменить, выключить или удалить. Для выключения отлично подходит способ "
"удаления прав исполнения со сценария. При удалении лучше всего вычищать пакет pppconfig "
"целиком."
#. Type: note
#. Description
#: ../templates:20
msgid "A rogue pppoeconf PPP hook script is present"
msgstr "Обнаружен неконтролируемый обработчик pppoeconf PPP"
#. Type: note
#. Description
#: ../templates:20
msgid ""
"Versions of the pppoeconf package prior to version 1.0 contain a script /etc/"
"ppp/ip-up.d/000usepeerdns (run by pppd after a PPP interface is brought up) "
"that overwrites /etc/resolv.conf. The script must be modified, disabled or "
"deleted so that it will not interfere with the operation of resolvconf. "
"Contrary to Debian policy, merely removing the pppoeconf package does not "
"disable the script."
msgstr ""
"Все версии пакета pppoeconf до 1.0 содержат сценарий /etc/"
"ppp/ip-up.d/000usepeerdns (запускаемый pppd после активации PPP интерфейса), "
"который перезаписывает /etc/resolv.conf. Этот сценарий должен быть изменён, "
"выключен или удалён для того, чтобы не мешать работе resolvconf. "
"Вопреки политике Debian, простое удаление пакета pppoeconf не блокирует этот "
"сценарий."
#. Type: note
#. Description
#: ../templates:20
msgid ""
"A non-empty executable script /etc/ppp/ip-up.d/000usepeerdns has been "
"detected. It must be modified, disabled or deleted. The best way to modify "
"it is to upgrade the pppoeconf package to version 1.0 or later and to allow "
"dpkg to install the new version of the script. The best way to disable it is "
"to remove its execute permission. The best way to delete it is to purge the "
"pppoeconf package."
msgstr ""
"Обнаружен не пустой исполняемый сценарий /etc/ppp/ip-up.d/000usepeerdns. "
"Он должен быть изменён, выключен или удалён. Для изменения лучше обновить "
"пакет pppoeconf до версии 1.0 или более новой и разрешить dpkg установить "
"новую версию сценария. Для выключения отлично подходит способ "
"удаления прав исполнения со сценария. При удалении лучше всего вычищать пакет "
"pppoeconf целиком."
#. Type: note
#. Description
#: ../templates:38
msgid "A rogue xisp PPP hook script is present"
msgstr "Обнаружен неконтролируемый обработчик xisp PPP"
#. Type: note
#. Description
#: ../templates:38
msgid ""
"The xisp package contains scripts /etc/ppp/ip-up.d/0xisp-dns and /etc/ppp/ip-"
"down.d/0xisp-dns (run by pppd after a PPP interface is brought up or down) "
"that overwrite /etc/resolv.conf. The scripts must be modified, disabled or "
"deleted so that they will not interfere with the operation of resolvconf. "
"Contrary to Debian policy, merely removing the xisp package does not disable "
"the scripts."
msgstr ""
"Пакет xisp содержит сценарии /etc/ppp/ip-up.d/0xisp-dns и /etc/ppp/ip-"
"down.d/0xisp-dns (запускаемые pppd после активации или деактивации PPP "
"интерфейса), которые перезаписывают /etc/resolv.conf. Эти сценарии должны "
"быть изменены, выключены или удалены для того, чтобы не мешать работе "
"resolvconf. Вопреки политике Debian, простое удаление пакета xisp не "
"блокирует этот сценарий."
#. Type: note
#. Description
#: ../templates:38
msgid ""
"A non-empty executable script /etc/ppp/ip-up.d/0xisp-dns and/or /etc/ppp/ip-"
"down.d/0xisp-dns has been detected. Each one must be modified, disabled or "
"deleted. The best way to disable it is to remove its execute permission. The "
"best way to delete it is to purge the xisp package."
msgstr ""
"Обнаружен не пустой исполняемый сценарий /etc/ppp/ip-up.d/0xisp-dns и/или "
"/etc/ppp/ip-down.d/0xisp-dns. Его нужно изменить, выключить или удалить. "
"Для выключения отлично подходит способ удаления прав исполнения со сценария. "
"При удалении лучше всего вычищать пакет xisp целиком."
#. Type: boolean
#. Description
#: ../templates:55
msgid "Disable rogue hook scripts?"
msgstr "Заблокировать неконтролируемые обработчики?"
#. Type: boolean
#. Description
#: ../templates:55
msgid ""
"Certain packages contain hook scripts which, contrary to Debian policy, "
"modify the resolver configuration file even when the packages that own them "
"are removed. Packages known to contain such rogue hook scripts are: "
"pppconfig (<< 2.2.0 and 2.3), pppoeconf (<< 1.0), totd (<< 1.4-4) and xisp. "
"Although the resolvconf package is marked as conflicting with these packages "
"so that they are removed before resolvconf is installed, their rogue hook "
"scripts may remain behind."
msgstr ""
"Некоторые пакеты содержат обработчики, которые вопреки политике Debian, "
"изменяют файл настройки определителя имён, даже когда пакеты содержащие их, "
"были удалены. Известные таким поведением пакеты: "
"pppconfig (<< 2.2.0 и 2.3), pppoeconf (<< 1.0), totd (<< 1.4-4) и xisp. "
"Хотя пакет resolvconf настроен как конфликтующий с этими пакетами и они будут "
"удалены перед установкой resolvconf, их неконтролируемые обработчики могут "
"остаться в системе."
#. Type: boolean
#. Description
#: ../templates:55
msgid ""
"If you agree then the post-installation process will disable rogue hook "
"scripts by removing their execute permissions."
msgstr ""
"Если вы ответите утвердительно, то завершающий процесс установки заблокирует "
"неконтролируемые обработчики удалив их права исполнения."
#. Type: boolean
#. Description
#: ../templates:55
msgid ""
"If you do not agree then you should disable the rogue scripts manually, "
"otherwise resolvconf will not work properly."
msgstr ""
"Если вы ответите отрицательно, то вы должны самостоятельно выключить "
"неконтролируемые обработчики, иначе resolvconf будет работать неправильно."
#. Type: boolean
#. Description
#: ../templates:73
msgid "Prepare /etc/resolv.conf for dynamic updates?"
msgstr "Включить динамическое обновление /etc/resolv.conf?"
#. Type: boolean
#. Description
#: ../templates:73
msgid ""
"This package contains the infrastructure required for dynamic updating of "
"the resolver configuration file. Part of the necessary infrastructure is a "
"symbolic link from /etc/resolv.conf to /etc/resolvconf/run/resolv.conf. If "
"you agree then this link will be created. The existing /etc/resolv.conf file "
"will be preserved as /etc/resolvconf/resolv.conf.d/original; it will be "
"restored if this package is removed."
msgstr ""
"Данный пакет содержит инфраструктуру динамического обновления "
"файла настройки определителя имён. Одной из необходимых частей инфраструктуры "
"является символическая ссылка /etc/resolv.conf на "
"/etc/resolvconf/run/resolv.conf. Если вы ответите утвердительно, то такая "
"ссылка будет создана. Существующий файл /etc/resolv.conf будет сохранён под "
"именем /etc/resolvconf/resolv.conf.d/original; он будет восстановлен при "
"удалении пакета."
#. Type: boolean
#. Description
#: ../templates:73
msgid ""
"If you wish to prevent future installations from recreating the symbolic "
"link then you can run dpkg-reconfigure later to withdraw your agreement."
msgstr ""
"Если в будущем вы захотите отказаться от создания символической ссылки, то "
"можете запустить dpkg-reconfigure и отменить своё согласие."
#. Type: boolean
#. Description
#: ../templates:73
msgid ""
"If you do not agree then the necessary symbolic link will not be created and "
"consequently your resolver configuration file will not be dynamically "
"updated. In order to activate dynamic updating you will have to configure "
"resolvconf manually following the straightforward instructions in the README "
"file. If you choose not to configure resolvconf at all then you should "
"remove the package because its presence causes some programs to deviate from "
"their default behavior."
msgstr ""
"Если вы не согласитесь, то необходимая символическая ссылка не будет создана "
"и следовательно файл настройки определителя имён не будет динамически "
"обновляться. Чтобы включить динамическое обновление нужно настроить resolvconf "
"вручную согласно простым инструкциям из файла README. Если вы не хотите "
"настраивать resolvconf, то должны удалить этот пакет, так как его "
"наличие в системе влияет на некоторые программы заставляя их изменять своё "
"поведение по умолчанию."
#. Type: boolean
#. Description
#: ../templates:73
msgid "However you decide, you should read the README file."
msgstr "Однако решать вам, прочитайте файл README."
#. Type: note
#. Description
#: ../templates:96
msgid "Remember to reconfigure network interfaces"
msgstr "Не забудьте перенастроить сетевые интерфейсы"
#. Type: note
#. Description
#: ../templates:96
msgid ""
"Once resolvconf is installed, interface configurers supply nameserver "
"information to it (which it then makes available to the C Library resolver "
"and to DNS caches). However, they do this only when they bring up "
"interfaces. Therefore for resolvconf's nameserver information to be up to "
"date after initial installation it is necessary to reconfigure interfaces -- "
"that is, to take them down and then to bring them up again -- and to restart "
"DNS caches."
msgstr ""
"После установки resolvconf, настройщики интерфейсов предоставляют ему "
"информацию о серверах имён (которая затем становится доступна C библиотеке "
"resolver и кеширующим DNS). Однако, они делают это только при активации "
"интерфейсов. Поэтому, чтобы синхронизировать информацию о серверах имён для "
"resolvconf после начальной установки необходимо перенастроить интерфейсы, "
"то есть, деактивировать их и тут же активировать заново, а также перезапустить "
"кеширующие DNS."
#. Type: boolean
#. Description
#: ../templates:108
msgid "Append original file to dynamic file?"
msgstr "Добавить имеющийся файл в динамически обновляемый файл?"
#. Type: boolean
#. Description
#: ../templates:108
msgid ""
"If your original static resolver configuration file (/etc/resolv.conf) "
"contains nameserver addresses then those addresses should be listed on \"dns-"
"nameservers\" lines in /etc/network/interfaces as described in the README. "
"Until you have modified /etc/network/interfaces and reconfigured the "
"affected interfaces resolvconf will not include those addresses in the "
"dynamically generated resolver configuration file. Without those addresses "
"you may have trouble resolving domain names. A TEMPORARY solution is to "
"append the whole original resolver configuration file to the end of the "
"dynamically generated file. This will be done if there is a symbolic link "
"from /etc/resolvconf/resolv.conf.d/tail to /etc/resolvconf/resolv.conf.d/"
"original. If you agree then this symbolic link will be created, provided "
"that no /etc/resolvconf/resolv.conf.d/tail already exists."
msgstr ""
"Если ваш статический файл настройки определителя имён (/etc/resolv.conf) "
"содержит адреса серверов имён, то эти адреса должны быть записаны в "
"строках \"dns-nameservers\" в файле /etc/network/interfaces согласно файлу "
"README. Пока вы не измените /etc/network/interfaces и не перенастроите "
"соответствующие интерфейсы resolvconf не включит эти адреса в динамически "
"создаваемый файл настройки определителя имён. Без этих адресов у вас могут "
"возникнуть проблемы с определением имён компьютеров. ВРЕМЕННЫМ решением "
"является добавление всего имеющегося файла настройки определителя имён в конец "
"динамически создаваемого файла. Это будет сделано, если есть символическая "
"ссылка /etc/resolvconf/resolv.conf.d/tail на /etc/resolvconf/resolv.conf.d/"
"original. Если вы ответите утвердительно, то такая ссылка будет создана, если "
"файл /etc/resolvconf/resolv.conf.d/tail уже не существует."
#. Type: boolean
#. Description
#: ../templates:108
msgid ""
"After you have modified /etc/network/interfaces to add the required \"dns-"
"nameservers\" lines you should point the /etc/resolvconf/resolv.conf.d/tail "
"symbolic link to /dev/null."
msgstr ""
"После добавления в /etc/network/interfaces необходимых строк \"dns-"
"nameservers\" нужно изменить символическую ссылку "
"/etc/resolvconf/resolv.conf.d/tail, чтобы она указывала в /dev/null."
--- NEW FILE: mans.pot ---
# SOME DESCRIPTIVE TITLE
# Copyright (C) YEAR Free Software Foundation, Inc.
# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2006-01-29 12:32+0300\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
"Language-Team: LANGUAGE <LL at li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=CHARSET\n"
"Content-Transfer-Encoding: ENCODING"
# type: TH
#: interface-order.5:1
#, no-wrap
msgid "INTERFACE-ORDER"
msgstr ""
# type: TH
#: interface-order.5:1
#, no-wrap
msgid "3 June 2004"
msgstr ""
# type: TH
#: interface-order.5:1 interface-order.5:1 resolvconf.8:1 resolvconf.8:1
#, no-wrap
msgid "resolvconf"
msgstr ""
# type: SH
#: interface-order.5:2 resolvconf.8:2
#, no-wrap
msgid "NAME"
msgstr ""
# type: Plain text
#: interface-order.5:4
msgid "interface-order - resolvconf configuration file"
msgstr ""
# type: SH
#: interface-order.5:4 resolvconf.8:14
#, no-wrap
msgid "DESCRIPTION"
msgstr ""
# type: Plain text
#: interface-order.5:16
msgid ""
"The file I</etc/resolvconf/interface-order> is used to control the order in "
"which resolvconf nameserver information records are processed by those "
"resolvconf update scripts that consult this file. (The name of the file is "
"apt because a resolvconf nameserver information record is named after the "
"interface with which it is associated.)"
msgstr ""
# type: Plain text
#: interface-order.5:21
msgid ""
"The file contains a sequence of shell glob patterns, one per line. The "
"position of a record in the order is the point at which its name first "
"matches a pattern."
msgstr ""
# type: Plain text
#: interface-order.5:24
msgid ""
"Patterns may not contain whitespace, slashes or initial dots or tildes. "
"Blank lines and lines beginning with a '#' are ignored."
msgstr ""
# type: Plain text
#: interface-order.5:37
msgid ""
"Resolvconf update scripts in I</etc/resolvconf/update.d/> that consult this "
"file include the current default versions of I<bind>, I<dnsmasq>, I<pdnsd> "
"and I<libc>. (Actually they don't read the file directly; they call the "
"utility program I</lib/resolvconf/list-records> which lists records in the "
"specified order.)"
msgstr ""
# type: SH
#: interface-order.5:37
#, no-wrap
msgid "EXAMPLE"
msgstr ""
# type: Plain text
#: interface-order.5:50
#, no-wrap
msgid ""
"# /etc/resolvconf/interface-order\n"
"# Use nameservers on the loopback interface first.\n"
"lo*\n"
"# Next use records for Ethernet interfaces\n"
"eth*\n"
"# Next use records for Wi-Fi interfaces\n"
"wlan*\n"
"# Next use records for PPP interfaces\n"
"ppp*\n"
"# Last use other interfaces\n"
"*\n"
msgstr ""
# type: SH
#: interface-order.5:52 resolvconf.8:139
#, no-wrap
msgid "AUTHOR"
msgstr ""
# type: Plain text
#: interface-order.5:54
msgid "Resolvconf was written by Thomas Hood E<lt>jdthood at yahoo.co.ukE<gt>."
msgstr ""
# type: SH
#: interface-order.5:54 resolvconf.8:141
#, no-wrap
msgid "COPYRIGHT"
msgstr ""
# type: Plain text
#: interface-order.5:56 resolvconf.8:143
msgid "Copyright \\(co 2004 Thomas Hood"
msgstr ""
# type: Plain text
#: interface-order.5:59 resolvconf.8:146
msgid ""
"This is free software; see the source for copying conditions. There is NO "
"warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE."
msgstr ""
# type: SH
#: interface-order.5:59 resolvconf.8:146
#, no-wrap
msgid "SEE ALSO"
msgstr ""
# type: Plain text
#: interface-order.5:60
msgid "B<resolvconf>(8)"
msgstr ""
# type: TH
#: resolvconf.8:1
#, no-wrap
msgid "RESOLVCONF"
msgstr ""
# type: TH
#: resolvconf.8:1
#, no-wrap
msgid "April 2005"
msgstr ""
# type: Plain text
#: resolvconf.8:4
msgid "resolvconf - manage nameserver information"
msgstr ""
# type: SH
#: resolvconf.8:4
#, no-wrap
msgid "SYNOPSIS"
msgstr ""
# type: Plain text
#: resolvconf.8:8
msgid "cat I<FILE> | B<resolvconf> B<-a> I<INTERFACE>"
msgstr ""
# type: Plain text
#: resolvconf.8:11
msgid "B<resolvconf> B<-d> I<INTERFACE>"
msgstr ""
# type: Plain text
#: resolvconf.8:14
msgid "B<resolvconf> B<-u>"
msgstr ""
# type: Plain text
#: resolvconf.8:18
msgid ""
"Overwrite (B<-a>) or delete (B<-d>) the nameserver information record for "
"network interface I<INTERFACE> and run the update scripts in "
"I</etc/resolvconf/update.d/>."
msgstr ""
# type: Plain text
#: resolvconf.8:20
msgid "With B<-u>, just run the update scripts."
msgstr ""
# type: SH
#: resolvconf.8:20
#, no-wrap
msgid "SERVERS"
msgstr ""
# type: Plain text
#: resolvconf.8:40
msgid ""
"Normally B<resolvconf> is run only by hook scripts attached to network "
"interface configurers such as B<pppd>(8) (for ppp interfaces), to DHCP "
"clients such as B<dhclient3>(8), to B<ifup>(8) and B<ifdown>, and to DNS "
"caches such as B<dnsmasq>(8) (for the loopback interface). However, the "
"administrator can also run B<resolvconf> from the command line to add or "
"delete auxiliary nameserver information."
msgstr ""
# type: SH
#: resolvconf.8:40
#, no-wrap
msgid "CLIENTS"
msgstr ""
# type: Plain text
#: resolvconf.8:53
msgid ""
"Nameserver information provided to B<resolvconf> is stored for use by "
"subscribers to B<resolvconf>'s notification service. Subscribers that need "
"to know when nameserver information has changed should install a script in "
"/etc/resolvconf/update.d/ (... or in /etc/resolvconf/update-libc.d/: see "
"below). For example, DNS caches such as B<dnsmasq>(8) and B<pdnsd>(8) "
"subscribe to the notification service so that they know whither to forward "
"queries."
msgstr ""
# type: Plain text
#: resolvconf.8:68
msgid ""
"The most important piece of software that subscribes to the notification "
"service is the set of functions that make up the GNU C Library "
"B<resolver>(3). When nameserver information is updated the script "
"/etc/resolvconf/update.d/libc writes a new resolver configuration file to "
"/etc/resolvconf/run/resolv.conf and then runs the scripts in "
"/etc/resolvconf/update-libc.d/. To make the resolver use the dynamically "
"generated resolver configuration file the administrator should ensure that "
"/etc/resolv.conf is a symbolic link to /etc/resolvconf/run/resolv.conf. "
"This link is never modified by B</sbin/resolvconf>. If you find that "
"I</etc/resolv.conf> is not being updated, check to see that the link is "
"intact."
msgstr ""
# type: Plain text
#: resolvconf.8:74
msgid ""
"The GNU C Library resolver library isn't the only resolver library "
"available. However, any resolver library that reads /etc/resolv.conf (and "
"most of them do, in order to be compatible with the GNU C Library resolver) "
"should work with B<resolvconf>."
msgstr ""
# type: Plain text
#: resolvconf.8:85
msgid ""
"Subscribers that need to know only when the resolver configuration file has "
"changed should install a script in /etc/resolvconf/update-libc.d/ rather "
"than in /etc/resolvconf/update.d/. (This is important for synchronization "
"purposes: scripts in update-libc.d/ are run I<after> resolv.conf has been "
"updated; the same is not necessarily true of scripts in update.d/.) "
"Examples of packages that do this are B<fetchmail>(1) and B<squid>(8)."
msgstr ""
# type: Plain text
#: resolvconf.8:88
msgid ""
"Hook scripts will find the files containing nameserver information in the "
"current directory."
msgstr ""
# type: SH
#: resolvconf.8:88
#, no-wrap
msgid "OPTIONS"
msgstr ""
# type: TP
#: resolvconf.8:89
#, no-wrap
msgid "B<-a> I<INTERFACE>"
msgstr ""
# type: Plain text
#: resolvconf.8:98
msgid ""
"Add or overwrite the record for network interface I<INTERFACE>. When this "
"option is used the information must be provided to B<resolvconf> on its "
"standard input in the format of the B<resolv.conf>(5) file. Each line in "
"the file must be terminated by a newline."
msgstr ""
# type: TP
#: resolvconf.8:98
#, no-wrap
msgid "B<-d> I<INTERFACE>"
msgstr ""
# type: Plain text
#: resolvconf.8:101
msgid "Delete the record for network interface I<INTERFACE>."
msgstr ""
# type: Plain text
#: resolvconf.8:104
msgid ""
"The I<INTERFACE> name may not contain spaces, slashes or initial dots, "
"hyphens or tildes."
msgstr ""
# type: Plain text
#: resolvconf.8:107
msgid ""
"Following the addition or deletion of the record, resolvconf runs the update "
"scripts as described in the CLIENTS section."
msgstr ""
# type: TP
#: resolvconf.8:107
#, no-wrap
msgid "B<-u>"
msgstr ""
# type: Plain text
#: resolvconf.8:110
msgid "Just run the update scripts."
msgstr ""
# type: SH
#: resolvconf.8:110
#, no-wrap
msgid "FILES"
msgstr ""
# type: TP
#: resolvconf.8:111
#, no-wrap
msgid "I</etc/resolvconf/run>"
msgstr ""
# type: Plain text
#: resolvconf.8:117
msgid ""
"This is either a directory where nameserver information can be stored or a "
"symbolic link to such a directory. Clients should not make any assumptions "
"about the canonical location of this directory or the hierarchy that is "
"constructed under it."
msgstr ""
# type: TP
#: resolvconf.8:117
#, no-wrap
msgid "I</etc/resolvconf/interface-order>"
msgstr ""
# type: Plain text
#: resolvconf.8:122
msgid ""
"Determines the order in which nameserver information records are processed. "
"See B<interface-order>(5)."
msgstr ""
# type: TP
#: resolvconf.8:122
#, no-wrap
msgid "I</etc/resolvconf/resolv.conf.d/base>"
msgstr ""
# type: Plain text
#: resolvconf.8:127
msgid ""
"File containing basic resolver information. The lines in this file are "
"included in the resolver configuration file even when no interfaces are "
"configured."
msgstr ""
# type: TP
#: resolvconf.8:127
#, no-wrap
msgid "I</etc/resolvconf/resolv.conf.d/head>"
msgstr ""
# type: Plain text
#: resolvconf.8:131
msgid ""
"File to be prepended to the dynamically generated resolver configuration "
"file. Normally this is just a comment line."
msgstr ""
# type: TP
#: resolvconf.8:131
#, no-wrap
msgid "I</etc/resolvconf/resolv.conf.d/tail>"
msgstr ""
# type: Plain text
#: resolvconf.8:135
msgid ""
"File to be appended to the dynamically generated resolver configuration "
"file. To append nothing, make this an empty file."
msgstr ""
# type: SH
#: resolvconf.8:135
#, no-wrap
msgid "BUGS"
msgstr ""
# type: Plain text
#: resolvconf.8:139
msgid ""
"Currently B<resolvconf> does not check the sanity of the information "
"provided to it."
msgstr ""
# type: Plain text
#: resolvconf.8:141
msgid "Written by Thomas Hood E<lt>jdthood at yahoo.co.ukE<gt>."
msgstr ""
# type: Plain text
#: resolvconf.8:149
msgid "B<interface-order>(5), B<resolv.conf>(5), B<resolver>(3)."
msgstr ""
--- NEW FILE: resolvconf.8 ---
.TH RESOLVCONF "8" "April 2005" "resolvconf" "resolvconf"
.SH NAME
resolvconf \- manage nameserver information
.SH SYNOPSIS
cat \fIFILE\fR |
.B resolvconf
\fB\-a\fR \fIINTERFACE\fR
.PP
.B resolvconf
\fB\-d\fR \fIINTERFACE\fR
.PP
.B resolvconf
\fB\-u\fR
.SH DESCRIPTION
Overwrite (\fB\-a\fR) or delete (\fB\-d\fR) the nameserver information
record for network interface \fIINTERFACE\fR
and run the update scripts in \fI/etc/resolvconf/update.d/\fR.
.PP
With \fB\-u\fR, just run the update scripts.
.SH SERVERS
Normally
.B resolvconf
is run only by hook scripts attached to network interface configurers
such as
.BR pppd (8)
(for ppp interfaces),
to DHCP clients such as
.BR dhclient3 (8),
to
.BR ifup (8)
and
.BR ifdown ,
and
to DNS caches such as
.BR dnsmasq (8)
(for the loopback interface).
However, the administrator can also run
.B resolvconf
from the command line to add or delete auxiliary nameserver information.
.SH CLIENTS
Nameserver information provided to
.B resolvconf
is stored for use by subscribers to \fBresolvconf\fR's notification service.
Subscribers that need to know when nameserver information has changed
should install a script in /etc/resolvconf/update.d/
(... or in /etc/resolvconf/update-libc.d/: see below).
For example, DNS caches such as
.BR dnsmasq (8)
and
.BR pdnsd (8)
subscribe to the notification service so that they know
whither to forward queries.
.PP
The most important piece of
software that subscribes to the notification service is the set of functions
that make up the GNU C Library
.BR resolver (3).
When nameserver information is updated the script
/etc/resolvconf/update.d/libc writes a new resolver configuration
file to /etc/resolvconf/run/resolv.conf and then runs the scripts in
/etc/resolvconf/update-libc.d/.
To make the resolver use the dynamically generated resolver configuration
file the administrator should ensure that /etc/resolv.conf is a symbolic
link to /etc/resolvconf/run/resolv.conf.
This link is never modified by \fB/sbin/resolvconf\fR.
If you find that \fI/etc/resolv.conf\fR is not being updated,
check to see that the link is intact.
.PP
The GNU C Library resolver library isn't the only resolver library available.
However, any resolver library that reads /etc/resolv.conf
(and most of them do, in order to be compatible with the GNU C Library resolver)
should work with
.BR resolvconf .
.PP
Subscribers that need to know only when the resolver configuration file
has changed should install a script in /etc/resolvconf/update-libc.d/
rather than in /etc/resolvconf/update.d/.
(This is important for synchronization purposes:
scripts in update-libc.d/ are run \fIafter\fR resolv.conf has been updated;
the same is not necessarily true of scripts in update.d/.)
Examples of packages that do this are
.BR fetchmail (1)
and
.BR squid (8).
.PP
Hook scripts will find the files containing nameserver
information in the current directory.
.SH OPTIONS
.TP
\fB\-a\fR \fIINTERFACE\fR
Add or overwrite the record for network interface \fIINTERFACE\fR.
When this option is used the information must be provided to
.B resolvconf
on its standard input in the format of the
.BR resolv.conf (5)
file.
Each line in the file must be terminated by a newline.
.TP
\fB\-d\fR \fIINTERFACE\fR
Delete the record for network interface \fIINTERFACE\fR.
.PP
The \fIINTERFACE\fR name may not contain spaces, slashes or
initial dots, hyphens or tildes.
.PP
Following the addition or deletion of the record, resolvconf runs
the update scripts as described in the CLIENTS section.
.TP
\fB\-u\fR
Just run the update scripts.
.SH FILES
.TP
.I /etc/resolvconf/run
This is either a directory where nameserver information can be stored
or a symbolic link to such a directory.
Clients should not make any assumptions about the canonical location
of this directory or the hierarchy that is constructed under it.
.TP
.I /etc/resolvconf/interface-order
Determines the order in which nameserver information records are processed.
See
.BR interface-order (5).
.TP
.I /etc/resolvconf/resolv.conf.d/base
File containing basic resolver information.
The lines in this file are included in the resolver configuration file
even when no interfaces are configured.
.TP
.I /etc/resolvconf/resolv.conf.d/head
File to be prepended to the dynamically generated resolver configuration file.
Normally this is just a comment line.
.TP
.I /etc/resolvconf/resolv.conf.d/tail
File to be appended to the dynamically generated resolver configuration file.
To append nothing, make this an empty file.
.SH BUGS
Currently
.B resolvconf
does not check the sanity of the information provided to it.
.SH AUTHOR
Written by Thomas Hood <jdthood at yahoo.co.uk>.
.SH COPYRIGHT
Copyright \(co 2004 Thomas Hood
.br
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
.SH "SEE ALSO"
.BR interface-order (5),
.BR resolv.conf (5),
.BR resolver (3).
--- NEW FILE: translator_russian.add ---
(This appears to be a binary file; contents omitted.)
More information about the l10n-russian-cvs-commits
mailing list