Translation

This line sets the <acronym>NIS</acronym> domain name to <literal>test-domain</literal> and bind to itself.

(itstool) path: callout/para

This line sets the <acronym>NIS</acronym> domain name to <literal>test-domain</literal> and bind to itself.
95/1070
Context English Portuguese (Brazil) State
Physical Server Requirements Requisitos Físicos do Servidor
There are several things to keep in mind when choosing a machine to use as a <acronym>NIS</acronym> server. Since <acronym>NIS</acronym> clients depend upon the availability of the server, choose a machine that is not rebooted frequently. The <acronym>NIS</acronym> server should ideally be a stand alone machine whose sole purpose is to be an <acronym>NIS</acronym> server. If the network is not heavily used, it is acceptable to put the <acronym>NIS</acronym> server on a machine running other services. However, if the <acronym>NIS</acronym> server becomes unavailable, it will adversely affect all <acronym>NIS</acronym> clients. Há várias coisas que você deve ter em mente ao escolher uma máquina para usar como um servidor <acronym>NIS</acronym>. Como os clientes do <acronym>NIS</acronym> dependem da disponibilidade do servidor, escolha uma máquina que não seja reinicializada com freqüência. O servidor do <acronym>NIS</acronym> deve idealmente ser uma máquina autônoma cujo único propósito seja ser um servidor <acronym>NIS</acronym>. Se a rede não for muito usada, é aceitável colocar o servidor <acronym>NIS</acronym> em uma máquina que executa outros serviços. No entanto, se o servidor <acronym>NIS</acronym> ficar indisponível, isso afetará negativamente todos os clientes <acronym>NIS</acronym>.
Configuring the <acronym>NIS</acronym> Master Server Configurando o Servidor <acronym>NIS</acronym> Master
The canonical copies of all <acronym>NIS</acronym> files are stored on the master server. The databases used to store the information are called <acronym>NIS</acronym> maps. In FreeBSD, these maps are stored in <filename>/var/yp/[domainname]</filename> where <filename>[domainname]</filename> is the name of the <acronym>NIS</acronym> domain. Since multiple domains are supported, it is possible to have several directories, one for each domain. Each domain will have its own independent set of maps. As cópias canônicas de todos os arquivos <acronym>NIS</acronym> são armazenadas no servidor master. Os bancos de dados usados para armazenar as informações são chamados de mapas de <acronym>NIS</acronym>. No FreeBSD, estes mapas são armazenados em <filename>/var/yp/[nome_do_domínio]</filename> onde <filename>[nome_do_dominio]</filename> é o nome do domínio <acronym>NIS</acronym>. Como vários domínios são suportados, é possível ter vários diretórios, um para cada domínio. Cada domínio terá seu próprio conjunto independente de mapas.
<acronym>NIS</acronym> master and slave servers handle all <acronym>NIS</acronym> requests through <citerefentry><refentrytitle>ypserv</refentrytitle><manvolnum>8</manvolnum></citerefentry>. This daemon is responsible for receiving incoming requests from <acronym>NIS</acronym> clients, translating the requested domain and map name to a path to the corresponding database file, and transmitting data from the database back to the client. Os servidores master e slave do <acronym>NIS</acronym> lidam com todas as requisições <acronym>NIS</acronym> através do <citerefentry><refentrytitle>ypserv</refentrytitle><manvolnum>8</manvolnum></citerefentry>. Esse daemon é responsável por receber solicitações de entrada de clientes <acronym>NIS</acronym>, traduzindo o domínio e o nome do mapa solicitados para um caminho para o arquivo de banco de dados correspondente e transmitindo dados do banco de dados de volta ao cliente.
<primary>NIS</primary> <secondary>server configuration</secondary> <primary>NIS</primary> <secondary>server configuration</secondary>
Setting up a master <acronym>NIS</acronym> server can be relatively straight forward, depending on environmental needs. Since FreeBSD provides built-in <acronym>NIS</acronym> support, it only needs to be enabled by adding the following lines to <filename>/etc/rc.conf</filename>: Configurar um servidor <acronym>NIS</acronym> master pode ser relativamente simples, dependendo das necessidades ambientais. Como o FreeBSD oferece suporte a <acronym>NIS</acronym> embutido, ele só precisa ser ativado adicionando as seguintes linhas ao arquivo <filename>/etc/rc.conf</filename>:
nisdomainname="<replaceable>test-domain</replaceable>" <co xml:id="network-nis-co-domainname"/>
nis_server_enable="YES" <co xml:id="network-nis-co-server"/>
nis_yppasswdd_enable="YES" <co xml:id="network-nis-co-yppasswdd"/>
nisdomainname="test-domain" <co xml:id="network-nis-co-domainname"/>
nis_server_enable="YES" <co xml:id="network-nis-co-server"/>
nis_yppasswdd_enable="YES" <co xml:id="network-nis-co-yppasswdd"/>
This line sets the <acronym>NIS</acronym> domain name to <literal>test-domain</literal>. Esta linha define o nome de domínio <acronym>NIS</acronym> para <literal>test-domain</literal>.
This automates the start up of the <acronym>NIS</acronym> server processes when the system boots. Isto automatiza o início dos processos do servidor <acronym>NIS</acronym> quando o sistema é inicializado.
This enables the <citerefentry><refentrytitle>rpc.yppasswdd</refentrytitle><manvolnum>8</manvolnum></citerefentry> daemon so that users can change their <acronym>NIS</acronym> password from a client machine. Isso habilita o daemon <citerefentry><refentrytitle>rpc.yppasswdd</refentrytitle><manvolnum>8</manvolnum></citerefentry> para que os usuários possam alterar sua senha <acronym>NIS</acronym> de uma máquina cliente.
Care must be taken in a multi-server domain where the server machines are also <acronym>NIS</acronym> clients. It is generally a good idea to force the servers to bind to themselves rather than allowing them to broadcast bind requests and possibly become bound to each other. Strange failure modes can result if one server goes down and others are dependent upon it. Eventually, all the clients will time out and attempt to bind to other servers, but the delay involved can be considerable and the failure mode is still present since the servers might bind to each other all over again. É preciso ter cuidado em um domínio com vários servidores, no qual as máquinas do servidor também são clientes <acronym>NIS</acronym>. Geralmente, é uma boa ideia forçar os servidores a fazerem bind em si mesmos, em vez de permitir que eles transmitam solicitações de bind e, possivelmente, fiquem vinculados um ao outro. Modos de falha estranhos podem ocorrer se um servidor cair e outros dependerem dele. Eventualmente, todos os clientes terão tempo limite e tentarão fazer bind em outros servidores, mas o atraso envolvido poderá ser considerável e o modo de falha ainda estará presente, uma vez que os servidores podem ligar-se entre si novamente.
A server that is also a client can be forced to bind to a particular server by adding these additional lines to <filename>/etc/rc.conf</filename>: Um servidor que também é um cliente pode ser forçado fazer bind em um servidor em particular adicionando estas linhas adicionais ao arquivo <filename>/etc/rc.conf</filename>:
nis_client_enable="YES" <co xml:id="network-nis-co-client"/>
nis_client_flags="-S <replaceable>test-domain</replaceable>,<replaceable>server</replaceable>" <co xml:id="network-nis-co-clientflags"/>
nis_client_enable="YES" # run client stuff as well
nis_client_flags="-S <replaceable>NIS domain</replaceable>,<replaceable>server</replaceable>"
This enables running client stuff as well.
This line sets the <acronym>NIS</acronym> domain name to <literal>test-domain</literal> and bind to itself. Esta linha define o nome de domínio <acronym>NIS</acronym> para <literal>test-domain</literal>.
After saving the edits, type <command>/etc/netstart</command> to restart the network and apply the values defined in <filename>/etc/rc.conf</filename>. Before initializing the <acronym>NIS</acronym> maps, start <citerefentry><refentrytitle>ypserv</refentrytitle><manvolnum>8</manvolnum></citerefentry>: Depois de salvar as edições, digite <command>/etc/netstart</command> para reiniciar a rede e aplicar os valores definidos no arquivo <filename>/etc/rc.conf</filename>. Antes de inicializar os mapas de <acronym>NIS</acronym>, inicie <citerefentry><refentrytitle>ypserv</refentrytitle><manvolnum>8</manvolnum></citerefentry>:
<prompt>#</prompt> <userinput>service ypserv start</userinput> <prompt>#</prompt> <userinput>service ypserv start</userinput>
Initializing the <acronym>NIS</acronym> Maps Inicializando os mapas do <acronym>NIS</acronym>
<primary>NIS</primary> <secondary>maps</secondary> <primary>NIS</primary> <secondary>maps</secondary>
<acronym>NIS</acronym> maps are generated from the configuration files in <filename>/etc</filename> on the <acronym>NIS</acronym> master, with one exception: <filename>/etc/master.passwd</filename>. This is to prevent the propagation of passwords to all the servers in the <acronym>NIS</acronym> domain. Therefore, before the <acronym>NIS</acronym> maps are initialized, configure the primary password files: Os mapeamentos <acronym>NIS</acronym> são gerados a partir dos arquivos de configuração no diretório <filename>/etc</filename> no <acronym>NIS</acronym> master, com uma exceção: <filename>/etc/master.passwd</filename>. Isso evita a propagação de senhas para todos os servidores no domínio <acronym>NIS</acronym>. Portanto, antes de inicializar os mapas do <acronym>NIS</acronym>, configure os arquivos de senha primários:
<prompt>#</prompt> <userinput>cp /etc/master.passwd /var/yp/master.passwd</userinput>
<prompt>#</prompt> <userinput>cd /var/yp</userinput>
<prompt>#</prompt> <userinput>vi master.passwd</userinput>
<prompt>#</prompt> <userinput>cp /etc/master.passwd /var/yp/master.passwd</userinput>
<prompt>#</prompt> <userinput>cd /var/yp</userinput>
<prompt>#</prompt> <userinput>vi master.passwd</userinput>
It is advisable to remove all entries for system accounts as well as any user accounts that do not need to be propagated to the <acronym>NIS</acronym> clients, such as the <systemitem class="username">root</systemitem> and any other administrative accounts. É aconselhável remover todas as entradas de contas do sistema, bem como quaisquer contas de usuário que não precisem ser propagadas para os clientes do <acronym>NIS</acronym>, como o <systemitem class="username">root</systemitem> e quaisquer outras contas administrativas.
Ensure that the <filename>/var/yp/master.passwd</filename> is neither group or world readable by setting its permissions to <literal>600</literal>. Assegure-se de que o arquivo <filename>/var/yp/master.passwd</filename> não seja de grupo nem de mundo legível, definindo suas permissões para <literal>600</literal>.
After completing this task, initialize the <acronym>NIS</acronym> maps. FreeBSD includes the <citerefentry><refentrytitle>ypinit</refentrytitle><manvolnum>8</manvolnum></citerefentry> script to do this. When generating maps for the master server, include <option>-m</option> and specify the <acronym>NIS</acronym> domain name: Depois de concluir esta tarefa, inicialize os mapas do <acronym>NIS</acronym>. O FreeBSD inclui o script <citerefentry><refentrytitle>ypinit</refentrytitle><manvolnum>8</manvolnum></citerefentry> para fazer isso. Ao gerar mapas para o servidor master, inclua <option>-m</option> e especifique o nome de domínio <acronym>NIS</acronym>:
ellington<prompt>#</prompt> <userinput>ypinit -m test-domain</userinput>
Server Type: MASTER Domain: test-domain
Creating an YP server will require that you answer a few questions.
Questions will all be asked at the beginning of the procedure.
Do you want this procedure to quit on non-fatal errors? [y/n: n] <userinput>n</userinput>
Ok, please remember to go back and redo manually whatever fails.
If not, something might not work.
At this point, we have to construct a list of this domains YP servers.
rod.darktech.org is already known as master server.
Please continue to add any slave servers, one per line. When you are
done with the list, type a &lt;control D&gt;.
master server : ellington
next host to add: <userinput>coltrane</userinput>
next host to add: <userinput>^D</userinput>
The current list of NIS servers looks like this:
ellington
coltrane
Is this correct? [y/n: y] <userinput>y</userinput>

[..output from map generation..]

NIS Map update completed.
ellington has been setup as an YP master server without any errors.
ellington<prompt>#</prompt> <userinput>ypinit -m test-domain</userinput>
Server Type: MASTER Domain: test-domain
Creating an YP server will require that you answer a few questions.
Questions will all be asked at the beginning of the procedure.
Do you want this procedure to quit on non-fatal errors? [y/n: n] <userinput>n</userinput>
Ok, please remember to go back and redo manually whatever fails.
If not, something might not work.
At this point, we have to construct a list of this domains YP servers.
rod.darktech.org is already known as master server.
Please continue to add any slave servers, one per line. When you are
done with the list, type a &lt;control D&gt;.
master server : ellington
next host to add: <userinput>coltrane</userinput>
next host to add: <userinput>^D</userinput>
The current list of NIS servers looks like this:
ellington
coltrane
Is this correct? [y/n: y] <userinput>y</userinput>

[..output from map generation..]

NIS Map update completed.
ellington has been setup as an YP master server without any errors.
This will create <filename>/var/yp/Makefile</filename> from <filename>/var/yp/Makefile.dist</filename>. By default, this file assumes that the environment has a single <acronym>NIS</acronym> server with only FreeBSD clients. Since <literal>test-domain</literal> has a slave server, edit this line in <filename>/var/yp/Makefile</filename> so that it begins with a comment (<literal>#</literal>): Isto irá criar <filename>/var/yp/Makefile</filename> a partir de <filename>/var/yp/Makefile.dist</filename>. Por padrão, este arquivo assume que o ambiente tem um único servidor <acronym>NIS</acronym> com apenas clientes FreeBSD. Como <literal>test-domain</literal> tem um servidor slave, edite esta linha no arquivo <filename>/var/yp/Makefile</filename> para que comece com um comentário (<literal> # </literal>) :
NOPUSH = "True" NOPUSH = "True"
Adding New Users Adicionando novos usuários
Every time a new user is created, the user account must be added to the master <acronym>NIS</acronym> server and the <acronym>NIS</acronym> maps rebuilt. Until this occurs, the new user will not be able to login anywhere except on the <acronym>NIS</acronym> master. For example, to add the new user <systemitem class="username">jsmith</systemitem> to the <literal>test-domain</literal> domain, run these commands on the master server: Toda vez que um novo usuário é criado, a conta de usuário deve ser adicionada ao servidor mestre <acronym>NIS</acronym> e aos mapeamentos do <acronym>NIS</acronym> reconstruídos. Até que isso ocorra, o novo usuário não poderá efetuar login em nenhum lugar, exceto no <acronym>NIS</acronym> master. Por exemplo, para adicionar o novo usuário <systemitem class="username">jsmith</systemitem> ao domínio <literal>test-domain</literal>, execute estes comandos no servidor master:
<prompt>#</prompt> <userinput>pw useradd jsmith</userinput>
<prompt>#</prompt> <userinput>cd /var/yp</userinput>
<prompt>#</prompt> <userinput>make test-domain</userinput>
<prompt>#</prompt> <userinput>pw useradd jsmith</userinput>
<prompt>#</prompt> <userinput>cd /var/yp</userinput>
<prompt>#</prompt> <userinput>make test-domain</userinput>

Loading…

User avatar None

Source string changed

FreeBSD Doc / books_handbookPortuguese (Brazil)

This line sets the <acronym>NIS</acronym> domain name to <literal>test-domain</literal> and bind to itself.
3 months ago
Browse all component changes

Glossary

English Portuguese (Brazil)
No related strings found in the glossary.

Source information

Source string comment

(itstool) path: callout/para

Source string location
book.translate.xml:54351
String age
3 months ago
Source string age
3 months ago
Translation file
books/pt_BR/handbook.po, string 8897