Changeset 33

Show
Ignore:
Timestamp:
07/28/09 21:50:30 (3 years ago)
Author:
hiei
Message:

Parciais de chap3.po, chap4.po e app5.po

Location:
trunk/l10n/guide/docbook/Intro-Linux
Files:
3 modified

Legend:

Unmodified
Added
Removed

  • trunk/l10n/guide/docbook/Intro-Linux/app5.po

    r7 r33  
     1# Brazilian Portuguese translation of Introduction to Linux - A Hands on Guide 
     2# LDP-BR Linux Team - Projeto de Documentação Gnome 
     3# Enrico Nicoletto <liverig@gmail.com>, 2009. 
     4# 
    15msgid "" 
    26msgstr "" 
    3 "Project-Id-Version: PACKAGE VERSION\n" 
     7"Project-Id-Version: Introduction to Linux - A Hands on Guide\n" 
    48"POT-Creation-Date: 2008-07-24 01:30-0300\n" 
    5 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" 
    6 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" 
     9"PO-Revision-Date: 2009-07-24 12:38-0300\n" 
     10"Last-Translator: Enrico Nicoletto <liverig@gmail.com>\n" 
    711"Language-Team: LANGUAGE <LL@li.org>\n" 
    812"MIME-Version: 1.0\n" 
    … …  
    1216#: ../app5.xml:2(title) 
    1317msgid "proc.txt" 
    14 msgstr "" 
     18msgstr "proc.txt" 
    1519 
    1620#: ../app5.xml:3(para) 
    17 msgid "" 
    18 "This appendix holds the file proc.txt, which explains the <filename>proc</" 
    19 "filename> file system on Linux machines." 
    20 msgstr "" 
     21msgid "This appendix holds the file proc.txt, which explains the <filename>proc</filename> file system on Linux machines." 
     22msgstr "Este apêndice acompanha o arquivo proc.txt, que explica o sistema de arquivo <filename>proc</filename> em máquinas LInux." 
    2123 
    2224#: ../app5.xml:4(title) 
    2325msgid "The /proc Filesystem" 
    24 msgstr "" 
     26msgstr "O arquivo de sistema /proc" 
    2527 
    2628#: ../app5.xml:5(para) 
    27 msgid "" 
    28 "This appendix contains a file from the documentation that comes with your " 
    29 "Linux system, the <filename>proc.txt</filename> file. It explains in detail " 
    30 "the contents of the <filename>/proc</filename> directory on your system. " 
    31 "You'll find this directory very helpful for gathering system information." 
    32 msgstr "" 
     29msgid "This appendix contains a file from the documentation that comes with your Linux system, the <filename>proc.txt</filename> file. It explains in detail the contents of the <filename>/proc</filename> directory on your system. You'll find this directory very helpful for gathering system information." 
     30msgstr "Este apêndice contém um arquivo da documentação que vem com o seu sistema Linux, o arquivo <filename>proc.txt</filename>. O apêndice explica em detalhes os conteúdos do diretório <filename>/proc</filename> no seu sistema. Você vai achar este diretório muito útil para obter informações do sistema." 
    3331 
    3432#: ../app5.xml:6(screen) 
    … …  
    3735"\n" 
    3836"------------------------------------------------------------------------------\n" 
    39 "                       T H E  /proc   F I L E S Y S T E M\n" 
    40 "------------------------------------------------------------------------------\n" 
    41 "/proc/sys         Terrehon Bowden &lt;terrehon@pacbell.net&gt;        October 7 1999\n" 
     37"         O   A R Q U I V O   D E   S I S T E M A   /proc \n" 
     38"------------------------------------------------------------------------------\n" 
     39"/proc/sys         Terrehon Bowden &lt;terrehon@pacbell.net&gt;     7 Out. 1999\n" 
    4240"                  Bodo Bauer &lt;bb@ricochet.net&gt;\n" 
    4341"\n" 
    44 "2.4.x update\t  Jorge Nerin &lt;comandante@zaralinux.com&gt;      November 14 2000\n" 
    45 "------------------------------------------------------------------------------\n" 
    46 "Version 1.3                                              Kernel version 2.2.12\n" 
     42"atualização 2.4.x\t  Jorge Nerin &lt;comandante@zaralinux.com&gt; 14 Nov. 2000\n" 
     43"------------------------------------------------------------------------------\n" 
     44"Versão 1.3                                            Versão do Kernel: 2.2.12\n" 
    4745"\t\t\t\t\t      Kernel version 2.4.0-test11-pre4\n" 
    4846"------------------------------------------------------------------------------\n" 
    4947"\n" 
    50 "Table of Contents\n" 
     48"Índice Remissivo\n" 
    5149"-----------------\n" 
    5250"\n" 
    53 "  0     Preface\n" 
    54 "  0.1\tIntroduction/Credits\n" 
     51"  0     Prefácio\n" 
     52"  0.1\tIntrodução/Créditos\n" 
     53"  0.2\tConteúdo Legal\n" 
     54"\n" 
     55"  1\tColetando informações do sistema\n" 
     56"  1.1\tSubdiretórios de processo específico\n" 
     57"  1.2\tDados do Kernel\n" 
     58"  1.3\tDispositivos IDE em /proc/ide\n" 
     59"  1.4\tInformações de rede em /proc/net\n" 
     60"  1.5\tInformações sobre SCSI\n" 
     61"  1.6\tInformações sobre portas paralelas em /proc/parport\n" 
     62"  1.7\tInformações sobre TTY em /proc/tty\n" 
     63"\n" 
     64"  2\tModificando parâmetros de sistema\n" 
     65"  2.1\t/proc/sys/fs - Dados do arquivo de sistema\n" 
     66"  2.2\t/proc/sys/fs/binfmt_misc - Outros formatos binários\n" 
     67"  2.3\t/proc/sys/kernel - Parâmetros comuns de kernel\n" 
     68"  2.4\t/proc/sys/vm - O subsistema de memória virtual\n" 
     69"  2.5\t/proc/sys/dev - Parâmetros específicos de Dispositivo\n" 
     70"  2.6\t/proc/sys/sunrpc - Chamadas de procedimento remoto\n" 
     71"  2.7\t/proc/sys/net - Materiais de Rede\n" 
     72"  2.8\t/proc/sys/net/ipv4 - Configurações de IPV4\n" 
     73"  2.9\tAppletalk\n" 
     74"  2.10\tIPX\n" 
     75"\n" 
     76"------------------------------------------------------------------------------\n" 
     77"Prefácio\n" 
     78"------------------------------------------------------------------------------\n" 
     79"\n" 
     80"0.1 Introdução/Créditos\n" 
     81"------------------------\n" 
     82"\n" 
     83"Esta documentação é parte de um livro que em breve será lançado (ou assim esperamos)\n" 
     84"na distribuição SUSE do Linux. Como não há uma documentação completa para o arquivo\n" 
     85"de sistema /proc e como nós utilizamos muito livremente fontes disponíveis para\n" 
     86"escrever estes capítulos, parece-nos justo atribuir o trabalho apenas à comunidade Linux.\n" 
     87"Este trabalho é baseado no kernel versão 2.2.*  e o próximo versão 2.4.*. Estou com medo\n" 
     88"que ainda esteja longe de terminar, mas nós acreditamos que isto será útil. Pelo que nós\n" 
     89"sabemos, este é o primeiro documento 'tudo-em-um' sobre o sistema de arquivo /proc. Ele \n" 
     90"é focado no hardware x86 da Intel, então se você está procurando por características PPC,\n" 
     91"ARM, SPARC, APX e etc, você provavelmente não encontrará o que está procurando.\n" 
     92"Esta documentação apenas abrange as redes IPv4, nem a IPv6 nem outros protocolos - foi mal\n" 
     93"Mas suplementos e correções são bem vindos e serão adicionados a este documento se você\n" 
     94"enviá-los ao Bodo.\n" 
     95"\n" 
     96"Nós gostariamos de agradecer Alan Cox, Rik van Riel, Alexey Kuznetsov e um monte de outras\n" 
     97"pessoas por ajudarem a compilar esta documentação. Nós gostaríamos também de estender um\n" 
     98"agradecimento especial para Andi Kleen pela documentação, que nós nos baseamos profundamente\n" 
     99"para criar este documento,  assim como as informações adicionais que ele nos fornceu.\n" 
     100"Obrigado a qualquer um que contribuiu fontes ou documentações para o kernel do Linux e\n" 
     101"ajudou a criar um ótimo pedaço de software... :)\n" 
     102"\n" 
     103"Se você possui quaisquer comentários, correções ou acréscimos, por favor não hesite em entrar\n" 
     104"em contato com Bodo  Bauer  em  bb@ricochet.net.  Nós ficaremos felizes em adicioná-los a este\n" 
     105"documento.\n" 
     106"\n" 
     107"A versão mais recente deste documento está disponível on-line em\n" 
     108"http://skaro.nightcrawler.com/~bb/Docs/Proc como versão HTML.\n" 
     109"\n" 
     110"Se o endereço de cima não funcionar pra você,  você pode tentar a lista de\n" 
     111"e-mail do kernel em  linux-kernel@vger.kernel.org e/ou tentar me achar em\n" 
     112"comandante@zaralinux.com.\n" 
     113"\n" 
     114"0.2 Conteúdo Legal\n" 
     115"---------------\n" 
     116"\n" 
     117"Nós não garantimos a veracidade deste documento, e se você vier a nós reclamando\n" 
     118"sobre como você estragou seus sistema por causa de documentação incorreta\n" 
     119"nós não nos sentiremos responsáveis...\n" 
     120"\n" 
     121"------------------------------------------------------------------------------\n" 
     122"CAPÍTULO 1: COLETANDO INFORMAÇÕES DO SISTEMA\n" 
     123"------------------------------------------------------------------------------\n" 
     124"\n" 
     125"------------------------------------------------------------------------------\n" 
     126"Neste capítulo \n" 
     127"------------------------------------------------------------------------------\n" 
     128"* Investigando as propriedades do pseudo-sistema de arquivos /proc e sua\n" 
     129"  habilidade em fornecer  informações  nos  sitemas  Linux  em  execução\n" 
     130"* Examinando a estrutura do /proc\n" 
     131"* Descobrindo  várias  informações sobre o kernel e os processos rodando\n" 
     132"  no sistema\n" 
     133"------------------------------------------------------------------------------\n" 
     134"\n" 
     135"\n" 
     136"O  sistema  de  arquivo  proc atua como uma interface para estruturas de dados\n" 
     137"internas no kernel. Isto pode ser usado para obter informações sobre o sistema\n" 
     138"e  para  alterar  certos  parâmetros do  kernel no tempo de execução (sysctl).\n" 
     139"\n" 
     140"Primeiro  nós  daremos  uma  olhada  nas  partes  somente  leitura  do  /proc.\n" 
     141"No  Capítulo  2  mostraremos  como  você  pode  usar /proc/sys para alterar as\n" 
     142"configurações.\n" 
     143"\n" 
     144"1.1 Subdiretórios de processo específico\n" 
     145"----------------------------------------\n" 
     146"\n" 
     147"O diretório  /proc  contém  (além de outras coisas) um  subdiretório para cada\n" 
     148"processo em execução no sistema, que é nomeado depois do ID do processo (PID).\n" 
     149"\n" 
     150"O próprio link aponta para o processo lendo o sistema de arquivo. Cada processo\n" 
     151"do subdiretório possui suas entradas listadas na Tabela 1-1.\n" 
     152"\n" 
     153"\n" 
     154"Tabela 1-1: Entradas de processo específico em /proc \n" 
     155"..............................................................................\n" 
     156" Arquivo  Conteúdo                                       \n" 
     157" cmdline  Argumentos de linha de comando                 \n" 
     158" cpu\t    A última e atual cpu no qual foi executado\t\t(2.4)(smp)\n" 
     159" cwd\t    Link para o diretório de trabalho atual \n" 
     160" environ  Valores das variáveis de ambiente       \n" 
     161" exe\t    Link para o executável deste processo   \n" 
     162" fd       Diretório, que contém todos os descritores de arquivo \n" 
     163" maps\t   Mapas de memória para executáveis e arquivos de biblioteca\t\t(2.4)\n" 
     164" mem      Memória retida por este processo               \n" 
     165" root\t   Link para o diretório raiz deste processo      \n" 
     166" stat     Status do processo                             \n" 
     167" statm    Informações do status de memória do processo   \n" 
     168" status   Status do processo em forma legível p/ humanos \n" 
     169"..............................................................................\n" 
     170"\n" 
     171"Por exemplo, para obter informações sobre o status de um processo, tudo o que você tem que fazer é\n" 
     172"ler o arquivo /proc/PID/status:\n" 
     173"\n" 
     174"  &gt;cat /proc/self/status \n" 
     175"  Name:   cat \n" 
     176"  State:  R (rodando) \n" 
     177"  Pid:    5452 \n" 
     178"  PPid:   743 \n" 
     179"  TracerPid:      0\t\t\t\t\t\t(2.4)\n" 
     180"  Uid:    501     501     501     501 \n" 
     181"  Gid:    100     100     100     100 \n" 
     182"  Groups: 100 14 16 \n" 
     183"  VmSize:     1112 kB \n" 
     184"  VmLck:         0 kB \n" 
     185"  VmRSS:       348 kB \n" 
     186"  VmData:       24 kB \n" 
     187"  VmStk:        12 kB \n" 
     188"  VmExe:         8 kB \n" 
     189"  VmLib:      1044 kB \n" 
     190"  SigPnd: 0000000000000000 \n" 
     191"  SigBlk: 0000000000000000 \n" 
     192"  SigIgn: 0000000000000000 \n" 
     193"  SigCgt: 0000000000000000 \n" 
     194"  CapInh: 00000000fffffeff \n" 
     195"  CapPrm: 0000000000000000 \n" 
     196"  CapEff: 0000000000000000 \n" 
     197"\n" 
     198"\n" 
     199"Isto mostra quase as mesmas informações que você teria  se  você  visualizasse\n" 
     200"isso com o comando ps. De fato, ps usa o sistema de arquivo proc para obter suas\n" 
     201"informações. O arquivo statm contém informações mais detalhadas sobre o processo\n" 
     202"de uso de memória. Seus sete campos são explicados na Tabela 1-2.\n" 
     203"\n" 
     204"\n" 
     205"Tabela 1-2: Conteúdo dos arquivos statm \n" 
     206"..............................................................................\n" 
     207" Arquivo   Conteúdo                        \n" 
     208" size      tamanho total do programa       \n" 
     209" resident  tamanho de porções de memória   \n" 
     210" shared    número de páginas compartilhadas\n" 
     211" trs       número de páginas em 'código'   \n" 
     212" drs       número de páginas de data/stack \n" 
     213" lrs       número de páginas de biblioteca \n" 
     214" dt        número de páginas danificadas   \n" 
     215"..............................................................................\n" 
     216"\n" 
     217"1.2 Dados do Kernel\n" 
     218"---------------\n" 
     219"\n" 
     220"Semelhante às entradas de processo, os arquivos de dados do kernel fornecem\n" 
     221"informações sobre o kernel em execução. Os arquivos utilizados para obter estas\n" 
     222"informações estão contidos no /proc e são listadas na Tabela 1-3. Nem todos eles\n" 
     223"estarão presentes no seu sistema. Isto depende da configuração do kernel e dos\n" 
     224"módulos carregados, que arquivos estão lá e quais estão faltando.\n" 
     225"\n" 
     226"Tabela 1-3: Informações do Kernel em /proc \n" 
     227"..............................................................................\n" 
     228" Arquivo     Conteúdo                                                \n" 
     229" apm         Informações avançadas de gerenciamento de energia       \n" 
     230" bus         Diretório contendo informações específicas de barramento\n" 
     231" cmdline     Linha de comando do Kernel                              \n" 
     232" cpuinfo     Informações sobre a CPU                                 \n" 
     233" devices     Dispositivos disponíveis (bloco e caractere)            \n" 
     234" dma         Canais DMS utilizados                                   \n" 
     235" filesystems Sistemas de arquivo suportados                          \n" 
     236" driver\t    Vários drivers agrupados aqui, atualmente rtc\t(2.4)\n" 
     237" execdomains Domínios de execução, relacionados à segurança\t\t\t(2.4)\n" 
     238" fb\t        Dispositivos Frame Buffer\t\t\t\t(2.4)\n" 
     239" fs\t        Parâmetros de sistema de arquivos, atualmente exportações/nfs\t(2.4)\n" 
     240" ide         Diretório contendo informações sobre o subsistema IDE   \n" 
     241" interrupts  Utilizado para interrupções                             \n" 
     242" iomem\t     Mapa de memória\t\t\t\t\t\t(2.4)\n" 
     243" ioports     Uso de portas de E/S                                    \n" 
     244" irq\t       Máscaras de irq para aproximar-se da cpu \t\t\t(2.4)(smp?)\n" 
     245" isapnp\t    Informações sobre ISA PnP (Plug&amp;Play)\t\t\t\t(2.4)    \n" 
     246" kcore       Kernel core image (can be ELF or A.OUT(deprecated in 2.4))\n" 
     247" kmsg        Mensagens do Kernel                               \n" 
     248" ksyms       Tabela de símbolos do Kernel                      \n" 
     249" loadavg     Carregar média do(s) último(s) 1, 5 e 15 minutos  \n" 
     250" locks       Travamentos de Kernel                             \n" 
     251" meminfo     Informações de Memória                            \n" 
     252" misc        Outros                                            \n" 
     253" modules     Lista de módulos carregados                       \n" 
     254" mounts      Sistemas de arquivo montados                      \n" 
     255" net         Informações de rede (ver o texto)                 \n" 
     256" partitions  Tabela de partições conhecidas pelo sistema       \n" 
     257" pci\t       Informações depreciativas do barramento PCI (novo modo -&gt; /proc/bus/pci/, \n" 
     258"             dissociado pelo lspci\t\t\t\t\t(2.4)\n" 
     259" rtc         Relógio em tempo real                             \n" 
     260" scsi        Informações sobre SCSI (ver o texto)              \n" 
     261" slabinfo    Informações sobre slab pool                       \n" 
     262" stat        Estatísticas globais                              \n" 
     263" swaps       Utilização de espaço Swap                         \n" 
     264" sys         Veja o capítulo 2                                 \n" 
     265" sysvipc     Informações sobre recursos SysVIPC (msg, sem, shm)\t\t(2.4)\n" 
     266" tty\t       Informações de drivers tty\n" 
     267" uptime      Tempo de funcionamento do sistema                 \n" 
     268" version     Versão do Kernel                                  \n" 
     269" video\t     bttv - informações de recursos de vídeo\t\t\t(2.4)\n" 
     270"..............................................................................\n" 
     271"\n" 
     272"Você pode,  por  exemplo,  checar quais interrupções estão atualmente em uso e no quê\n" 
     273"elas são usadas por quem, olhando o arquivo /proc/interrupts:\n" 
     274"\n" 
     275"  &gt; cat /proc/interrupts \n" 
     276"             CPU0        \n" 
     277"    0:    8728810          XT-PIC  timer \n" 
     278"    1:        895          XT-PIC  teclado \n" 
     279"    2:          0          XT-PIC  cascade \n" 
     280"    3:     531695          XT-PIC  aha152x \n" 
     281"    4:    2014133          XT-PIC  serial \n" 
     282"    5:      44401          XT-PIC  pcnet_cs \n" 
     283"    8:          2          XT-PIC  rtc \n" 
     284"   11:          8          XT-PIC  i82365 \n" 
     285"   12:     182918          XT-PIC  Mouse PS/2 \n" 
     286"   13:          1          XT-PIC  fpu \n" 
     287"   14:    1232265          XT-PIC  ide0 \n" 
     288"   15:          7          XT-PIC  ide1 \n" 
     289"  NMI:          0 \n" 
     290"\n" 
     291"In 2.4.* um par de linhas foram adicionadas ao arquivo LOC &amp; ERR (desta vez é a\n" 
     292"saída de uma máquina SMP):\n" 
     293"\n" 
     294"  &gt; cat /proc/interrupts \n" 
     295"\n" 
     296"             CPU0       CPU1       \n" 
     297"    0:    1243498    1214548    IO-APIC-edge  timer\n" 
     298"    1:       8949       8958    IO-APIC-edge  teclado\n" 
     299"    2:          0          0          XT-PIC  cascade\n" 
     300"    5:      11286      10161    IO-APIC-edge  soundblaster\n" 
     301"    8:          1          0    IO-APIC-edge  rtc\n" 
     302"    9:      27422      27407    IO-APIC-edge  3c503\n" 
     303"   12:     113645     113873    IO-APIC-edge  Mouse PS/2\n" 
     304"   13:          0          0          XT-PIC  fpu\n" 
     305"   14:      22491      24012    IO-APIC-edge  ide0\n" 
     306"   15:       2183       2415    IO-APIC-edge  ide1\n" 
     307"   17:      30564      30414   IO-APIC-level  eth0\n" 
     308"   18:        177        164   IO-APIC-level  bttv\n" 
     309"  NMI:    2457961    2457959 \n" 
     310"  LOC:    2457882    2457881 \n" 
     311"  ERR:       2155\n" 
     312"\n" 
     313"NMI is incremented in this case because every timer interrupt generates a NMI\n" 
     314"(Non Maskable Interrupt) which is used by the NMI Watchdog to detect lookups.\n" 
     315"\n" 
     316"LOC is the local interrupt counter of the internal APIC of every CPU.\n" 
     317"\n" 
     318"ERR is incremented in the case of errors in the IO-APIC bus (the bus that\n" 
     319"connects the CPUs in a SMP system. This means that an error has been detected,\n" 
     320"the IO-APIC automatically retry the transmission, so it should not be a big\n" 
     321"problem, but you should read the SMP-FAQ.\n" 
     322"\n" 
     323"In this context it could be interesting to note the new irq directory in 2.4.\n" 
     324"It could be used to set IRQ to CPU affinity, this means that you can \"hook\" an\n" 
     325"IRQ to only one CPU, or to exclude a CPU of handling IRQs. The contents of the\n" 
     326"irq subdir is one subdir for each IRQ, and one file; prof_cpu_mask\n" 
     327"\n" 
     328"Por exemplo: \n" 
     329"  &gt; ls /proc/irq/\n" 
     330"  0  10  12  14  16  18  2  4  6  8  prof_cpu_mask\n" 
     331"  1  11  13  15  17  19  3  5  7  9\n" 
     332"  &gt; ls /proc/irq/0/\n" 
     333"  smp_affinity\n" 
     334"\n" 
     335"The contents of the prof_cpu_mask file and each smp_affinity file for each IRQ\n" 
     336"is the same by default:\n" 
     337"\n" 
     338"  &gt; cat /proc/irq/0/smp_affinity \n" 
     339"  ffffffff\n" 
     340"\n" 
     341"It's a bitmask, in wich you can specify wich CPUs can handle the IRQ, you can\n" 
     342"set it by doing:\n" 
     343"\n" 
     344"  &gt; echo 1 &gt; /proc/irq/prof_cpu_mask\n" 
     345"\n" 
     346"This means that only the first CPU will handle the IRQ, but you can also echo 5\n" 
     347"wich means that only the first and fourth CPU can handle the IRQ.\n" 
     348"\n" 
     349"The way IRQs are routed is handled by the IO-APIC, and it's Round Robin\n" 
     350"between all the CPUs which are allowed to handle it. As usual the kernel has\n" 
     351"more info than you and does a better job than you, so the defaults are the\n" 
     352"best choice for almost everyone.\n" 
     353"\n" 
     354"There are  three  more  important subdirectories in /proc: net, scsi, and sys.\n" 
     355"The general  rule  is  that  the  contents,  or  even  the  existence of these\n" 
     356"directories, depend  on your kernel configuration. If SCSI is not enabled, the\n" 
     357"directory scsi  may  not  exist. The same is true with the net, which is there\n" 
     358"only when networking support is present in the running kernel.\n" 
     359"\n" 
     360"The slabinfo  file  gives  information  about  memory usage at the slab level.\n" 
     361"Linux uses  slab  pools for memory management above page level in version 2.2.\n" 
     362"Commonly used  objects  have  their  own  slab  pool (such as network buffers,\n" 
     363"directory cache, and so on).\n" 
     364"\n" 
     365"1.3 Dispositivos IDE em /proc/ide\n" 
     366"----------------------------\n" 
     367"\n" 
     368"The subdirectory /proc/ide contains information about all IDE devices of which\n" 
     369"the kernel  is  aware.  There is one subdirectory for each IDE controller, the\n" 
     370"file drivers  and a link for each IDE device, pointing to the device directory\n" 
     371"in the controller specific subtree.\n" 
     372"\n" 
     373"The file  drivers  contains general information about the drivers used for the\n" 
     374"IDE devices:\n" 
     375"\n" 
     376"  &gt; cat /proc/ide/drivers \n" 
     377"  ide-cdrom version 4.53 \n" 
     378"  ide-disk version 1.08 \n" 
     379"\n" 
     380"\n" 
     381"More detailed  information  can  be  found  in  the  controller  specific\n" 
     382"subdirectories. These  are  named  ide0,  ide1  and  so  on.  Each  of  these\n" 
     383"directories contains the files shown in table 1-4.\n" 
     384"\n" 
     385"\n" 
     386"Tabela 1-4: Informações do controlador IDE em  /proc/ide/ide? \n" 
     387"..............................................................................\n" 
     388" Arquivo   Conteúdo                                \n" 
     389" channel   Canal IDE (0 ou 1)                      \n" 
     390" config    Configuração (apenas para ponte PCI/IDE)\n" 
     391" mate      Mate name                               \n" 
     392" model     Tipo/Chipset do controlador IDE         \n" 
     393"..............................................................................\n" 
     394"\n" 
     395"Each device  connected  to  a  controller  has  a separate subdirectory in the\n" 
     396"controllers directory.  The  files  listed in table 1-5 are contained in these\n" 
     397"directories.\n" 
     398"\n" 
     399"\n" 
     400"Tabela 1-5: Informações sobre dispositivos IDE \n" 
     401"..............................................................................\n" 
     402" File             Content                                    \n" 
     403" cache            O cache                                    \n" 
     404" capacity         Capacidade da mídia (em blocos de 512Byte) \n" 
     405" driver           driver e versão                            \n" 
     406" geometry         geometria física e lógica                  \n" 
     407" identify         device identify block                      \n" 
     408" media            tipo da mídia                              \n" 
     409" model            device identifier                          \n" 
     410" settings         device setup                               \n" 
     411" smart_thresholds IDE disk management thresholds             \n" 
     412" smart_values     IDE disk management values                 \n" 
     413"..............................................................................\n" 
     414"\n" 
     415"The most  interesting  file is settings. This file contains a nice overview of\n" 
     416"the drive parameters:\n" 
     417"\n" 
     418"  # cat /proc/ide/ide0/hda/settings \n" 
     419"  name                    value           min             max             mode \n" 
     420"  ----                    -----           ---             ---             ---- \n" 
     421"  bios_cyl                526             0               65535           rw \n" 
     422"  bios_head               255             0               255             rw \n" 
     423"  bios_sect               63              0               63              rw \n" 
     424"  breada_readahead        4               0               127             rw \n" 
     425"  bswap                   0               0               1               r \n" 
     426"  file_readahead          72              0               2097151         rw \n" 
     427"  io_32bit                0               0               3               rw \n" 
     428"  keepsettings            0               0               1               rw \n" 
     429"  max_kb_per_request      122             1               127             rw \n" 
     430"  multcount               0               0               8               rw \n" 
     431"  nice1                   1               0               1               rw \n" 
     432"  nowerr                  0               0               1               rw \n" 
     433"  pio_mode                write-only      0               255             w \n" 
     434"  slow                    0               0               1               rw \n" 
     435"  unmaskirq               0               0               1               rw \n" 
     436"  using_dma               0               0               1               rw \n" 
     437"\n" 
     438"\n" 
     439"1.4 Networking info in /proc/net\n" 
     440"--------------------------------\n" 
     441"\n" 
     442"The subdirectory  /proc/net  follows  the  usual  pattern. Table 1-6 shows the\n" 
     443"additional values  you  get  for  IP  version 6 if you configure the kernel to\n" 
     444"support this. Table 1-7 lists the files and their meaning.\n" 
     445"\n" 
     446"\n" 
     447"Table 1-6: IPv6 info in /proc/net \n" 
     448"..............................................................................\n" 
     449" Arquivo    Conteúdo                                              \n" 
     450" udp6       Soquetes UDP (IPv6)                                   \n" 
     451" tcp6       Soquetes TCP (IPv6)                                   \n" 
     452" raw6       Raw device statistics (IPv6)                          \n" 
     453" igmp6      IP multicast addresses, which this host joined (IPv6) \n" 
     454" if_inet6   List of IPv6 interface addresses                      \n" 
     455" ipv6_route Kernel routing table for IPv6                         \n" 
     456" rt6_stats  Global IPv6 routing tables statistics                 \n" 
     457" sockstat6  Socket statistics (IPv6)                              \n" 
     458" snmp6      Snmp data (IPv6)                                      \n" 
     459"..............................................................................\n" 
     460"\n" 
     461"\n" 
     462"Tabela 1-7: Informações de rede em /proc/net \n" 
     463"..............................................................................\n" 
     464" Arquivo       Conteúdo                                                        \n" 
     465" arp           Kernel  ARP table                                               \n" 
     466" dev           network devices with statistics                                 \n" 
     467" dev_mcast     the Layer2 multicast groups a device is listening too\n" 
     468"               (interface index, label, number of references, number of bound\n" 
     469"               addresses). \n" 
     470" dev_stat      network device status                                           \n" 
     471" ip_fwchains   Firewall chain linkage                                          \n" 
     472" ip_fwnames    Firewall chain names                                            \n" 
     473" ip_masq       Directory containing the masquerading tables                    \n" 
     474" ip_masquerade Major masquerading table                                        \n" 
     475" netstat       Network statistics                                              \n" 
     476" raw           raw device statistics                                           \n" 
     477" route         Kernel routing table                                            \n" 
     478" rpc           Directory containing rpc info                                   \n" 
     479" rt_cache      Routing cache                                                   \n" 
     480" snmp          SNMP data                                                       \n" 
     481" sockstat      Socket statistics                                               \n" 
     482" tcp           TCP  sockets                                                    \n" 
     483" tr_rif        Token ring RIF routing table                                    \n" 
     484" udp           UDP sockets                                                     \n" 
     485" unix          UNIX domain sockets                                             \n" 
     486" wireless      Wireless interface data (Wavelan etc)                           \n" 
     487" igmp          IP multicast addresses, which this host joined                  \n" 
     488" psched        Global packet scheduler parameters.                             \n" 
     489" netlink       List of PF_NETLINK sockets                                      \n" 
     490" ip_mr_vifs    List of multicast virtual interfaces                            \n" 
     491" ip_mr_cache   List of multicast routing cache                                 \n" 
     492"..............................................................................\n" 
     493"\n" 
     494"You can  use  this  information  to see which network devices are available in\n" 
     495"your system and how much traffic was routed over those devices:\n" 
     496"\n" 
     497"  &gt; cat /proc/net/dev \n" 
     498"  Inter-|Receive                                                   |[... \n" 
     499"   face |bytes    packets errs drop fifo frame compressed multicast|[... \n" 
     500"      lo:  908188   5596     0    0    0     0          0         0 [...         \n" 
     501"    ppp0:15475140  20721   410    0    0   410          0         0 [...  \n" 
     502"    eth0:  614530   7085     0    0    0     0          0         1 [... \n" 
     503"   \n" 
     504"  ...] Transmit \n" 
     505"  ...] bytes    packets errs drop fifo colls carrier compressed \n" 
     506"  ...]  908188     5596    0    0    0     0       0          0 \n" 
     507"  ...] 1375103    17405    0    0    0     0       0          0 \n" 
     508"  ...] 1703981     5535    0    0    0     3       0          0 \n" 
     509"\n" 
     510"In addition, each Channel Bond interface has it's own directory.  For\n" 
     511"example, the bond0 device will have a directory called /proc/net/bond0/.\n" 
     512"It will contain information that is specific to that bond, such as the\n" 
     513"current slaves of the bond, the link status of the slaves, and how\n" 
     514"many times the slaves link has failed.\n" 
     515"\n" 
     516"1.5 SCSI info\n" 
     517"-------------\n" 
     518"\n" 
     519"If you  have  a  SCSI  host adapter in your system, you'll find a subdirectory\n" 
     520"named after  the driver for this adapter in /proc/scsi. You'll also see a list\n" 
     521"of all recognized SCSI devices in /proc/scsi:\n" 
     522"\n" 
     523"  &gt;cat /proc/scsi/scsi \n" 
     524"  Attached devices: \n" 
     525"  Host: scsi0 Channel: 00 Id: 00 Lun: 00 \n" 
     526"    Vendor: IBM      Model: DGHS09U          Rev: 03E0 \n" 
     527"    Type:   Direct-Access                    ANSI SCSI revision: 03 \n" 
     528"  Host: scsi0 Channel: 00 Id: 06 Lun: 00 \n" 
     529"    Vendor: PIONEER  Model: CD-ROM DR-U06S   Rev: 1.04 \n" 
     530"    Type:   CD-ROM                           ANSI SCSI revision: 02 \n" 
     531"\n" 
     532"\n" 
     533"The directory  named  after  the driver has one file for each adapter found in\n" 
     534"the system.  These  files  contain information about the controller, including\n" 
     535"the used  IRQ  and  the  IO  address range. The amount of information shown is\n" 
     536"dependent on  the adapter you use. The example shows the output for an Adaptec\n" 
     537"AHA-2940 SCSI adapter:\n" 
     538"\n" 
     539"  &gt; cat /proc/scsi/aic7xxx/0 \n" 
     540"   \n" 
     541"  Adaptec AIC7xxx driver version: 5.1.19/3.2.4 \n" 
     542"  Compile Options: \n" 
     543"    TCQ Enabled By Default : Disabled \n" 
     544"    AIC7XXX_PROC_STATS     : Disabled \n" 
     545"    AIC7XXX_RESET_DELAY    : 5 \n" 
     546"  Adapter Configuration: \n" 
     547"             SCSI Adapter: Adaptec AHA-294X Ultra SCSI host adapter \n" 
     548"                             Ultra Wide Controller \n" 
     549"      PCI MMAPed I/O Base: 0xeb001000 \n" 
     550"   Adapter SEEPROM Config: SEEPROM found and used. \n" 
     551"        Adaptec SCSI BIOS: Enabled \n" 
     552"                      IRQ: 10 \n" 
     553"                     SCBs: Active 0, Max Active 2, \n" 
     554"                           Allocated 15, HW 16, Page 255 \n" 
     555"               Interrupts: 160328 \n" 
     556"        BIOS Control Word: 0x18b6 \n" 
     557"     Adapter Control Word: 0x005b \n" 
     558"     Extended Translation: Enabled \n" 
     559"  Disconnect Enable Flags: 0xffff \n" 
     560"       Ultra Enable Flags: 0x0001 \n" 
     561"   Tag Queue Enable Flags: 0x0000 \n" 
     562"  Ordered Queue Tag Flags: 0x0000 \n" 
     563"  Default Tag Queue Depth: 8 \n" 
     564"      Tagged Queue By Device array for aic7xxx host instance 0: \n" 
     565"        {255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255} \n" 
     566"      Actual queue depth per device for aic7xxx host instance 0: \n" 
     567"        {1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1} \n" 
     568"  Statistics: \n" 
     569"  (scsi0:0:0:0) \n" 
     570"    Device using Wide/Sync transfers at 40.0 MByte/sec, offset 8 \n" 
     571"    Transinfo settings: current(12/8/1/0), goal(12/8/1/0), user(12/15/1/0) \n" 
     572"    Total transfers 160151 (74577 reads and 85574 writes) \n" 
     573"  (scsi0:0:6:0) \n" 
     574"    Device using Narrow/Sync transfers at 5.0 MByte/sec, offset 15 \n" 
     575"    Transinfo settings: current(50/15/0/0), goal(50/15/0/0), user(50/15/0/0) \n" 
     576"    Total transfers 0 (0 reads and 0 writes) \n" 
     577"\n" 
     578"\n" 
     579"1.6 Parallel port info in /proc/parport\n" 
     580"---------------------------------------\n" 
     581"\n" 
     582"The directory  /proc/parport  contains information about the parallel ports of\n" 
     583"your system.  It  has  one  subdirectory  for  each port, named after the port\n" 
     584"number (0,1,2,...).\n" 
     585"\n" 
     586"These directories contain the four files shown in Table 1-8.\n" 
     587"\n" 
     588"\n" 
     589"Table 1-8: Files in /proc/parport \n" 
     590"..............................................................................\n" 
     591" File      Content                                                             \n" 
     592" autoprobe Any IEEE-1284 device ID information that has been acquired.         \n" 
     593" devices   list of the device drivers using that port. A + will appear by the\n" 
     594"           name of the device currently using the port (it might not appear\n" 
     595"           against any). \n" 
     596" hardware  Parallel port's base address, IRQ line and DMA channel.             \n" 
     597" irq       IRQ that parport is using for that port. This is in a separate\n" 
     598"           file to allow you to alter it by writing a new value in (IRQ\n" 
     599"           number or none). \n" 
     600"..............................................................................\n" 
     601"\n" 
     602"1.7 TTY info in /proc/tty\n" 
     603"-------------------------\n" 
     604"\n" 
     605"Information about  the  available  and actually used tty's can be found in the\n" 
     606"directory /proc/tty.You'll  find  entries  for drivers and line disciplines in\n" 
     607"this directory, as shown in Table 1-9.\n" 
     608"\n" 
     609"\n" 
     610"Table 1-9: Files in /proc/tty \n" 
     611"..............................................................................\n" 
     612" File          Content                                        \n" 
     613" drivers       list of drivers and their usage                \n" 
     614" ldiscs        registered line disciplines                    \n" 
     615" driver/serial usage statistic and status of single tty lines \n" 
     616"..............................................................................\n" 
     617"\n" 
     618"To see  which  tty's  are  currently in use, you can simply look into the file\n" 
     619"/proc/tty/drivers:\n" 
     620"\n" 
     621"  &gt; cat /proc/tty/drivers \n" 
     622"  pty_slave            /dev/pts      136   0-255 pty:slave \n" 
     623"  pty_master           /dev/ptm      128   0-255 pty:master \n" 
     624"  pty_slave            /dev/ttyp       3   0-255 pty:slave \n" 
     625"  pty_master           /dev/pty        2   0-255 pty:master \n" 
     626"  serial               /dev/cua        5   64-67 serial:callout \n" 
     627"  serial               /dev/ttyS       4   64-67 serial \n" 
     628"  /dev/tty0            /dev/tty0       4       0 system:vtmaster \n" 
     629"  /dev/ptmx            /dev/ptmx       5       2 system \n" 
     630"  /dev/console         /dev/console    5       1 system:console \n" 
     631"  /dev/tty             /dev/tty        5       0 system:/dev/tty \n" 
     632"  unknown              /dev/tty        4    1-63 console \n" 
     633"\n" 
     634"\n" 
     635"------------------------------------------------------------------------------\n" 
     636"Summary\n" 
     637"------------------------------------------------------------------------------\n" 
     638"The /proc file system serves information about the running system. It not only\n" 
     639"allows access to process data but also allows you to request the kernel status\n" 
     640"by reading files in the hierarchy.\n" 
     641"\n" 
     642"The directory  structure  of /proc reflects the types of information and makes\n" 
     643"it easy, if not obvious, where to look for specific data.\n" 
     644"------------------------------------------------------------------------------\n" 
     645"\n" 
     646"------------------------------------------------------------------------------\n" 
     647"CHAPTER 2: MODIFYING SYSTEM PARAMETERS\n" 
     648"------------------------------------------------------------------------------\n" 
     649"\n" 
     650"------------------------------------------------------------------------------\n" 
     651"In This Chapter\n" 
     652"------------------------------------------------------------------------------\n" 
     653"* Modifying kernel parameters by writing into files found in /proc/sys\n" 
     654"* Exploring the files which modify certain parameters\n" 
     655"* Review of the /proc/sys file tree\n" 
     656"------------------------------------------------------------------------------\n" 
     657"\n" 
     658"\n" 
     659"A very  interesting part of /proc is the directory /proc/sys. This is not only\n" 
     660"a source  of  information,  it also allows you to change parameters within the\n" 
     661"kernel. Be  very  careful  when attempting this. You can optimize your system,\n" 
     662"but you  can  also  cause  it  to  crash.  Never  alter kernel parameters on a\n" 
     663"production system.  Set  up  a  development machine and test to make sure that\n" 
     664"everything works  the  way  you want it to. You may have no alternative but to\n" 
     665"reboot the machine once an error has been made.\n" 
     666"\n" 
     667"To change  a  value,  simply  echo  the new value into the file. An example is\n" 
     668"given below  in the section on the file system data. You need to be root to do\n" 
     669"this. You  can  create  your  own  boot script to perform this every time your\n" 
     670"system boots.\n" 
     671"\n" 
     672"The files  in /proc/sys can be used to fine tune and monitor miscellaneous and\n" 
     673"general things  in  the operation of the Linux kernel. Since some of the files\n" 
     674"can inadvertently  disrupt  your  system,  it  is  advisable  to  read  both\n" 
     675"documentation and  source  before actually making adjustments. In any case, be\n" 
     676"very careful  when  writing  to  any  of these files. The entries in /proc may\n" 
     677"change slightly between the 2.1.* and the 2.2 kernel, so if there is any doubt\n" 
     678"review the kernel documentation in the directory /usr/src/linux/Documentation.\n" 
     679"This chapter  is  heavily  based  on the documentation included in the pre 2.2\n" 
     680"kernels, and became part of it in version 2.2.1 of the Linux kernel.\n" 
     681"\n" 
     682"2.1 /proc/sys/fs - File system data\n" 
     683"-----------------------------------\n" 
     684"\n" 
     685"This subdirectory  contains  specific  file system, file handle, inode, dentry\n" 
     686"and quota information.\n" 
     687"\n" 
     688"Currently, these files are in /proc/sys/fs:\n" 
     689"\n" 
     690"dentry-state\n" 
     691"------------\n" 
     692"\n" 
     693"Status of  the  directory  cache.  Since  directory  entries  are  dynamically\n" 
     694"allocated and  deallocated,  this  file indicates the current status. It holds\n" 
     695"six values, in which the last two are not used and are always zero. The others\n" 
     696"are listed in table 2-1.\n" 
     697"\n" 
     698"\n" 
     699"Table 2-1: Status files of the directory cache \n" 
     700"..............................................................................\n" 
     701" File       Content                                                            \n" 
     702" nr_dentry  Almost always zero                                                 \n" 
     703" nr_unused  Number of unused cache entries                                     \n" 
     704" age_limit  \n" 
     705"            in seconds after the entry may be reclaimed, when memory is short \n" 
     706" want_pages internally                                                         \n" 
     707"..............................................................................\n" 
     708"\n" 
     709"dquot-nr and dquot-max\n" 
     710"----------------------\n" 
     711"\n" 
     712"The file dquot-max shows the maximum number of cached disk quota entries.\n" 
     713"\n" 
     714"The file  dquot-nr  shows  the  number of allocated disk quota entries and the\n" 
     715"number of free disk quota entries.\n" 
     716"\n" 
     717"If the number of available cached disk quotas is very low and you have a large\n" 
     718"number of simultaneous system users, you might want to raise the limit.\n" 
     719"\n" 
     720"file-nr and file-max\n" 
     721"--------------------\n" 
     722"\n" 
     723"The kernel  allocates file handles dynamically, but doesn't free them again at\n" 
     724"this time.\n" 
     725"\n" 
     726"The value  in  file-max  denotes  the  maximum number of file handles that the\n" 
     727"Linux kernel will allocate. When you get a lot of error messages about running\n" 
     728"out of  file handles, you might want to raise this limit. The default value is\n" 
     729"4096. To change it, just write the new number into the file:\n" 
     730"\n" 
     731"  # cat /proc/sys/fs/file-max \n" 
     732"  4096 \n" 
     733"  # echo 8192 &gt; /proc/sys/fs/file-max \n" 
     734"  # cat /proc/sys/fs/file-max \n" 
     735"  8192 \n" 
     736"\n" 
     737"\n" 
     738"This method  of  revision  is  useful  for  all customizable parameters of the\n" 
     739"kernel - simply echo the new value to the corresponding file.\n" 
     740"\n" 
     741"The three  values  in file-nr denote the number of allocated file handles, the\n" 
     742"number of  used file handles, and the maximum number of file handles. When the\n" 
     743"allocated file  handles  come close to the maximum, but the number of actually\n" 
     744"used ones  is  far  behind,  you've  encountered  a peak in your usage of file\n" 
     745"handles and you don't need to increase the maximum.\n" 
     746"\n" 
     747"inode-state and inode-nr\n" 
     748"------------------------\n" 
     749"\n" 
     750"The file inode-nr contains the first two items from inode-state, so we'll skip\n" 
     751"to that file...\n" 
     752"\n" 
     753"inode-state contains  two  actual numbers and five dummy values. The numbers\n" 
     754"are nr_inodes and nr_free_inodes (in order of appearance).\n" 
     755"\n" 
     756"nr_inodes\n" 
     757"~~~~~~~~~\n" 
     758"\n" 
     759"Denotes the  number  of  inodes the system has allocated. This number will\n" 
     760"grow and shrink dynamically.\n" 
     761"\n" 
     762"nr_free_inodes\n" 
     763"--------------\n" 
     764"\n" 
     765"Represents the  number of free inodes. Ie. The number of inuse inodes is\n" 
     766"(nr_inodes - nr_free_inodes).\n" 
     767"\n" 
     768"super-nr and super-max\n" 
     769"----------------------\n" 
     770"\n" 
     771"Again, super  block structures are allocated by the kernel, but not freed. The\n" 
     772"file super-max  contains  the  maximum  number  of super block handlers, where\n" 
     773"super-nr shows the number of currently allocated ones.\n" 
     774"\n" 
     775"Every mounted file system needs a super block, so if you plan to mount lots of\n" 
     776"file systems, you may want to increase these numbers.\n" 
     777"\n" 
     778"2.2 /proc/sys/fs/binfmt_misc - Miscellaneous binary formats\n" 
     779"-----------------------------------------------------------\n" 
     780"\n" 
     781"Besides these  files, there is the subdirectory /proc/sys/fs/binfmt_misc. This\n" 
     782"handles the kernel support for miscellaneous binary formats.\n" 
     783"\n" 
     784"Binfmt_misc provides  the ability to register additional binary formats to the\n" 
     785"Kernel without  compiling  an additional module/kernel. Therefore, binfmt_misc\n" 
     786"needs to  know magic numbers at the beginning or the filename extension of the\n" 
     787"binary.\n" 
     788"\n" 
     789"It works by maintaining a linked list of structs that contain a description of\n" 
     790"a binary  format,  including  a  magic  with size (or the filename extension),\n" 
     791"offset and  mask,  and  the  interpreter name. On request it invokes the given\n" 
     792"interpreter with  the  original  program  as  argument,  as  binfmt_java  and\n" 
     793"binfmt_em86 and  binfmt_mz  do.  Since binfmt_misc does not define any default\n" 
     794"binary-formats, you have to register an additional binary-format.\n" 
     795"\n" 
     796"There are two general files in binfmt_misc and one file per registered format.\n" 
     797"The two general files are register and status.\n" 
     798"\n" 
     799"Registering a new binary format\n" 
     800"-------------------------------\n" 
     801"\n" 
     802"To register a new binary format you have to issue the command\n" 
     803"\n" 
     804"  echo :name:type:offset:magic:mask:interpreter: &gt; /proc/sys/fs/binfmt_misc/register \n" 
     805"\n" 
     806"\n" 
     807"\n" 
     808"with appropriate  name (the name for the /proc-dir entry), offset (defaults to\n" 
     809"0, if  omitted),  magic, mask (which can be omitted, defaults to all 0xff) and\n" 
     810"last but  not  least,  the  interpreter that is to be invoked (for example and\n" 
     811"testing /bin/echo).  Type  can be M for usual magic matching or E for filename\n" 
     812"extension matching (give extension in place of magic).\n" 
     813"\n" 
     814"Check or reset the status of the binary format handler\n" 
     815"------------------------------------------------------\n" 
     816"\n" 
     817"If you  do a cat on the file /proc/sys/fs/binfmt_misc/status, you will get the\n" 
     818"current status (enabled/disabled) of binfmt_misc. Change the status by echoing\n" 
     819"0 (disables)  or  1  (enables)  or  -1  (caution:  this  clears all previously\n" 
     820"registered binary  formats)  to status. For example echo 0 &gt; status to disable\n" 
     821"binfmt_misc (temporarily).\n" 
     822"\n" 
     823"Status of a single handler\n" 
     824"--------------------------\n" 
     825"\n" 
     826"Each registered  handler has an entry in /proc/sys/fs/binfmt_misc. These files\n" 
     827"perform the  same function as status, but their scope is limited to the actual\n" 
     828"binary format.  By  cating this file, you also receive all related information\n" 
     829"about the interpreter/magic of the binfmt.\n" 
     830"\n" 
     831"Example usage of binfmt_misc (emulate binfmt_java)\n" 
     832"--------------------------------------------------\n" 
     833"\n" 
     834"  cd /proc/sys/fs/binfmt_misc  \n" 
     835"  echo ':Java:M::\\xca\\xfe\\xba\\xbe::/usr/local/java/bin/javawrapper:' &gt; register  \n" 
     836"  echo ':HTML:E::html::/usr/local/java/bin/appletviewer:' &gt; register  \n" 
     837"  echo ':Applet:M::&lt;applet::/usr/local/java/bin/appletviewer:' &gt; register \n" 
     838"  echo ':DEXE:M::\\x0eDEX::/usr/bin/dosexec:' &gt; register \n" 
     839"\n" 
     840"\n" 
     841"These four  lines  add  support  for  Java  executables and Java applets (like\n" 
     842"binfmt_java, additionally  recognizing the .html extension with no need to put\n" 
     843"&lt;!--applet&gt; to  every  applet  file).  You  have  to  install  the JDK and the\n" 
     844"shell-script /usr/local/java/bin/javawrapper  too.  It  works  around  the\n" 
     845"brokenness of  the Java filename handling. To add a Java binary, just create a\n" 
     846"link to the class-file somewhere in the path.\n" 
     847"\n" 
     848"2.3 /proc/sys/kernel - general kernel parameters\n" 
     849"------------------------------------------------\n" 
     850"\n" 
     851"This directory  reflects  general  kernel  behaviors. As I've said before, the\n" 
     852"contents depend  on  your  configuration.  Here you'll find the most important\n" 
     853"files, along with descriptions of what they mean and how to use them.\n" 
     854"\n" 
     855"acct\n" 
     856"----\n" 
     857"\n" 
     858"The file contains three values; highwater, lowwater, and frequency.\n" 
     859"\n" 
     860"It exists  only  when  BSD-style  process  accounting is enabled. These values\n" 
     861"control its behavior. If the free space on the file system where the log lives\n" 
     862"goes below  lowwater  percentage,  accounting  suspends.  If  it  goes  above\n" 
     863"highwater percentage,  accounting  resumes. Frequency determines how often you\n" 
     864"check the amount of free space (value is in seconds). Default settings are: 4,\n" 
     865"2, and  30.  That is, suspend accounting if there is less than 2 percent free;\n" 
     866"resume it  if we have a value of 3 or more percent; consider information about\n" 
     867"the amount of free space valid for 30 seconds\n" 
     868"\n" 
     869"ctrl-alt-del\n" 
     870"------------\n" 
     871"\n" 
     872"When the value in this file is 0, ctrl-alt-del is trapped and sent to the init\n" 
     873"program to  handle a graceful restart. However, when the value is greater that\n" 
     874"zero, Linux's  reaction  to  this key combination will be an immediate reboot,\n" 
     875"without syncing its dirty buffers.\n" 
     876"\n" 
     877"[NOTE]\n" 
     878"    When a  program  (like  dosemu)  has  the  keyboard  in  raw  mode,  the\n" 
     879"    ctrl-alt-del is  intercepted  by  the  program  before it ever reaches the\n" 
     880"    kernel tty  layer,  and  it is up to the program to decide what to do with\n" 
     881"    it.\n" 
     882"\n" 
     883"domainname and hostname\n" 
     884"-----------------------\n" 
     885"\n" 
     886"These files  can  be controlled to set the NIS domainname and hostname of your\n" 
     887"box. For the classic darkstar.frop.org a simple:\n" 
     888"\n" 
     889"  # echo \"darkstar\" &gt; /proc/sys/kernel/hostname \n" 
     890"  # echo \"frop.org\" &gt; /proc/sys/kernel/domainname \n" 
     891"\n" 
     892"\n" 
     893"would suffice to set your hostname and NIS domainname.\n" 
     894"\n" 
     895"osrelease, ostype and version\n" 
     896"-----------------------------\n" 
     897"\n" 
     898"The names make it pretty obvious what these fields contain:\n" 
     899"\n" 
     900"  &gt; cat /proc/sys/kernel/osrelease \n" 
     901"  2.2.12 \n" 
     902"   \n" 
     903"  &gt; cat /proc/sys/kernel/ostype \n" 
     904"  Linux \n" 
     905"   \n" 
     906"  &gt; cat /proc/sys/kernel/version \n" 
     907"  #4 Fri Oct 1 12:41:14 PDT 1999 \n" 
     908"\n" 
     909"\n" 
     910"The files  osrelease and ostype should be clear enough. Version needs a little\n" 
     911"more clarification.  The  #4 means that this is the 4th kernel built from this\n" 
     912"source base and the date after it indicates the time the kernel was built. The\n" 
     913"only way to tune these values is to rebuild the kernel.\n" 
     914"\n" 
     915"panic\n" 
     916"-----\n" 
     917"\n" 
     918"The value  in  this  file  represents  the  number of seconds the kernel waits\n" 
     919"before rebooting  on  a  panic.  When  you  use  the  software  watchdog,  the\n" 
     920"recommended setting  is  60. If set to 0, the auto reboot after a kernel panic\n" 
     921"is disabled, which is the default setting.\n" 
     922"\n" 
     923"printk\n" 
     924"------\n" 
     925"\n" 
     926"The four values in printk denote\n" 
     927"* console_loglevel,\n" 
     928"* default_message_loglevel,\n" 
     929"* minimum_console_level and\n" 
     930"* default_console_loglevel\n" 
     931"respectively.\n" 
     932"\n" 
     933"These values  influence  printk()  behavior  when  printing  or  logging error\n" 
     934"messages, which  come  from  inside  the  kernel.  See  syslog(2)  for  more\n" 
     935"information on the different log levels.\n" 
     936"\n" 
     937"console_loglevel\n" 
     938"----------------\n" 
     939"\n" 
     940"Messages with a higher priority than this will be printed to the console.\n" 
     941"\n" 
     942"default_message_level\n" 
     943"---------------------\n" 
     944"\n" 
     945"Messages without an explicit priority will be printed with this priority.\n" 
     946"\n" 
     947"minimum_console_loglevel\n" 
     948"------------------------\n" 
     949"\n" 
     950"Minimum (highest) value to which the console_loglevel can be set.\n" 
     951"\n" 
     952"default_console_loglevel\n" 
     953"------------------------\n" 
     954"\n" 
     955"Default value for console_loglevel.\n" 
     956"\n" 
     957"sg-big-buff\n" 
     958"-----------\n" 
     959"\n" 
     960"This file  shows  the size of the generic SCSI (sg) buffer. At this point, you\n" 
     961"can't tune  it  yet,  but  you  can  change  it  at  compile  time  by editing\n" 
     962"include/scsi/sg.h and changing the value of SG_BIG_BUFF.\n" 
     963"\n" 
     964"If you use a scanner with SANE (Scanner Access Now Easy) you might want to set\n" 
     965"this to a higher value. Refer to the SANE documentation on this issue.\n" 
     966"\n" 
     967"modprobe\n" 
     968"--------\n" 
     969"\n" 
     970"The location  where  the  modprobe  binary  is  located.  The kernel uses this\n" 
     971"program to load modules on demand.\n" 
     972"\n" 
     973"2.4 /proc/sys/vm - The virtual memory subsystem\n" 
     974"-----------------------------------------------\n" 
     975"\n" 
     976"The files  in  this directory can be used to tune the operation of the virtual\n" 
     977"memory (VM)  subsystem  of  the  Linux  kernel.  In addition, one of the files\n" 
     978"(bdflush) has some influence on disk usage.\n" 
     979"\n" 
     980"bdflush\n" 
     981"-------\n" 
     982"\n" 
     983"This file  controls  the  operation of the bdflush kernel daemon. It currently\n" 
     984"contains nine  integer  values,  six of which are actually used by the kernel.\n" 
     985"They are listed in table 2-2.\n" 
     986"\n" 
     987"\n" 
     988"Table 2-2: Parameters in /proc/sys/vm/bdflush \n" 
     989"..............................................................................\n" 
     990" Value      Meaning                                                            \n" 
     991" nfract     Percentage of buffer cache dirty to  activate bdflush              \n" 
     992" ndirty     Maximum number of dirty blocks to  write out per wake-cycle        \n" 
     993" nrefill    Number of clean buffers to try to obtain  each time we call refill \n" 
     994" nref_dirt  buffer threshold for activating bdflush when trying to refill\n" 
     995"            buffers. \n" 
     996" dummy      Unused                                                             \n" 
     997" age_buffer Time for normal buffer to age before we flush it                   \n" 
     998" age_super  Time for superblock to age before we flush it                      \n" 
     999" dummy      Unused                                                             \n" 
     1000" dummy      Unused                                                             \n" 
     1001"..............................................................................\n" 
     1002"\n" 
     1003"nfract\n" 
     1004"------\n" 
     1005"\n" 
     1006"This parameter  governs  the  maximum  number  of  dirty buffers in the buffer\n" 
     1007"cache. Dirty means that the contents of the buffer still have to be written to\n" 
     1008"disk (as  opposed  to  a  clean  buffer,  which  can just be forgotten about).\n" 
     1009"Setting this  to  a  higher value means that Linux can delay disk writes for a\n" 
     1010"long time, but it also means that it will have to do a lot of I/O at once when\n" 
     1011"memory becomes short. A lower value will spread out disk I/O more evenly.\n" 
     1012"\n" 
     1013"ndirty\n" 
     1014"------\n" 
     1015"\n" 
     1016"Ndirty gives the maximum number of dirty buffers that bdflush can write to the\n" 
     1017"disk at  one  time.  A high value will mean delayed, bursty I/O, while a small\n" 
     1018"value can lead to memory shortage when bdflush isn't woken up often enough.\n" 
     1019"\n" 
     1020"nrefill\n" 
     1021"-------\n" 
     1022"\n" 
     1023"This is  the  number  of  buffers  that  bdflush  will add to the list of free\n" 
     1024"buffers when  refill_freelist()  is  called.  It is necessary to allocate free\n" 
     1025"buffers beforehand,  since  the  buffers  are  often  different sizes than the\n" 
     1026"memory pages  and some bookkeeping needs to be done beforehand. The higher the\n" 
     1027"number, the  more  memory  will be wasted and the less often refill_freelist()\n" 
     1028"will need to run.\n" 
     1029"\n" 
     1030"nref_dirt\n" 
     1031"---------\n" 
     1032"\n" 
     1033"When refill_freelist() comes across more than nref_dirt dirty buffers, it will\n" 
     1034"wake up bdflush.\n" 
     1035"\n" 
     1036"age_buffer and age_super\n" 
     1037"------------------------\n" 
     1038"\n" 
     1039"Finally, the age_buffer and age_super parameters govern the maximum time Linux\n" 
     1040"waits before  writing  out  a  dirty buffer to disk. The value is expressed in\n" 
     1041"jiffies (clockticks),  the  number of jiffies per second is 100. Age_buffer is\n" 
     1042"the maximum age for data blocks, while age_super is for filesystems meta data.\n" 
     1043"\n" 
     1044"buffermem\n" 
     1045"---------\n" 
     1046"\n" 
     1047"The three  values  in  this  file  control  how much memory should be used for\n" 
     1048"buffer memory.  The  percentage  is calculated as a percentage of total system\n" 
     1049"memory.\n" 
     1050"\n" 
     1051"The values are:\n" 
     1052"\n" 
     1053"min_percent\n" 
     1054"-----------\n" 
     1055"\n" 
     1056"This is  the  minimum  percentage  of  memory  that  should be spent on buffer\n" 
     1057"memory.\n" 
     1058"\n" 
     1059"borrow_percent\n" 
     1060"--------------\n" 
     1061"\n" 
     1062"When Linux is short on memory, and the buffer cache uses more than it has been\n" 
     1063"allotted, the  memory  management  (MM)  subsystem will prune the buffer cache\n" 
     1064"more heavily than other memory to compensate.\n" 
     1065"\n" 
     1066"max_percent\n" 
     1067"-----------\n" 
     1068"\n" 
     1069"This is the maximum amount of memory that can be used for buffer memory.\n" 
     1070"\n" 
     1071"freepages\n" 
     1072"---------\n" 
     1073"\n" 
     1074"This file contains three values: min, low and high:\n" 
     1075"\n" 
     1076"min\n" 
     1077"---\n" 
     1078"When the  number  of  free  pages  in the system reaches this number, only the\n" 
     1079"kernel can allocate more memory.\n" 
     1080"\n" 
     1081"low\n" 
     1082"---\n" 
     1083"If the number of free pages falls below this point, the kernel starts swapping\n" 
     1084"aggressively.\n" 
     1085"\n" 
     1086"high\n" 
     1087"----\n" 
     1088"The kernel  tries  to  keep  up to this amount of memory free; if memory falls\n" 
     1089"below this point, the kernel starts gently swapping in the hopes that it never\n" 
     1090"has to do really aggressive swapping.\n" 
     1091"\n" 
     1092"kswapd\n" 
     1093"------\n" 
     1094"\n" 
     1095"Kswapd is  the  kernel  swap  out daemon. That is, kswapd is that piece of the\n" 
     1096"kernel that  frees  memory when it gets fragmented or full. Since every system\n" 
     1097"is different, you'll probably want some control over this piece of the system.\n" 
     1098"\n" 
     1099"The file contains three numbers:\n" 
     1100"\n" 
     1101"tries_base\n" 
     1102"----------\n" 
     1103"\n" 
     1104"The maximum  number  of  pages kswapd tries to free in one round is calculated\n" 
     1105"from this  number.  Usually  this  number  will  be  divided  by  4  or 8 (see\n" 
     1106"mm/vmscan.c), so it isn't as big as it looks.\n" 
     1107"\n" 
     1108"When you  need to increase the bandwidth to/from swap, you'll want to increase\n" 
     1109"this number.\n" 
     1110"\n" 
     1111"tries_min\n" 
     1112"---------\n" 
     1113"\n" 
     1114"This is  the  minimum number of times kswapd tries to free a page each time it\n" 
     1115"is called. Basically it's just there to make sure that kswapd frees some pages\n" 
     1116"even when it's being called with minimum priority.\n" 
     1117"\n" 
     1118"swap_cluster\n" 
     1119"------------\n" 
     1120"\n" 
     1121"This is probably the greatest influence on system performance.\n" 
     1122"\n" 
     1123"swap_cluster is  the  number  of  pages kswapd writes in one turn. You'll want\n" 
     1124"this value  to  be  large  so that kswapd does its I/O in large chunks and the\n" 
     1125"disk doesn't  have  to  seek  as  often, but you don't want it to be too large\n" 
     1126"since that would flood the request queue.\n" 
     1127"\n" 
     1128"overcommit_memory\n" 
     1129"-----------------\n" 
     1130"\n" 
     1131"This file  contains  one  value.  The following algorithm is used to decide if\n" 
     1132"there's enough  memory:  if  the  value of overcommit_memory is positive, then\n" 
     1133"there's always  enough  memory. This is a useful feature, since programs often\n" 
     1134"malloc() huge  amounts  of  memory 'just in case', while they only use a small\n" 
     1135"part of  it.  Leaving  this value at 0 will lead to the failure of such a huge\n" 
     1136"malloc(), when in fact the system has enough memory for the program to run.\n" 
     1137"\n" 
     1138"On the  other  hand,  enabling this feature can cause you to run out of memory\n" 
     1139"and thrash the system to death, so large and/or important servers will want to\n" 
     1140"set this value to 0.\n" 
     1141"\n" 
     1142"pagecache\n" 
     1143"---------\n" 
     1144"\n" 
     1145"This file  does exactly the same job as buffermem, only this file controls the\n" 
     1146"amount of memory allowed for memory mapping and generic caching of files.\n" 
     1147"\n" 
     1148"You don't  want  the  minimum level to be too low, otherwise your system might\n" 
     1149"thrash when memory is tight or fragmentation is high.\n" 
     1150"\n" 
     1151"pagetable_cache\n" 
     1152"---------------\n" 
     1153"\n" 
     1154"The kernel  keeps a number of page tables in a per-processor cache (this helps\n" 
     1155"a lot  on  SMP systems). The cache size for each processor will be between the\n" 
     1156"low and the high value.\n" 
     1157"\n" 
     1158"On a  low-memory,  single  CPU system, you can safely set these values to 0 so\n" 
     1159"you don't  waste  memory.  It  is  used  on SMP systems so that the system can\n" 
     1160"perform fast  pagetable allocations without having to acquire the kernel memory\n" 
     1161"lock.\n" 
     1162"\n" 
     1163"For large  systems,  the  settings  are probably fine. For normal systems they\n" 
     1164"won't hurt  a  bit.  For  small  systems  (  less  than  16MB ram) it might be\n" 
     1165"advantageous to set both values to 0.\n" 
     1166"\n" 
     1167"swapctl\n" 
     1168"-------\n" 
     1169"\n" 
     1170"This file  contains  no less than 8 variables. All of these values are used by\n" 
     1171"kswapd.\n" 
     1172"\n" 
     1173"The first four variables\n" 
     1174"* sc_max_page_age,\n" 
     1175"* sc_page_advance,\n" 
     1176"* sc_page_decline and\n" 
     1177"* sc_page_initial_age\n" 
     1178"are used  to  keep  track  of  Linux's page aging. Page aging is a bookkeeping\n" 
     1179"method to  track  which pages of memory are often used, and which pages can be\n" 
     1180"swapped out without consequences.\n" 
     1181"\n" 
     1182"When a  page  is  swapped in, it starts at sc_page_initial_age (default 3) and\n" 
     1183"when the  page  is  scanned  by  kswapd,  its age is adjusted according to the\n" 
     1184"following scheme:\n" 
     1185"\n" 
     1186"* If  the  page  was used since the last time we scanned, its age is increased\n" 
     1187"  by sc_page_advance  (default  3).  Where  the  maximum  value  is  given  by\n" 
     1188"  sc_max_page_age (default 20).\n" 
     1189"* Otherwise  (meaning  it wasn't used) its age is decreased by sc_page_decline\n" 
     1190"  (default 1).\n" 
     1191"\n" 
     1192"When a page reaches age 0, it's ready to be swapped out.\n" 
     1193"\n" 
     1194"The variables  sc_age_cluster_fract, sc_age_cluster_min, sc_pageout_weight and\n" 
     1195"sc_bufferout_weight, can  be  used  to  control  kswapd's  aggressiveness  in\n" 
     1196"swapping out pages.\n" 
     1197"\n" 
     1198"Sc_age_cluster_fract is used to calculate how many pages from a process are to\n" 
     1199"be scanned by kswapd. The formula used is\n" 
     1200"\n" 
     1201"(sc_age_cluster_fract divided by 1024) times resident set size\n" 
     1202"\n" 
     1203"So if you want kswapd to scan the whole process, sc_age_cluster_fract needs to\n" 
     1204"have a  value  of  1024.  The  minimum  number  of  pages  kswapd will scan is\n" 
     1205"represented by sc_age_cluster_min, which is done so that kswapd will also scan\n" 
     1206"small processes.\n" 
     1207"\n" 
     1208"The values  of  sc_pageout_weight  and sc_bufferout_weight are used to control\n" 
     1209"how many  tries  kswapd  will make in order to swap out one page/buffer. These\n" 
     1210"values can  be used to fine-tune the ratio between user pages and buffer/cache\n" 
     1211"memory. When  you find that your Linux system is swapping out too many process\n" 
     1212"pages in  order  to  satisfy  buffer  memory  demands,  you may want to either\n" 
     1213"increase sc_bufferout_weight, or decrease the value of sc_pageout_weight.\n" 
     1214"\n" 
     1215"2.5 /proc/sys/dev - Device specific parameters\n" 
     1216"----------------------------------------------\n" 
     1217"\n" 
     1218"Currently there is only support for CDROM drives, and for those, there is only\n" 
     1219"one read-only  file containing information about the CD-ROM drives attached to\n" 
     1220"the system:\n" 
     1221"\n" 
     1222"  &gt;cat /proc/sys/dev/cdrom/info \n" 
     1223"  CD-ROM information, Id: cdrom.c 2.55 1999/04/25 \n" 
     1224"   \n" 
     1225"  drive name:             sr0     hdb \n" 
     1226"  drive speed:            32      40 \n" 
     1227"  drive # of slots:       1       0 \n" 
     1228"  Can close tray:         1       1 \n" 
     1229"  Can open tray:          1       1 \n" 
     1230"  Can lock tray:          1       1 \n" 
     1231"  Can change speed:       1       1 \n" 
     1232"  Can select disk:        0       1 \n" 
     1233"  Can read multisession:  1       1 \n" 
     1234"  Can read MCN:           1       1 \n" 
     1235"  Reports media changed:  1       1 \n" 
     1236"  Can play audio:         1       1 \n" 
     1237"\n" 
     1238"\n" 
     1239"You see two drives, sr0 and hdb, along with a list of their features.\n" 
     1240"\n" 
     1241"2.6 /proc/sys/sunrpc - Remote procedure calls\n" 
     1242"---------------------------------------------\n" 
     1243"\n" 
     1244"This directory  contains four files, which enable or disable debugging for the\n" 
     1245"RPC functions NFS, NFS-daemon, RPC and NLM. The default values are 0. They can\n" 
     1246"be set to one to turn debugging on. (The default value is 0 for each)\n" 
     1247"\n" 
     1248"2.7 /proc/sys/net - Networking stuff\n" 
     1249"------------------------------------\n" 
     1250"\n" 
     1251"The interface  to  the  networking  parts  of  the  kernel  is  located  in\n" 
     1252"/proc/sys/net. Table  2-3  shows all possible subdirectories. You may see only\n" 
     1253"some of them, depending on your kernel's configuration.\n" 
     1254"\n" 
     1255"\n" 
     1256"Table 2-3: Subdirectories in /proc/sys/net \n" 
     1257"..............................................................................\n" 
     1258" Directory Content             Directory  Content            \n" 
     1259" core      General parameter   appletalk  Appletalk protocol \n" 
     1260" unix      Unix domain sockets netrom     NET/ROM            \n" 
     1261" 802       E802 protocol       ax25       AX25               \n" 
     1262" ethernet  Ethernet protocol   rose       X.25 PLP layer     \n" 
     1263" ipv4      IP version 4        x25        X.25 protocol      \n" 
     1264" ipx       IPX                 token-ring IBM token ring     \n" 
     1265" bridge    Bridging            decnet     DEC net            \n" 
     1266" ipv6      IP version 6                   \n" 
     1267"..............................................................................\n" 
     1268"\n" 
     1269"We will  concentrate  on IP networking here. Since AX15, X.25, and DEC Net are\n" 
     1270"only minor players in the Linux world, we'll skip them in this chapter. You'll\n" 
     1271"find some  short  info on Appletalk and IPX further on in this chapter. Review\n" 
     1272"the online  documentation  and the kernel source to get a detailed view of the\n" 
     1273"parameters for  those  protocols.  In  this  section  we'll  discuss  the\n" 
     1274"subdirectories printed  in  bold letters in the table above. As default values\n" 
     1275"are suitable for most needs, there is no need to change these values.\n" 
     1276"\n" 
     1277"/proc/sys/net/core - Network core options\n" 
     1278"-----------------------------------------\n" 
     1279"\n" 
     1280"rmem_default\n" 
     1281"------------\n" 
     1282"\n" 
     1283"The default setting of the socket receive buffer in bytes.\n" 
     1284"\n" 
     1285"rmem_max\n" 
     1286"--------\n" 
     1287"\n" 
     1288"The maximum receive socket buffer size in bytes.\n" 
     1289"\n" 
     1290"wmem_default\n" 
     1291"------------\n" 
     1292"\n" 
     1293"The default setting (in bytes) of the socket send buffer.\n" 
     1294"\n" 
     1295"wmem_max\n" 
     1296"--------\n" 
     1297"\n" 
     1298"The maximum send socket buffer size in bytes.\n" 
     1299"\n" 
     1300"message_burst and message_cost\n" 
     1301"------------------------------\n" 
     1302"\n" 
     1303"These parameters  are used to limit the warning messages written to the kernel\n" 
     1304"log from  the  networking  code.  They  enforce  a  rate  limit  to  make  a\n" 
     1305"denial-of-service attack  impossible. A higher message_cost factor, results in\n" 
     1306"fewer messages that will be written. Message_burst controls when messages will\n" 
     1307"be dropped.  The  default  settings  limit  warning messages to one every five\n" 
     1308"seconds.\n" 
     1309"\n" 
     1310"netdev_max_backlog\n" 
     1311"------------------\n" 
     1312"\n" 
     1313"Maximum number  of  packets,  queued  on  the  INPUT  side, when the interface\n" 
     1314"receives packets faster than kernel can process them.\n" 
     1315"\n" 
     1316"optmem_max\n" 
     1317"----------\n" 
     1318"\n" 
     1319"Maximum ancillary buffer size allowed per socket. Ancillary data is a sequence\n" 
     1320"of struct cmsghdr structures with appended data.\n" 
     1321"\n" 
     1322"/proc/sys/net/unix - Parameters for Unix domain sockets\n" 
     1323"-------------------------------------------------------\n" 
     1324"\n" 
     1325"There are  only  two  files  in this subdirectory. They control the delays for\n" 
     1326"deleting and destroying socket descriptors.\n" 
     1327"\n" 
     1328"2.8 /proc/sys/net/ipv4 - IPV4 settings\n" 
     1329"--------------------------------------\n" 
     1330"\n" 
     1331"IP version  4  is  still the most used protocol in Unix networking. It will be\n" 
     1332"replaced by  IP version 6 in the next couple of years, but for the moment it's\n" 
     1333"the de  facto  standard  for  the  internet  and  is  used  in most networking\n" 
     1334"environments around  the  world.  Because  of the importance of this protocol,\n" 
     1335"we'll have a deeper look into the subtree controlling the behavior of the IPv4\n" 
     1336"subsystem of the Linux kernel.\n" 
     1337"\n" 
     1338"Let's start with the entries in /proc/sys/net/ipv4.\n" 
     1339"\n" 
     1340"ICMP settings\n" 
     1341"-------------\n" 
     1342"\n" 
     1343"icmp_echo_ignore_all and icmp_echo_ignore_broadcasts\n" 
     1344"----------------------------------------------------\n" 
     1345"\n" 
     1346"Turn on (1) or off (0), if the kernel should ignore all ICMP ECHO requests, or\n" 
     1347"just those to broadcast and multicast addresses.\n" 
     1348"\n" 
     1349"Please note that if you accept ICMP echo requests with a broadcast/multi\\-cast\n" 
     1350"destination address  your  network  may  be  used as an exploder for denial of\n" 
     1351"service packet flooding attacks to other hosts.\n" 
     1352"\n" 
     1353"icmp_destunreach_rate, icmp_echoreply_rate, icmp_paramprob_rate and icmp_timeexeed_rate\n" 
     1354"---------------------------------------------------------------------------------------\n" 
     1355"\n" 
     1356"Sets limits  for  sending  ICMP  packets  to specific targets. A value of zero\n" 
     1357"disables all  limiting.  Any  positive  value sets the maximum package rate in\n" 
     1358"hundredth of a second (on Intel systems).\n" 
     1359"\n" 
     1360"IP settings\n" 
     1361"-----------\n" 
     1362"\n" 
     1363"ip_autoconfig\n" 
     1364"-------------\n" 
     1365"\n" 
     1366"This file contains the number one if the host received its IP configuration by\n" 
     1367"RARP, BOOTP, DHCP or a similar mechanism. Otherwise it is zero.\n" 
     1368"\n" 
     1369"ip_default_ttl\n" 
     1370"--------------\n" 
     1371"\n" 
     1372"TTL (Time  To  Live) for IPv4 interfaces. This is simply the maximum number of\n" 
     1373"hops a packet may travel.\n" 
     1374"\n" 
     1375"ip_dynaddr\n" 
     1376"----------\n" 
     1377"\n" 
     1378"Enable dynamic  socket  address rewriting on interface address change. This is\n" 
     1379"useful for dialup interface with changing IP addresses.\n" 
     1380"\n" 
     1381"ip_forward\n" 
     1382"----------\n" 
     1383"\n" 
     1384"Enable or  disable forwarding of IP packages between interfaces. Changing this\n" 
     1385"value resets  all other parameters to their default values. They differ if the\n" 
     1386"kernel is configured as host or router.\n" 
     1387"\n" 
     1388"ip_local_port_range\n" 
     1389"-------------------\n" 
     1390"\n" 
     1391"Range of  ports  used  by  TCP  and UDP to choose the local port. Contains two\n" 
     1392"numbers, the  first  number  is the lowest port, the second number the highest\n" 
     1393"local port.  Default  is  1024-4999.  Should  be  changed  to  32768-61000 for\n" 
     1394"high-usage systems.\n" 
     1395"\n" 
     1396"ip_no_pmtu_disc\n" 
     1397"---------------\n" 
     1398"\n" 
     1399"Global switch  to  turn  path  MTU  discovery off. It can also be set on a per\n" 
     1400"socket basis by the applications or on a per route basis.\n" 
     1401"\n" 
     1402"ip_masq_debug\n" 
     1403"-------------\n" 
     1404"\n" 
     1405"Enable/disable debugging of IP masquerading.\n" 
     1406"\n" 
     1407"IP fragmentation settings\n" 
     1408"-------------------------\n" 
     1409"\n" 
     1410"ipfrag_high_trash and ipfrag_low_trash\n" 
     1411"--------------------------------------\n" 
     1412"\n" 
     1413"Maximum memory  used to reassemble IP fragments. When ipfrag_high_thresh bytes\n" 
     1414"of memory  is  allocated  for  this  purpose,  the  fragment handler will toss\n" 
     1415"packets until ipfrag_low_thresh is reached.\n" 
     1416"\n" 
     1417"ipfrag_time\n" 
     1418"-----------\n" 
     1419"\n" 
     1420"Time in seconds to keep an IP fragment in memory.\n" 
     1421"\n" 
     1422"TCP settings\n" 
     1423"------------\n" 
     1424"\n" 
     1425"tcp_ecn\n" 
     1426"-------\n" 
     1427"\n" 
     1428"This file controls the use of the ECN bit in the IPv4 headers, this is a new\n" 
     1429"feature about Explicit Congestion Notification, but some routers and firewalls\n" 
     1430"block trafic that has this bit set, so it could be necessary to echo 0 to\n" 
     1431"/proc/sys/net/ipv4/tcp_ecn, if you want to talk to this sites. For more info\n" 
     1432"you could read RFC2481.\n" 
     1433"\n" 
     1434"tcp_retrans_collapse\n" 
     1435"--------------------\n" 
     1436"\n" 
     1437"Bug-to-bug compatibility with some broken printers. On retransmit, try to send\n" 
     1438"larger packets to work around bugs in certain TCP stacks. Can be turned off by\n" 
     1439"setting it to zero.\n" 
     1440"\n" 
     1441"tcp_keepalive_probes\n" 
     1442"--------------------\n" 
     1443"\n" 
     1444"Number of  keep  alive  probes  TCP  sends  out,  until  it  decides  that the\n" 
     1445"connection is broken.\n" 
     1446"\n" 
     1447"tcp_keepalive_time\n" 
     1448"------------------\n" 
     1449"\n" 
     1450"How often  TCP  sends out keep alive messages, when keep alive is enabled. The\n" 
     1451"default is 2 hours.\n" 
     1452"\n" 
     1453"tcp_syn_retries\n" 
     1454"---------------\n" 
     1455"\n" 
     1456"Number of  times  initial  SYNs  for  a  TCP  connection  attempt  will  be\n" 
     1457"retransmitted. Should  not  be  higher  than 255. This is only the timeout for\n" 
     1458"outgoing connections,  for  incoming  connections the number of retransmits is\n" 
     1459"defined by tcp_retries1.\n" 
     1460"\n" 
     1461"tcp_sack\n" 
     1462"--------\n" 
     1463"\n" 
     1464"Enable select acknowledgments after RFC2018.\n" 
     1465"\n" 
     1466"tcp_timestamps\n" 
     1467"--------------\n" 
     1468"\n" 
     1469"Enable timestamps as defined in RFC1323.\n" 
     1470"\n" 
     1471"tcp_stdurg\n" 
     1472"----------\n" 
     1473"\n" 
     1474"Enable the  strict  RFC793 interpretation of the TCP urgent pointer field. The\n" 
     1475"default is  to  use  the  BSD  compatible interpretation of the urgent pointer\n" 
     1476"pointing to the first byte after the urgent data. The RFC793 interpretation is\n" 
     1477"to have  it  point  to  the last byte of urgent data. Enabling this option may\n" 
     1478"lead to interoperatibility problems. Disabled by default.\n" 
     1479"\n" 
     1480"tcp_syncookies\n" 
     1481"--------------\n" 
     1482"\n" 
     1483"Only valid  when  the  kernel  was  compiled  with CONFIG_SYNCOOKIES. Send out\n" 
     1484"syncookies when  the  syn backlog queue of a socket overflows. This is to ward\n" 
     1485"off the common 'syn flood attack'. Disabled by default.\n" 
     1486"\n" 
     1487"Note that  the  concept  of a socket backlog is abandoned. This means the peer\n" 
     1488"may not  receive  reliable  error  messages  from  an  over loaded server with\n" 
     1489"syncookies enabled.\n" 
     1490"\n" 
     1491"tcp_window_scaling\n" 
     1492"------------------\n" 
     1493"\n" 
     1494"Enable window scaling as defined in RFC1323.\n" 
     1495"\n" 
     1496"tcp_fin_timeout\n" 
     1497"---------------\n" 
     1498"\n" 
     1499"The length  of  time  in  seconds  it  takes to receive a final FIN before the\n" 
     1500"socket is  always  closed.  This  is  strictly  a  violation  of  the  TCP\n" 
     1501"specification, but required to prevent denial-of-service attacks.\n" 
     1502"\n" 
     1503"tcp_max_ka_probes\n" 
     1504"-----------------\n" 
     1505"\n" 
     1506"Indicates how  many  keep alive probes are sent per slow timer run. Should not\n" 
     1507"be set too high to prevent bursts.\n" 
     1508"\n" 
     1509"tcp_max_syn_backlog\n" 
     1510"-------------------\n" 
     1511"\n" 
     1512"Length of  the per socket backlog queue. Since Linux 2.2 the backlog specified\n" 
     1513"in listen(2)  only  specifies  the  length  of  the  backlog  queue of already\n" 
     1514"established sockets. When more connection requests arrive Linux starts to drop\n" 
     1515"packets. When  syncookies  are  enabled the packets are still answered and the\n" 
     1516"maximum queue is effectively ignored.\n" 
     1517"\n" 
     1518"tcp_retries1\n" 
     1519"------------\n" 
     1520"\n" 
     1521"Defines how  often  an  answer  to  a  TCP connection request is retransmitted\n" 
     1522"before giving up.\n" 
     1523"\n" 
     1524"tcp_retries2\n" 
     1525"------------\n" 
     1526"\n" 
     1527"Defines how often a TCP packet is retransmitted before giving up.\n" 
     1528"\n" 
     1529"Interface specific settings\n" 
     1530"---------------------------\n" 
     1531"\n" 
     1532"In the directory /proc/sys/net/ipv4/conf you'll find one subdirectory for each\n" 
     1533"interface the  system  knows about and one directory calls all. Changes in the\n" 
     1534"all subdirectory  affect  all  interfaces,  whereas  changes  in  the  other\n" 
     1535"subdirectories affect  only  one  interface.  All  directories  have  the same\n" 
     1536"entries:\n" 
     1537"\n" 
     1538"accept_redirects\n" 
     1539"----------------\n" 
     1540"\n" 
     1541"This switch  decides  if the kernel accepts ICMP redirect messages or not. The\n" 
     1542"default is 'yes' if the kernel is configured for a regular host and 'no' for a\n" 
     1543"router configuration.\n" 
     1544"\n" 
     1545"accept_source_route\n" 
     1546"-------------------\n" 
     1547"\n" 
     1548"Should source  routed  packages  be  accepted  or  declined.  The  default  is\n" 
     1549"dependent on  the  kernel  configuration.  It's 'yes' for routers and 'no' for\n" 
     1550"hosts.\n" 
     1551"\n" 
     1552"bootp_relay\n" 
     1553"~~~~~~~~~~~\n" 
     1554"\n" 
     1555"Accept packets  with source address 0.b.c.d with destinations not to this host\n" 
     1556"as local ones. It is supposed that a BOOTP relay daemon will catch and forward\n" 
     1557"such packets.\n" 
     1558"\n" 
     1559"The default  is  0,  since this feature is not implemented yet (kernel version\n" 
     1560"2.2.12).\n" 
     1561"\n" 
     1562"forwarding\n" 
     1563"----------\n" 
     1564"\n" 
     1565"Enable or disable IP forwarding on this interface.\n" 
     1566"\n" 
     1567"log_martians\n" 
     1568"------------\n" 
     1569"\n" 
     1570"Log packets with source addresses with no known route to kernel log.\n" 
     1571"\n" 
     1572"mc_forwarding\n" 
     1573"-------------\n" 
     1574"\n" 
     1575"Do multicast routing. The kernel needs to be compiled with CONFIG_MROUTE and a\n" 
     1576"multicast routing daemon is required.\n" 
     1577"\n" 
     1578"proxy_arp\n" 
     1579"---------\n" 
     1580"\n" 
     1581"Does (1) or does not (0) perform proxy ARP.\n" 
     1582"\n" 
     1583"rp_filter\n" 
     1584"---------\n" 
     1585"\n" 
     1586"Integer value determines if a source validation should be made. 1 means yes, 0\n" 
     1587"means no.  Disabled by default, but local/broadcast address spoofing is always\n" 
     1588"on.\n" 
     1589"\n" 
     1590"If you  set this to 1 on a router that is the only connection for a network to\n" 
     1591"the net,  it  will  prevent  spoofing  attacks  against your internal networks\n" 
     1592"(external addresses  can  still  be  spoofed), without the need for additional\n" 
     1593"firewall rules.\n" 
     1594"\n" 
     1595"secure_redirects\n" 
     1596"----------------\n" 
     1597"\n" 
     1598"Accept ICMP  redirect  messages  only  for gateways, listed in default gateway\n" 
     1599"list. Enabled by default.\n" 
     1600"\n" 
     1601"shared_media\n" 
     1602"------------\n" 
     1603"\n" 
     1604"If it  is  not  set  the kernel does not assume that different subnets on this\n" 
     1605"device can communicate directly. Default setting is 'yes'.\n" 
     1606"\n" 
     1607"send_redirects\n" 
     1608"--------------\n" 
     1609"\n" 
     1610"Determines whether to send ICMP redirects to other hosts.\n" 
     1611"\n" 
     1612"Routing settings\n" 
     1613"----------------\n" 
     1614"\n" 
     1615"The directory  /proc/sys/net/ipv4/route  contains  several  file  to  control\n" 
     1616"routing issues.\n" 
     1617"\n" 
     1618"error_burst and error_cost\n" 
     1619"--------------------------\n" 
     1620"\n" 
     1621"These parameters  are used to limit the warning messages written to the kernel\n" 
     1622"log from  the  routing  code.  The  higher the error_cost factor is, the fewer\n" 
     1623"messages will  be written. Error_burst controls when messages will be dropped.\n" 
     1624"The default settings limit warning messages to one every five seconds.\n" 
     1625"\n" 
     1626"flush\n" 
     1627"-----\n" 
     1628"\n" 
     1629"Writing to this file results in a flush of the routing cache.\n" 
     1630"\n" 
     1631"gc_elastic, gc_interval, gc_min_interval, gc_tresh, gc_timeout\n" 
     1632"--------------------------------------------------------------\n" 
     1633"\n" 
     1634"Values to  control  the  frequency  and  behavior  of  the  garbage collection\n" 
     1635"algorithm for the routing cache.\n" 
     1636"\n" 
     1637"max_size\n" 
     1638"--------\n" 
     1639"\n" 
     1640"Maximum size  of  the routing cache. Old entries will be purged once the cache\n" 
     1641"reached has this size.\n" 
     1642"\n" 
     1643"max_delay, min_delay\n" 
     1644"--------------------\n" 
     1645"\n" 
     1646"Delays for flushing the routing cache.\n" 
     1647"\n" 
     1648"redirect_load, redirect_number\n" 
     1649"------------------------------\n" 
     1650"\n" 
     1651"Factors which  determine  if  more ICPM redirects should be sent to a specific\n" 
     1652"host. No  redirects  will be sent once the load limit or the maximum number of\n" 
     1653"redirects has been reached.\n" 
     1654"\n" 
     1655"redirect_silence\n" 
     1656"----------------\n" 
     1657"\n" 
     1658"Timeout for redirects. After this period redirects will be sent again, even if\n" 
     1659"this has been stopped, because the load or number limit has been reached.\n" 
     1660"\n" 
     1661"Network Neighbor handling\n" 
     1662"-------------------------\n" 
     1663"\n" 
     1664"Settings about how to handle connections with direct neighbors (nodes attached\n" 
     1665"to the same link) can be found in the directory /proc/sys/net/ipv4/neigh.\n" 
     1666"\n" 
     1667"As we  saw  it  in  the  conf directory, there is a default subdirectory which\n" 
     1668"holds the  default  values, and one directory for each interface. The contents\n" 
     1669"of the  directories  are identical, with the single exception that the default\n" 
     1670"settings contain additional options to set garbage collection parameters.\n" 
     1671"\n" 
     1672"In the interface directories you'll find the following entries:\n" 
     1673"\n" 
     1674"base_reachable_time\n" 
     1675"-------------------\n" 
     1676"\n" 
     1677"A base  value  used for computing the random reachable time value as specified\n" 
     1678"in RFC2461.\n" 
     1679"\n" 
     1680"retrans_time\n" 
     1681"------------\n" 
     1682"\n" 
     1683"The time,  expressed  in  jiffies  (1/100 sec), between retransmitted Neighbor\n" 
     1684"Solicitation messages.  Used  for  address  resolution  and  to determine if a\n" 
     1685"neighbor is unreachable.\n" 
     1686"\n" 
     1687"unres_qlen\n" 
     1688"----------\n" 
     1689"\n" 
     1690"Maximum queue  length  for a pending arp request - the number of packets which\n" 
     1691"are accepted from other layers while the ARP address is still resolved.\n" 
     1692"\n" 
     1693"anycast_delay\n" 
     1694"-------------\n" 
     1695"\n" 
     1696"Maximum for  random  delay  of  answers  to  neighbor solicitation messages in\n" 
     1697"jiffies (1/100  sec). Not yet implemented (Linux does not have anycast support\n" 
     1698"yet).\n" 
     1699"\n" 
     1700"ucast_solicit\n" 
     1701"-------------\n" 
     1702"\n" 
     1703"Maximum number of retries for unicast solicitation.\n" 
     1704"\n" 
     1705"mcast_solicit\n" 
     1706"-------------\n" 
     1707"\n" 
     1708"Maximum number of retries for multicast solicitation.\n" 
     1709"\n" 
     1710"delay_first_probe_time\n" 
     1711"----------------------\n" 
     1712"\n" 
     1713"Delay for  the  first  time  probe  if  the  neighbor  is  reachable.  (see\n" 
     1714"gc_stale_time)\n" 
     1715"\n" 
     1716"locktime\n" 
     1717"--------\n" 
     1718"\n" 
     1719"An ARP/neighbor  entry  is only replaced with a new one if the old is at least\n" 
     1720"locktime old. This prevents ARP cache thrashing.\n" 
     1721"\n" 
     1722"proxy_delay\n" 
     1723"-----------\n" 
     1724"\n" 
     1725"Maximum time  (real  time is random [0..proxytime]) before answering to an ARP\n" 
     1726"request for  which  we have an proxy ARP entry. In some cases, this is used to\n" 
     1727"prevent network flooding.\n" 
     1728"\n" 
     1729"proxy_qlen\n" 
     1730"----------\n" 
     1731"\n" 
     1732"Maximum queue length of the delayed proxy arp timer. (see proxy_delay).\n" 
     1733"\n" 
     1734"app_solcit\n" 
     1735"----------\n" 
     1736"\n" 
     1737"Determines the  number of requests to send to the user level ARP daemon. Use 0\n" 
     1738"to turn off.\n" 
     1739"\n" 
     1740"gc_stale_time\n" 
     1741"-------------\n" 
     1742"\n" 
     1743"Determines how  often  to  check  for stale ARP entries. After an ARP entry is\n" 
     1744"stale it  will  be resolved again (which is useful when an IP address migrates\n" 
     1745"to another  machine).  When  ucast_solicit is greater than 0 it first tries to\n" 
     1746"send an  ARP  packet  directly  to  the  known  host  When  that  fails  and\n" 
     1747"mcast_solicit is greater than 0, an ARP request is broadcasted.\n" 
     1748"\n" 
     1749"2.9 Appletalk\n" 
     1750"-------------\n" 
     1751"\n" 
     1752"The /proc/sys/net/appletalk  directory  holds the Appletalk configuration data\n" 
     1753"when Appletalk is loaded. The configurable parameters are:\n" 
     1754"\n" 
     1755"aarp-expiry-time\n" 
     1756"----------------\n" 
     1757"\n" 
     1758"The amount  of  time  we keep an ARP entry before expiring it. Used to age out\n" 
     1759"old hosts.\n" 
     1760"\n" 
     1761"aarp-resolve-time\n" 
     1762"-----------------\n" 
     1763"\n" 
     1764"The amount of time we will spend trying to resolve an Appletalk address.\n" 
     1765"\n" 
     1766"aarp-retransmit-limit\n" 
     1767"---------------------\n" 
     1768"\n" 
     1769"The number of times we will retransmit a query before giving up.\n" 
     1770"\n" 
     1771"aarp-tick-time\n" 
     1772"--------------\n" 
     1773"\n" 
     1774"Controls the rate at which expires are checked.\n" 
     1775"\n" 
     1776"The directory  /proc/net/appletalk  holds the list of active Appletalk sockets\n" 
     1777"on a machine.\n" 
     1778"\n" 
     1779"The fields  indicate  the DDP type, the local address (in network:node format)\n" 
     1780"the remote  address,  the  size of the transmit pending queue, the size of the\n" 
     1781"received queue  (bytes waiting for applications to read) the state and the uid\n" 
     1782"owning the socket.\n" 
     1783"\n" 
     1784"/proc/net/atalk_iface lists  all  the  interfaces  configured for appletalk.It\n" 
     1785"shows the  name  of the interface, its Appletalk address, the network range on\n" 
     1786"that address  (or  network number for phase 1 networks), and the status of the\n" 
     1787"interface.\n" 
     1788"\n" 
     1789"/proc/net/atalk_route lists  each  known  network  route.  It lists the target\n" 
     1790"(network) that the route leads to, the router (may be directly connected), the\n" 
     1791"route flags, and the device the route is using.\n" 
     1792"\n" 
     1793"2.10 IPX\n" 
     1794"--------\n" 
     1795"\n" 
     1796"The IPX protocol has no tunable values in proc/sys/net.\n" 
     1797"\n" 
     1798"The IPX  protocol  does,  however,  provide  proc/net/ipx. This lists each IPX\n" 
     1799"socket giving  the  local  and  remote  addresses  in  Novell  format (that is\n" 
     1800"network:node:port). In  accordance  with  the  strange  Novell  tradition,\n" 
     1801"everything but the port is in hex. Not_Connected is displayed for sockets that\n" 
     1802"are not  tied to a specific remote address. The Tx and Rx queue sizes indicate\n" 
     1803"the number  of  bytes  pending  for  transmission  and  reception.  The  state\n" 
     1804"indicates the  state  the  socket  is  in and the uid is the owning uid of the\n" 
     1805"socket.\n" 
     1806"\n" 
     1807"The /proc/net/ipx_interface  file lists all IPX interfaces. For each interface\n" 
     1808"it gives  the network number, the node number, and indicates if the network is\n" 
     1809"the primary  network.  It  also  indicates  which  device  it  is bound to (or\n" 
     1810"Internal for  internal  networks)  and  the  Frame  Type if appropriate. Linux\n" 
     1811"supports 802.3,  802.2,  802.2  SNAP  and DIX (Blue Book) ethernet framing for\n" 
     1812"IPX.\n" 
     1813"\n" 
     1814"The /proc/net/ipx_route  table  holds  a list of IPX routes. For each route it\n" 
     1815"gives the  destination  network, the router node (or Directly) and the network\n" 
     1816"address of the router (or Connected) for internal networks.\n" 
     1817"\n" 
     1818"------------------------------------------------------------------------------\n" 
     1819"Summary\n" 
     1820"------------------------------------------------------------------------------\n" 
     1821"Certain aspects  of  kernel  behavior  can be modified at runtime, without the\n" 
     1822"need to  recompile  the kernel, or even to reboot the system. The files in the\n" 
     1823"/proc/sys tree  can  not only be read, but also modified. You can use the echo\n" 
     1824"command to write value into these files, thereby changing the default settings\n" 
     1825"of the kernel.\n" 
     1826"------------------------------------------------------------------------------\n" 
     1827"\n" 
     1828msgstr "" 
     1829"\n" 
     1830"------------------------------------------------------------------------------\n" 
     1831"                      O   A R Q U I V O   D E   S I S T E M A  /proc\n" 
     1832"------------------------------------------------------------------------------\n" 
     1833"/proc/sys    Terrehon Bowden &lt;terrehon@pacbell.net&gt; 7 de Outubro de1999\n" 
     1834"                  Bodo Bauer &lt;bb@ricochet.net&gt;\n" 
     1835"\n" 
     1836"atualização 2.4.x\t  Jorge Nerin &lt;comandante@zaralinux.com&gt;  14 de Novembro de 2000\n" 
     1837"------------------------------------------------------------------------------\n" 
     1838"Versão  1.3                                         Versão do Kernel: 2.2.12\n" 
     1839"\t\t\t\t\t      Kernel version 2.4.0-test11-pre4\n" 
     1840"------------------------------------------------------------------------------\n" 
     1841"\n" 
     1842"índice Remissivo\n" 
     1843"-----------------\n" 
     1844"\n" 
     1845"  0     Prefácio\n" 
     1846"  0.1\tIntrodução/Créditos\n" 
    551847"  0.2\tLegal Stuff\n" 
    561848"\n" 
    … …  
    18183610"\n" 
    18193611"------------------------------------------------------------------------------\n" 
    1820 "Summary\n" 
    1821 "------------------------------------------------------------------------------\n" 
    1822 "Certain aspects  of  kernel  behavior  can be modified at runtime, without the\n" 
    1823 "need to  recompile  the kernel, or even to reboot the system. The files in the\n" 
    1824 "/proc/sys tree  can  not only be read, but also modified. You can use the echo\n" 
    1825 "command to write value into these files, thereby changing the default settings\n" 
    1826 "of the kernel.\n" 
    1827 "------------------------------------------------------------------------------\n" 
    1828 "\n" 
    1829 msgstr "" 
     3612"Resumo\n" 
     3613"------------------------------------------------------------------------------\n" 
     3614"Certos aspectos  do  comportamento do kernel podem ser modificados no tempo de\n" 
     3615"execução, sem precisar recompilar o kernel, ou até mesmo reiniciar o sistema. \n" 
     3616"Os arquivos da árvore /proc/sys não precisam ser apenas lidos, mas podem também\n" 
     3617"serem modificados. Você pode usar o comando Echo para escrever valores  nesses\n" 
     3618"arquivos, com isso alterando as configurações padrão\n" 
     3619"do kernel.\n" 
     3620"------------------------------------------------------------------------------\n" 
     3621"\n" 
    18303622 
    18313623#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2. 
    18323624#: ../app5.xml:0(None) 
    18333625msgid "translator-credits" 
    1834 msgstr "" 
     3626msgstr "Enrico Nicoletto <liverig@gmail.com>, 2009." 
     3627 

  • trunk/l10n/guide/docbook/Intro-Linux/chap3.po

    r32 r33  
    508508"primary><secondary>types</secondary></indexterm> on a Linux system:" 
    509509msgstr "" 
     510"Existem dois tipos principais de partições<indexterm><primary>partitions</" 
     511"primary><secondary>types</secondary></indexterm> em um sistema Linux:" 
    510512 
    511513#: ../chap3.xml:104(para) 
    … …  
    516518"run the system; and" 
    517519msgstr "" 
     520"<emphasis>partição de dados<indexterm><primary>data partition</primary></" 
     521"indexterm></emphasis>: dados usuais do sistema Linux, aqui inclusa a " 
     522"<emphasis>partição root</emphasis>, que contém todas informações " 
     523"necessárias à inicialização e execução do sistema; e" 
    518524 
    519525#: ../chap3.xml:105(para) 
    … …  
    523529"memory on hard disk." 
    524530msgstr "" 
     531"<emphasis>partição swap<indexterm><primary>swap partition</primary></" 
     532"indexterm></emphasis>: uma expansão da memória física do computador, " 
     533"alocação disco rígido para a memória." 
    525534 
    526535#: ../chap3.xml:107(para) 
    … …  
    531540"file system for MS Windows data." 
    532541msgstr "" 
     542"A maior parte dos sistemas contém uma partição root, uma ou mais partições " 
     543"de dados e uma ou mais partições de swap. Sistemas em ambientes mistos " 
     544"podem possuir partições destinadas aos dados de outros sistemas, como, " 
     545"por exemplo, partições FAT ou VFAT para dados do MS Windows." 
    533546 
    534547#: ../chap3.xml:108(para) 
    … …  
    545558"command> utility has built-in help, should you forget these values." 
    546559msgstr "" 
     560"A maioria dos sistemas Linux usa o <command>fdisk<indexterm><primary>fdisk</" 
     561"primary></indexterm></command> quando da instalação para configurar" 
     562"<indexterm><primary>partitions</primary><secondary>creation</secondary></" 
     563"indexterm> o tipo de partição. Como você deve ter notado ao longo dos " 
     564"exercícios do Capítulo 1, isto normalmente acontece automaticamente. Em " 
     565"algumas situações, contudo, você pode não ter tanta sorte. Nestas hipóteses, " 
     566"você precisará selecionar os tipos de partições manualmente ou mesmo " 
     567"realizar o particionamento à mão. As partições Linux padrão possuem o número " 
     568"82 para swap e 83 para dados, as quais, por sua vez, podem ser journaled " 
     569"(ext3) ou convencionais (ext2, em sistemas mais antigos). O utilitário " 
     570"<command>fdisk</command> tem um recurso embutido de ajuda, caso você se " 
     571"esqueça destes valores." 
    547572 
    548573#: ../chap3.xml:109(para) 
    … …  
    553578"systems." 
    554579msgstr "" 
     580"Além destes dois, o Linux também suporta uma larga gama de outros sistemas " 
     581"de arquivos, como, por exemplo, o Reiser, o JFS, o NFS, o FATxx, bem como " 
     582"outros sistemas de arquivos disponíveis em outros sistemas operacionais " 
     583"(proprietários)." 
    555584 
    556585#: ../chap3.xml:111(para) 
    … …  
    565594"user. A standard installation requires about 250 MB for the root partition." 
    566595msgstr "" 
     596"A partição root padrão<indexterm><primary>partitions</" 
     597"primary><secondary>root partition</secondary></indexterm> (representada com " 
     598"uma barra simples<indexterm><primary>slash</primary><secondary>forward</" 
     599"secondary></indexterm>, <emphasis>/</emphasis>) possui em torno de 100/500MB, " 
     600"e contém<indexterm><primary>root partition</primary></indexterm> os arquivos " 
     601"de configuração do sistema, os comandos mais básicos e programas de servidor, " 
     602"as bibliotecas do sistema, espaço temporário e o diretório home do usuário " 
     603"administrador. Uma instalação padrão requer em torno de 250MB para a partição " 
     604"root." 
     605 
    567606 
    568607#: ../chap3.xml:112(para) 
    … …  
    579618"operating systems outside the UNIX world by now." 
    580619msgstr "" 
     620"O espaço de swap<indexterm><primary>swap partition</primary></indexterm> " 
     621"(representado por <emphasis>swap<indexterm><primary>partitions</" 
     622"primary><secondary>swap</secondary></indexterm></emphasis>) somente pode " 
     623"ser acessado pelo próprio sistema, encontrando-se oculta durante uma " 
     624"operação normal. A swap é o sistema que garante, como ocorre em sistemas " 
     625"UNIX, que você pode continuar trabalhando, não importa o que aconteça. No " 
     626"Linux, você jamais verá mensagens como <emphasis>Sem memória, por favor " 
     627"encerre alguns aplicativos e então tente novamente</emphasis>, por conta " 
     628"desta memória adicional. Atualmente diversos outros sistemas operacionais " 
     629"fora do mundo UNIX já também adotaram a técnica da swap ou memória virtual." 
    581630 
    582631#: ../chap3.xml:113(para) 
    … …  
    587636"\"chap_04\"/>." 
    588637msgstr "" 
     638"Naturalmente, o uso da memória no disco rígido é mais lento do que o do " 
     639"chip de memória de um computador, mas este pequeno adicional é um grande " 
     640"conforto. Aprenderemos mais sobre a swap quando discutirmos os processos no " 
     641"<xref linkend=\"chap_04\"/>." 
    589642 
    590643#: ../chap3.xml:114(para) 
    … …  
    596649"with 512 MB of RAM:" 
    597650msgstr "" 
     651"O Linux em geral espera ter o dobro da memória física na forma de swap. " 
     652"Quando da instalação do seu sistema convém que você saiba como fazer isto. " 
     653"Um exemplo<indexterm><primary>swap partition</primary><secondary>example</" 
     654"secondary></indexterm> em um sistema com 512MB de RAM:" 
    598655 
    599656#: ../chap3.xml:116(para) 
    600657msgid "1st possibility: one swap partition of 1 GB" 
    601 msgstr "" 
     658msgstr "1ª possibilidade: uma partição swap de 1GB" 
    602659 
    603660#: ../chap3.xml:117(para) 
    604661msgid "2nd possibility: two swap partitions of 512 MB" 
    605 msgstr "" 
     662msgstr "2ª possibilidade: duas partições swap de 512MB" 
    606663 
    607664#: ../chap3.xml:118(para) 
    … …  
    609666"3rd possibility: with two hard disks: 1 partition of 512 MB on each disk." 
    610667msgstr "" 
     668"3ª possibilidade: com dois discos rígidos: 1 partição de 512MB em cada um." 
    611669 
    612670#: ../chap3.xml:120(para) 
    … …  
    615673"expected." 
    616674msgstr "" 
     675"A última opção é a que fornece melhores resultados quando se espera realizar " 
     676"muitas operações de entrada e saída." 
    617677 
    618678#: ../chap3.xml:121(para) 
    … …  
    623683"Swap space may also depend on your kernel version." 
    624684msgstr "" 
     685"Leia a documentação do seu software para diretrizes específicas. Alguns " 
     686"aplicativos como bases de dados, podem precisar de mais swap. Outras, " 
     687"como alguns sistemas portáteis, podem dispensar a swap por falta de espaço " 
     688"em disco. O espaço de swap pode também depender da versão do seu kernel." 
    625689 
    626690#: ../chap3.xml:122(para) 
    … …  
    632696"accompanying data files." 
    633697msgstr "" 
     698"O kernel também está em uma partição separada em muitas distribuições, vez que " 
     699"ele é o arquivo mais importante no seu sistema. Neste caso, você descobrirá que " 
     700"também possui uma partição <emphasis>/boot<indexterm><primary>boot partition</" 
     701"primary></indexterm></emphasis>, guardando o seu kernel e os arquivos que lhe " 
     702"acompanham." 
    634703 
    635704#: ../chap3.xml:123(para) 
    … …  
    643712"secondary></indexterm> a set pattern:" 
    644713msgstr "" 
     714"O restante do(s) disco(s) rígido(s) é normalmente dividido em partições de " 
     715"dados<indexterm><primary>data partitions</primary></indexterm>, embora pode " 
     716"bem ser que todos os dados não-críticos ao sistema residam em uma só partição, " 
     717"por exemplo, quando se instala uma estação de trabalho padrão. Quando os dados " 
     718"não-críticos são separados em diferentes partições, isto normalmente é feito " 
     719"segundo<indexterm><primary>partitions</primary><secondary>layout</" 
     720"secondary></indexterm> um padrão pré-estabelecido." 
    645721 
    646722#: ../chap3.xml:125(para) 
    647723msgid "a partition for user programs (<emphasis>/usr</emphasis>)" 
    648 msgstr "" 
     724msgstr "uma partição para os programas de usuário (<emphasis>/usr</emphasis>)" 
    649725 
    650726#: ../chap3.xml:126(para) 
    … …  
    652728"a partition containing the users' personal data (<emphasis>/home</emphasis>)" 
    653729msgstr "" 
     730"uma partição contem os dados pessoais dos usuários (<emphasis>/home</emphasis>)" 
    654731 
    655732#: ../chap3.xml:127(para) 
    … …  
    658735"var</emphasis>)" 
    659736msgstr "" 
     737"uma partição para o armazenamento temporário de dados como filas de email ou " 
     738"impressão (<emphasis>/var</emphasis>)." 
    660739 
    661740#: ../chap3.xml:128(para) 
    … …  
    663742"a partition for third party and extra software (<emphasis>/opt</emphasis>)" 
    664743msgstr "" 
     744"uma partição para softwares de terceiros ou extras (<emphasis>/opt</emphasis>)" 
    665745 
    666746#: ../chap3.xml:130(para) 
    … …  
    669749"properties of existing partitions is possible but not advisable." 
    670750msgstr "" 
     751"Criadas as partições, somente é possível criar mais. Mudar o tamanho ou " 
     752"propriedades das partições é possível, mas não é aconselhável." 
    671753 
    672754#: ../chap3.xml:131(para) 
    … …  
    684766"text-based tool for creating partitions and setting their properties." 
    685767msgstr "" 
     768"A divisão dos discos rígidos em partições é determinada pelo administrador do " 
     769"sistema. Em sistemas maiores<indexterm><primary>partitions</" 
     770"primary><secondary>server layout</secondary></indexterm>, ele(a) pode até " 
     771"mesmo decidir acomodar uma única partição em vários discos rígidos, usando " 
     772"os softwares apropriados. A maior parte das distribuições permite configurações " 
     773"padrão otimizadas para estações de trabalho (usuário médio) e também para " 
     774"servidores, mas também aceita partições personalizadas. Ao longo do processo " 
     775"de instalação você pode definir o formato de suas partições usando a ferramenta " 
     776"específica de sua distribuição, que normalmente será um aplicativo gráfico bem " 
     777"intuitivo ou com o <command>fdisk<indexterm><primary>fdisk</primary></indexterm></" 
     778"command>, uma ferramenta-texto para a criação de partições e configuração de " 
     779"suas propriedades." 
    686780 
    687781#: ../chap3.xml:132(para) 
    … …  
    698792"problem situations." 
    699793msgstr "" 
     794"Uma estação de trabalho<indexterm><primary>partitions</" 
     795"primary><secondary>workstation layout</secondary></indexterm> ou instalação " 
     796"cliente é destinada ao uso de uma única pessoa. Os softwares selecionados para " 
     797"a instalação são reflexo desta presunção e buscam os pacotes de usuário mais " 
     798"comuns, como temas de desktop agradáveis, ferramentas de desenvolvimento, " 
     799"clientes de email, softwares de multimídia, web e outros serviços. Tudo é " 
     800"acomodado em uma única partição, espaço de swap com o dobro da RAM é adicionado " 
     801"e a sua estação de trabalho genérica está completa, fornecendo a maior " 
     802"quantidade de espaço em disco possível para uso pessoal, porém com a " 
     803"desvantagem de perda da integridade dos dados em situações problemáticas." 
    700804 
    701805#: ../chap3.xml:133(para) 
    … …  
    707811"will be created on such systems:" 
    708812msgstr "" 
     813"Em um servidor, os dados <indexterm><primary>partitions</" 
     814"primary><secondary>server layout</secondary></indexterm> do sistema são " 
     815"alocados em uma área separada daquela destinada aos dados de usuários. Os " 
     816"programas que fornecem serviços são mantidos em um local diferente daquele " 
     817"em que são guardados os dados manipulados por este serviço. Diferentes " 
     818"partições serão criadas em tais sistemas:" 
    709819 
    710820#: ../chap3.xml:135(para) 
    711821msgid "a partition with all data necessary to boot the machine" 
    712 msgstr "" 
     822msgstr "uma partição com todos os dados necessários à inicialização do sistema" 
    713823 
    714824#: ../chap3.xml:136(para) 
    715825msgid "a partition with configuration data and server programs" 
    716 msgstr "" 
     826msgstr "uma partição com os dados de configuração e os programas de servidor" 
    717827 
    718828#: ../chap3.xml:137(para) 
    … …  
    721831"user mails, an ftp archive etc." 
    722832msgstr "" 
     833"uma ou mais partições contendo os dados do serviços como as tabelas com bases de " 
     834"dados, emails de usuários e arquivos ftp e etc." 
    723835 
    724836#: ../chap3.xml:138(para) 
    725837msgid "a partition with user programs and applications" 
    726 msgstr "" 
     838msgstr "uma partição com os programas de usuário e aplicativos" 
    727839 
    728840#: ../chap3.xml:139(para) 
    729841msgid "one or more partitions for the user specific files (home directories)" 
    730 msgstr "" 
     842msgstr "uma ou mais partições para os arquivos específicos de usuários " 
     843"(diretório home)" 
    731844 
    732845#: ../chap3.xml:140(para) 
    733846msgid "one or more swap partitions (virtual memory)" 
    734 msgstr "" 
     847msgstr "uma ou mais partições swap (memória virtual)" 
    735848 
    736849#: ../chap3.xml:143(para) 
    … …  
    741854"swap is often divided into different swap partitions." 
    742855msgstr "" 
     856"Servidores em geral possuem mais memória e mais espaço de swap. Certos " 
     857"processos de servidor, como bancos de dados, podem requer mais espaço swap " 
     858"do que o normal; procure saber mais na documentação específica. Para uma " 
     859"melhor performance, a swap normalmente é dividida em duas partições distintas." 
    743860 
    744861#: ../chap3.xml:145(title) 
    745862msgid "Mount points" 
    746 msgstr "" 
     863msgstr "Pontos de montagem" 
    747864 
    748865#: ../chap3.xml:146(para) 
    … …  
    759876"partition that holds the following directories:" 
    760877msgstr "" 
     878"Todas as partições<indexterm><primary>partitions</primary><secondary>mount " 
     879"points</secondary></indexterm> são acopladas ao sistema por meio de um ponto " 
     880"de montagem<indexterm><primary>mount point</primary></indexterm>. O ponto de " 
     881"montagem define o local destinado a um conjunto particular de dados no sistema " 
     882"de arquivos. Normalmente, todas as partições estão conctadas por meio da " 
     883"partição <indexterm><primary>partitions</primary><secondary>root partition</" 
     884"secondary></indexterm> <emphasis>root</emphasis>. Nesta partição, que é " 
     885"indicada por uma barra (/), diretórios são criados. Estes diretórios vazios " 
     886"serão o ponto de partida das partições que estão acopladas a eles. Um exemplo: " 
     887"dada uma partição que armazena os seguintes diretórios:" 
    761888 
    762889#: ../chap3.xml:147(screen) 
    … …  
    766893"videos/\t\tcd-images/\tpictures/\n" 
    767894msgstr "" 
     895"\n" 
     896"videos/\t\tcd-imagens/\tfotos/\n" 
    768897 
    769898#: ../chap3.xml:150(para) 
    … …  
    781910"partition of a hard disk, CD, DVD, flash card, USB or other storage device)." 
    782911msgstr "" 
     912"Nós queremos acoplar<indexterm><primary>mount point</" 
     913"primary><secondary>example</secondary></indexterm> esta partição no sistema " 
     914"de arquivos em um diretório chamado <filename>/opt/media</filename>. Para " 
     915"fazer isto, o administrador do sistema tem que garantir que o diretório " 
     916"<filename>/opt/media</filename> existe no sistema. De preferência, ele deve " 
     917"ser um diretório vazio. Como isto é feito será explicado mais adiante neste " 
     918"capítulo. Então, usando o comando <command>mount</command>, o administrador " 
     919"pode acoplar a partição ao sistema. Quando você olhar para o conteúdo do " 
     920"diretório anteriormente vazio <command>mount</command>, ele irá conter os " 
     921"arquivos e diretórios que estão no meio montado (disco rígido ou partição " 
     922"de um disco, CD, DVD, cartão flash, USB ou outro dispositivo de armazenamento)." 
    783923 
    784924#: ../chap3.xml:151(para) 
    … …  
    794934"linkend=\"sect_09_03\"/>." 
    795935msgstr "" 
     936"Ao longo da inicialização do sistema, todas as partições são montadas, como " 
     937"descrito no arquivo <filename>/etc/fstab<indexterm><primary>fstab</primary></" 
     938"indexterm></filename>. Algumas partições não são montadas por padrão, por " 
     939"exemplo quando elas não estão conectadas sempre ao sistema, como é o caso do " 
     940"espaço de armazenamento da sua câmera digital. Se bem configurado, o " 
     941"dispositivo será montado assim que o sistema perceber que ele está conectado, " 
     942"ou ele pode ser montado pelo usuário, p. ex., não é necessário privilégio " 
     943"administrativo para fazê-lo. Há um exemplo no <xref linkend=\"sect_09_03\"/>." 
    796944 
    797945#: ../chap3.xml:153(para) 
    … …  
    808956"better features." 
    809957msgstr "" 
     958"Em um sistema em execução, informações sobre as partições e seus pontos de " 
     959"montagem podem ser exibidos usando o comando <command>df<indexterm><primary>df</" 
     960"primary></indexterm></command> (sigla para <emphasis>disco cheio</emphasis> - " 
     961"full no inglês - ou <emphasis>disco livre</emphasis> - free no inglês). No Linux, " 
     962"o <command>df</command> é a versão GNU e aceita a opção <option>-h</option> ou " 
     963"<emphasis>inteligível por humanos</emphasis> que facilita muito a sua " 
     964"legibilidade. Perceba que todas as máquinas UNIX comerciais normalmente possuem " 
     965"suas próprias versões do <command>df</command> e muitos outros comandos. O seu " 
     966"comportamento é em geral o mesmo, embora as versões GNU das ferramentas mais " 
     967"comuns possuem mais e melhores recursos." 
    810968 
    811969#: ../chap3.xml:154(para) 
    … …  
    818976"indexterm> environments." 
    819977msgstr "" 
     978"O comando <command>df</command> apenas exibe informações sobre partições " 
     979"ativas e não-swap. Aqui estão inclusas as partições de outros sistemas em rede, " 
     980"como no exemplo abaixo, em que os diretórios home estão montados em um arquivo " 
     981"de um servidor na rede, uma situação recorrente no ambiente empresarial" 
     982"<indexterm><primary>df</primary><secondary>example</secondary></indexterm>." 
    820983 
    821984#: ../chap3.xml:156(prompt) 
    822985msgid "freddy:~&gt;" 
    823 msgstr "" 
     986msgstr "freddy:~&gt;" 
    824987 
    825988#: ../chap3.xml:156(command) 
    826989msgid "df -h" 
    827 msgstr "" 
     990msgstr "df -h" 
    828991 
    829992#: ../chap3.xml:155(screen) 
    … …  
    8401003"fs1:/home           8.9G  3.7G  4.7G  44% /.automount/fs1/root/home\n" 
    8411004msgstr "" 
     1005"\n" 
     1006"<placeholder-1/> <placeholder-2/>\n" 
     1007"Siistema de Arquivos   Tam   Uso   Dispon Uso% Montada em\n" 
     1008"/dev/hda8              496M  183M  288M   39% /\n" 
     1009"/dev/hda1              124M  8.4M  109M   8%  /boot\n" 
     1010"/dev/hda5              19G   15G   2.7G   85% /opt\n" 
     1011"/dev/hda6              7.0G  5.4G  1.2G   81% /usr\n" 
     1012"/dev/hda7              3.7G  2.7G  867M   77% /var\n" 
     1013"fs1:/home              8.9G  3.7G  4.7G   44% /.automont/fs1/root/home\n" 
    8421014 
    8431015#: ../chap3.xml:167(title) 
    8441016msgid "More file system layout" 
    845 msgstr "" 
     1017msgstr "Mais sobre a disposição do sistema de arquivos" 
    8461018 
    8471019#: ../chap3.xml:168(title) 
    8481020msgid "Visual" 
    849 msgstr "" 
     1021msgstr "Visual" 
    8501022 
    8511023#: ../chap3.xml:169(para) 
    … …  
    8571029"primary></indexterm> below." 
    8581030msgstr "" 
     1031"Por conveniência, o sistema de arquivos do Linux é comumente pensado como em " 
     1032"uma estrutura de<indexterm><primary>file system</primary><secondary>layout</" 
     1033"secondary></indexterm> árvore. Em um sistema Linux padrão você perceberá que a " 
     1034"disposição via de regra segue o esquema apresentado" 
     1035"<indexterm><primary>directory tree</primary></indexterm> abaixo." 
    8591036 
    8601037#: ../chap3.xml:170(title) 
    8611038msgid "Linux file system layout" 
    862 msgstr "" 
     1039msgstr "Disposição do sistema de arquivos no Linux" 
    8631040 
    8641041#: ../chap3.xml:179(phrase) 
    … …  
    8671044"subdirectories." 
    8681045msgstr "" 
     1046"Panorama gráfico dos principais diretórios do Linux e subdiretórios mais " 
     1047"importantes." 
    8691048 
    8701049#: ../chap3.xml:183(para) 
    … …  
    8751054"even required; they are only a convention." 
    8761055msgstr "" 
     1056"Esta é a apresentação de um sistema RedHat. Dependendo do administrador do " 
     1057"sistema, deste e da missão da máquina UNIX, a estrutura pode varias, " 
     1058"e alguns diretórios podem ser deixados de lado ou adicionados livremente. " 
     1059"Os nomes não são sequer obrigatórios, mas mera convenção." 
    8771060 
    8781061#: ../chap3.xml:184(para) 
    … …  
    8851068"or <quote>the root</quote> of the file system." 
    8861069msgstr "" 
     1070"A árvore do sistema de arquivos começa no tronco ou " 
     1071"<emphasis>barra<indexterm><primary>slash</primary></indexterm></emphasis>, " 
     1072"indicada por uma barra (/). Este diretório, contendo todos os diretórios e " 
     1073"arquivos subjacentes, também é chamado de <emphasis>diretório " 
     1074"root<indexterm><primary>root directory</primary></indexterm></emphasis> " 
     1075"ou <quote>a raiz</quote> do sistema de arquivos." 
    8871076 
    8881077#: ../chap3.xml:185(para) 
    … …  
    8951084"secondary></indexterm>. Let's see what you could run into:" 
    8961085msgstr "" 
     1086"Diretórios que s]ap apenas um nível abaixo do diretório raiz são " 
     1087"precedidos por uma barra, para indicar sua posição e evitar confusão com " 
     1088"outros diretórios que podem ter o mesmo nome. Quando se começa com um novo " 
     1089"sistema, é sempre um boa idéia dar uma olhada na pasta root" 
     1090"<indexterm><primary>root directory</primary><secondary>example</" 
     1091"secondary></indexterm>. Vamos ver com o que você pode se deparar:" 
    8971092 
    8981093#: ../chap3.xml:187(prompt) 
    8991094msgid "emmy:~&gt;" 
    900 msgstr "" 
     1095msgstr "emmy:~&gt;" 
    9011096 
    9021097#: ../chap3.xml:187(command) 
    9031098msgid "cd /" 
    904 msgstr "" 
     1099msgstr "cd /" 
    9051100 
    9061101#: ../chap3.xml:188(prompt) 
    9071102msgid "emmy:/&gt;" 
    908 msgstr "" 
     1103msgstr "emmy:/&gt;" 
    9091104 
    9101105#: ../chap3.xml:188(command) ../chap3.xml:719(command) 
    9111106#: ../chap3.xml:862(command) ../chap3.xml:896(command) 
    9121107msgid "ls" 
    913 msgstr "" 
     1108msgstr "ls" 
    9141109 
    9151110#: ../chap3.xml:186(screen) 
    … …  
    9221117"boot/  etc/  initrd/  lost+found/  mnt/   proc/    sbin/  usr/\n" 
    9231118msgstr "" 
     1119"\n" 
     1120"<placeholder-1/> <placeholder-2/>\n" 
     1121"<placeholder-3/> <placeholder-4/>\n" 
     1122"bin/   dev/  home/    lib/         misc/  opt/     root/  tmp/  var/\n" 
     1123"boot/  etc/  initrd/  lost+found/  mnt/   proc/    sbin/  usr/\n" 
    9241124 
    9251125#: ../chap3.xml:193(title) 
    9261126msgid "Subdirectories of the root directory" 
    927 msgstr "" 
     1127msgstr "Subdiretórios do diretório raiz" 
    9281128 
    9291129#: ../chap3.xml:198(entry) 
    9301130msgid "Content" 
    931 msgstr "" 
     1131msgstr "Conteúdo" 
    9321132 
    9331133#: ../chap3.xml:203(entry) 
    9341134msgid "/bin" 
    935 msgstr "" 
     1135msgstr "/bin" 
    9361136 
    9371137#: ../chap3.xml:204(primary) 
    9381138msgid "bin" 
    939 msgstr "" 
     1139msgstr "bin" 
    9401140 
    9411141#: ../chap3.xml:204(entry) 
    … …  
    9441144"system, the system administrator and the users." 
    9451145msgstr "" 
     1146"Programas<indexterm><placeholder-1/></indexterm> comuns, compartilhados " 
     1147"pelo sistema, pelo administrador e pelos usuários." 
    9461148 
    9471149#: ../chap3.xml:208(entry) 
    9481150msgid "/boot" 
    949 msgstr "" 
     1151msgstr "/boot" 
    9501152 
    9511153#: ../chap3.xml:209(primary) 
    9521154msgid "boot" 
    953 msgstr "" 
     1155msgstr "boot" 
    9541156 
    9551157#: ../chap3.xml:209(filename) 
    9561158msgid "vmlinuz" 
    957 msgstr "" 
     1159msgstr "vmlinuz" 
    9581160 
    9591161#: ../chap3.xml:209(filename) 
    9601162msgid "grub" 
    961 msgstr "" 
     1163msgstr "grub" 
    9621164 
    9631165#: ../chap3.xml:209(application) 
    9641166msgid "GRand Unified Boot" 
    965 msgstr "" 
     1167msgstr "GRand Unified Boot" 
    9661168 
    9671169#: ../chap3.xml:209(entry) 
    … …  
    9721174"different boot-loaders we know today." 
    9731175msgstr "" 
     1176"Os arquivos<indexterm><placeholder-1/></indexterm> de inicialização e o kernel, " 
     1177"<placeholder-2/>. Em algumas distribuições mais recentes, também dados " 
     1178"<placeholder-3/>. O Grub é o carregador <placeholder-4/> e é uma tentativa de " 
     1179"descartar todos os demais carregadores que conhecemos hoje em dia." 
    9741180 
    9751181#: ../chap3.xml:211(entry) 
    9761182msgid "/dev" 
    977 msgstr "" 
     1183msgstr "/dev" 
    9781184 
    9791185#: ../chap3.xml:212(primary) 
    9801186msgid "dev" 
    981 msgstr "" 
     1187msgstr "dev" 
    9821188 
    9831189#: ../chap3.xml:212(entry) 
    … …  
    9861192"peripheral hardware, which are represented as files with special properties." 
    9871193msgstr "" 
     1194"Contém referências<indexterm><placeholder-1/></indexterm> para todos os " 
     1195"periféridos da CPU, que são representados como arquivos com propriedades " 
     1196"especiais." 
    9881197 
    9891198#: ../chap3.xml:214(entry) ../chap3.xml:215(filename) 
    9901199msgid "/etc" 
    991 msgstr "" 
     1200msgstr "/etc" 
    9921201 
    9931202#: ../chap3.xml:215(primary) 
    9941203msgid "etc" 
    995 msgstr "" 
     1204msgstr "etc" 
    9961205 
    9971206#: ../chap3.xml:215(entry) 
    … …  
    10011210"in the Control Panel in Windows" 
    10021211msgstr "" 
     1212"Os arquivos de configuração mais importantes<indexterm><placeholder-1/></" 
     1213"indexterm> do sistema estão no <placeholder-2/>, este diretório contém dados " 
     1214"semelhantes àqueles encontrados no Painel de Controle do Windows." 
    10031215 
    10041216#: ../chap3.xml:216(entry) 
    10051217msgid "/home" 
    1006 msgstr "" 
     1218msgstr "/home" 
    10071219 
    10081220#: ../chap3.xml:217(primary) 
    10091221msgid "home" 
    1010 msgstr "" 
     1222msgstr "home" 
    10111223 
    10121224#: ../chap3.xml:217(entry) 
    … …  
    10141226"Home directories<indexterm><placeholder-1/></indexterm> of the common users." 
    10151227msgstr "" 
     1228"Diretórios home<indexterm><placeholder-1/></indexterm> dos usuários comuns." 
    10161229 
    10171230#: ../chap3.xml:219(entry) 
    10181231msgid "/initrd" 
    1019 msgstr "" 
     1232msgstr "/initrd" 
    10201233 
    10211234#: ../chap3.xml:220(primary) 
    10221235msgid "initrd" 
    1023 msgstr "" 
     1236msgstr "initrd" 
    10241237 
    10251238#: ../chap3.xml:220(entry) 
    … …  
    10281241"for booting. Do not remove!" 
    10291242msgstr "" 
     1243"(em algumas distribuições) Inofrmações<indexterm><placeholder-1/></indexterm>" 
     1244"para inicialização. Não remova!" 
    10301245 
    10311246#: ../chap3.xml:222(entry) 
    10321247msgid "/lib" 
    1033 msgstr "" 
     1248msgstr "/lib" 
    10341249 
    10351250#: ../chap3.xml:223(primary) 
    10361251msgid "lib" 
    1037 msgstr "" 
     1252msgstr "lib" 
    10381253 
    10391254#: ../chap3.xml:223(entry) 
    … …  
    10421257"kinds of programs needed by the system and the users." 
    10431258msgstr "" 
     1259"Arquivos de bibliotecas<indexterm><placeholder-1/></indexterm>, inclui arquivos " 
     1260"para todos os tipos de programas precisos pelo sistemas e usuários." 
    10441261 
    10451262#: ../chap3.xml:225(entry) 
    10461263msgid "/lost+found" 
    1047 msgstr "" 
     1264msgstr "/lost+found" 
    10481265 
    10491266#: ../chap3.xml:226(primary) ../chap3.xml:226(filename) 
    10501267msgid "lost+found" 
    1051 msgstr "" 
     1268msgstr "lost+found" 
    10521269 
    10531270#: ../chap3.xml:226(entry) 
    … …  
    10561273"> in its upper directory. Files that were saved during failures are here." 
    10571274msgstr "" 
     1275"Todas as partições<indexterm><placeholder-1/></indexterm> têm um <placeholder-2/" 
     1276"> em seu diretório superior. Arquivos que são salvos durante falhas ficam " 
     1277"guardados aqui." 
    10581278 
    10591279#: ../chap3.xml:228(entry) 
    10601280msgid "/misc" 
    1061 msgstr "" 
     1281msgstr "/misc" 
    10621282 
    10631283#: ../chap3.xml:229(primary) 
    10641284msgid "misc" 
    1065 msgstr "" 
     1285msgstr "misc" 
    10661286 
    10671287#: ../chap3.xml:229(entry) 
    10681288msgid "For miscellaneous<indexterm><placeholder-1/></indexterm> purposes." 
    1069 msgstr "" 
     1289msgstr "Para propósitos variados<indexterm><placeholder-1/></indexterm>." 
    10701290 
    10711291#: ../chap3.xml:231(entry) 
    10721292msgid "/mnt" 
    1073 msgstr "" 
     1293msgstr "/mnt" 
    10741294 
    10751295#: ../chap3.xml:232(primary) 
    10761296msgid "mnt" 
    1077 msgstr "" 
     1297msgstr "mnt" 
    10781298 
    10791299#: ../chap3.xml:232(entry) 
    … …  
    10821302"file systems, e.g. a CD-ROM or a digital camera." 
    10831303msgstr "" 
     1304"Ponto de montagem<indexterm><placeholder-1/></indexterm> padrão para " 
     1305"sistemas de arquivos externos, p. ex., um CD-ROM ou uma câmera digital." 
    10841306 
    10851307#: ../chap3.xml:234(entry) 
    10861308msgid "/net" 
    1087 msgstr "" 
     1309msgstr "/net" 
    10881310 
    10891311#: ../chap3.xml:235(primary) 
    10901312msgid "net" 
    1091 msgstr "" 
     1313msgstr "net" 
    10921314 
    10931315#: ../chap3.xml:235(entry) 
    … …  
    10961318"remote file systems" 
    10971319msgstr "" 
     1320"Ponto de montagem<indexterm><placeholder-1/></indexterm> padrão para " 
     1321"sistemas de arquivos remotos." 
    10981322 
    10991323#: ../chap3.xml:237(entry) 
    11001324msgid "/opt" 
    1101 msgstr "" 
     1325msgstr "/opt" 
    11021326 
    11031327#: ../chap3.xml:238(primary) 
    11041328msgid "opt" 
    1105 msgstr "" 
     1329msgstr "opt" 
    11061330 
    11071331#: ../chap3.xml:238(entry) 
    … …  
    11101334"party software." 
    11111335msgstr "" 
     1336"Em geral, contém<indexterm><placeholder-1/></indexterm> softwares extras ou " 
     1337"de terceiros." 
    11121338 
    11131339#: ../chap3.xml:240(entry) 
    11141340msgid "/proc" 
    1115 msgstr "" 
     1341msgstr "/proc" 
    11161342 
    11171343#: ../chap3.xml:241(primary) ../chap3.xml:241(filename) 
    11181344#: ../chap3.xml:241(parameter) 
    11191345msgid "proc" 
    1120 msgstr "" 
     1346msgstr "proc" 
    11211347 
    11221348#: ../chap3.xml:241(command) ../chap3.xml:1553(command) 
    11231349msgid "man <placeholder-1/>" 
    1124 msgstr "" 
     1350msgstr "man <placeholder-1/>" 
    11251351 
    11261352#: ../chap3.xml:241(filename) 
    11271353msgid "proc.txt" 
    1128 msgstr "" 
     1354msgstr "proc.txt" 
    11291355 
    11301356#: ../chap3.xml:241(entry) 
    … …  
    11361362"the virtual file system in detail." 
    11371363msgstr "" 
     1364"Um sistema de arquivos virtual<indexterm><placeholder-1/></indexterm> " 
     1365"contendo informações sobre os recursos do sistema. Mais informações sobre " 
     1366"o significado dos arquivos no <placeholder-2/> pode ser obtida informando o " 
     1367"comando <placeholder-3/> em uma janela de terminal. O arquivo <placeholder-4/> " 
     1368"discute o sistema de arquivos virtual em detalhes." 
    11381369 
    11391370#: ../chap3.xml:243(entry) 
    11401371msgid "/root" 
    1141 msgstr "" 
     1372msgstr "/root" 
    11421373 
    11431374#: ../chap3.xml:244(primary) ../chap3.xml:244(emphasis) 
    11441375msgid "root" 
    1145 msgstr "" 
     1376msgstr "root" 
    11461377 
    11471378#: ../chap3.xml:244(entry) 
    … …  
    11511382"home directory of the <placeholder-2/> user." 
    11521383msgstr "" 
     1384"O diretório home do usuário administrativo<indexterm><placeholder-1/></indexterm>. " 
     1385"Note a distinção entre /, o diretório root e /root, a pasta home do " 
     1386"usuário <placeholder-2/>." 
    11531387 
    11541388#: ../chap3.xml:246(entry) 
    11551389msgid "/sbin" 
    1156 msgstr "" 
     1390msgstr "/sbin" 
    11571391 
    11581392#: ../chap3.xml:247(primary) 
    11591393msgid "sbin" 
    1160 msgstr "" 
     1394msgstr "sbin" 
    11611395 
    11621396#: ../chap3.xml:247(entry) 
    … …  
    11651399"the system administrator." 
    11661400msgstr "" 
     1401"Programas<indexterm><placeholder-1/></indexterm> para uso do sistema e do " 
     1402"administrador do sistema." 
    11671403 
    11681404#: ../chap3.xml:249(entry) 
    11691405msgid "/tmp" 
    1170 msgstr "" 
     1406msgstr "/tmp" 
    11711407 
    11721408#: ../chap3.xml:250(primary) 
    11731409msgid "tmp" 
    1174 msgstr "" 
     1410msgstr "tmp" 
    11751411 
    11761412#: ../chap3.xml:250(entry) 
    … …  
    11791415"system, cleaned upon reboot, so don't use this for saving any work!" 
    11801416msgstr "" 
     1417"Espaço temporário<indexterm><placeholder-1/></indexterm> para uso do " 
     1418"sistema, é limpo quando da reinicialização, portanto, não use para " 
     1419"armazenar nenhum tipo de trabalho." 
    11811420 
    11821421#: ../chap3.xml:252(entry) 
    11831422msgid "/usr" 
    1184 msgstr "" 
     1423msgstr "/usr" 
    11851424 
    11861425#: ../chap3.xml:253(primary) 
    11871426msgid "usr" 
    1188 msgstr "" 
     1427msgstr "usr" 
    11891428 
    11901429#: ../chap3.xml:253(entry) 
    … …  
    11931432"etc. for all user-related programs." 
    11941433msgstr "" 
     1434"Programas<indexterm><placeholder-1/></indexterm>,, bibliotecas, documentação " 
     1435"e etc para todos os programas de usuários." 
    11951436 
    11961437#: ../chap3.xml:255(entry) 
    11971438msgid "/var" 
    1198 msgstr "" 
     1439msgstr "/var" 
    11991440 
    12001441#: ../chap3.xml:256(primary) 
    12011442msgid "var" 
    1202 msgstr "" 
     1443msgstr "var" 
    12031444 
    12041445#: ../chap3.xml:256(entry) 
    … …  
    12091450"Internet, or to keep an image of a CD before burning it." 
    12101451msgstr "" 
     1452"Espaço de armazenamento de todos os arquivos variáveis<indexterm>" 
     1453"<placeholder-1/></indexterm> e temporários criados pelos usuários, como os " 
     1454"arquivos de log, fila de emil, área de spooler de impressão, espaço para " 
     1455"armazenamento temporário de arquivos baixados da internet ou para gravar a " 
     1456"imagem de um CD antes de gravá-la no disco." 
    12111457 
    12121458#: ../chap3.xml:261(para) 
    … …  
    12181464"indexterm> on this partition:" 
    12191465msgstr "" 
     1466"Como descobrir em qual partição um diretório está? Usando o comando " 
     1467"<command>df</command> com um ponto (.) de opção exibe a partição a que " 
     1468"pertence o diretório atual e informa sobre a quantidade de espaço em uso " 
     1469"<indexterm><primary>df</primary><secondary>example</secondary></" 
     1470"indexterm> na partição:" 
    12201471 
    12211472#: ../chap3.xml:263(prompt) 
    12221473msgid "sandra:/lib&gt;" 
    1223 msgstr "" 
     1474msgstr "sandra:/lib&gt;" 
    12241475 
    12251476#: ../chap3.xml:263(command) 
    12261477msgid "df -h ." 
    1227 msgstr "" 
     1478msgstr "df -h ." 
    12281479 
    12291480#: ../chap3.xml:262(screen) 
    … …  
    12351486"/dev/hda7             980M  163M  767M  18% /\n" 
    12361487msgstr "" 
     1488"\n" 
     1489"<placeholder-1/> <placeholder-2/>\n" 
     1490"Sistema de arquivos   Tam   Uso   Dispon Uso% Montado em\n" 
     1491"/dev/hda7             980M  163M  767M   18%  /\n" 
    12371492 
    12381493#: ../chap3.xml:267(para) 
    … …  
    12431498"other options)." 
    12441499msgstr "" 
     1500"Como regra geral, todos os diretórios dentro do diretório raiz estão na " 
     1501"partição root, a não ser que ele possua uma entrada em separado na lista " 
     1502"completa do comando <command>df</command> (ou <command>df <option>-h</option></" 
     1503"command> sem outras opções)." 
    12451504 
    12461505#: ../chap3.xml:268(para) 
    … …  
    12491508"primary><secondary>hierarchy</secondary></indexterm></parameter></command>." 
    12501509msgstr "" 
     1510"Leia mais em <command>man <parameter>hier<indexterm><primary>file system</" 
     1511"primary><secondary>hierarchy</secondary></indexterm></parameter></command>." 
    12511512 
    12521513#: ../chap3.xml:271(title) 
    12531514msgid "The file system in reality" 
    1254 msgstr "" 
     1515msgstr "O sistema de arquivos na realidade" 
    12551516 
    12561517#: ../chap3.xml:272(para) 
    … …  
    12611522"structures." 
    12621523msgstr "" 
     1524"Para a maior parte dos usuários e para as tarefas mais comuns de um " 
     1525"administrador de sistemas, é suficiente aceitar que os arquivos e diretórios " 
     1526"estão ordenados em uma estrutura de árvore. O computador, contudo, não entende " 
     1527"absolutamente nada sobre árvores ou estruturas em árvore." 
    12631528 
    12641529#: ../chap3.xml:273(para) 
    … …  
    12731538"file: to whom this file belongs, and where is it located on the hard disk." 
    12741539msgstr "" 
     1540"Toda partição<indexterm><primary>partitions</primary><secondary>file " 
     1541"system</secondary></indexterm> possui seu próprio sistema de arquivos. " 
     1542"Imaginando todos estes sistemas de arquivos juntos, podemos ter uma idéia " 
     1543"de um sistema em estrutura de árvore, mas ele não é tão simples assim. Em " 
     1544"um sistema de arquivos, um arquivo é representado por um <emphasis>inode" 
     1545"<indexterm><primary>inode</primary><secondary>definition</secondary></" 
     1546"indexterm></emphasis>, uma espécie de número de série contendo informações " 
     1547"sobre os dados que o arquivo contém: a quem ele pertence e em que local do " 
     1548"disco ele está armazenado." 
    12751549 
    12761550#: ../chap3.xml:274(para) 
    … …  
    12791553"partitions, files with the same inode number can exist." 
    12801554msgstr "" 
     1555"Toda partição possui seu próprio conjunto de inodes; em um sistema com " 
     1556"múltiplas partições, podem existir arquivos com o mesmo número inode." 
    12811557 
    12821558#: ../chap3.xml:275(para) 
    … …  
    12921568"storage." 
    12931569msgstr "" 
     1570"Cada inode descreve a estrutura dos dados no disco rígido, armazenando as " 
     1571"propriedades de um arquivo, incluindo a localização física dos dados. " 
     1572"Quando um disco rígido é inicializado para aceitar o armazenamento de dados, " 
     1573"em geral durante o processo de instalação do sistema, um número fixo de " 
     1574"inodes por partição é criado. Este número será a quantidade máxima de arquivos, " 
     1575"de todos os tipos (incluindo diretórios, arquivos especiais, links e etc.) que " 
     1576"podem existir ao mesmo tempo naquela partição. Via de regra existe 1 inode para " 
     1577"cada 2 a 8 quilobytes de espaço." 
    12941578 
    12951579#: ../chap3.xml:276(para) 
    … …  
    12991583"information</secondary></indexterm> information:" 
    13001584msgstr "" 
     1585"Quando um novo arquivo é criado, ele recebe livremente um inode. Neste inode " 
     1586"se encontram as seguintes<indexterm><primary>inode</primary><secondary>stored " 
     1587"information</secondary></indexterm> informações:" 
    13011588 
    13021589#: ../chap3.xml:278(para) 
    13031590msgid "Owner and group owner of the file." 
    1304 msgstr "" 
     1591msgstr "Proprietário e grupo proprietário do arquivo." 
    13051592 
    13061593#: ../chap3.xml:279(para) 
    13071594msgid "File type (regular, directory, ...)" 
    1308 msgstr "" 
     1595msgstr "Tipo de arquivo (normal, diretório, ...)" 
    13091596 
    13101597#: ../chap3.xml:280(para) 
    13111598msgid "Permissions on the file <xref linkend=\"sect_03_04_01\"/>" 
    1312 msgstr "" 
     1599msgstr "Permissões do arquivo <xref linkend=\"sect_03_04_01\"/>" 
    13131600 
    13141601#: ../chap3.xml:281(para) 
    13151602msgid "Date and time of creation, last read and change." 
    1316 msgstr "" 
     1603msgstr "Data e hora da criação, do último acesso e mudança" 
    13171604 
    13181605#: ../chap3.xml:282(para) 
    13191606msgid "Date and time this information has been changed in the inode." 
    1320 msgstr "" 
     1607msgstr "Data e hora em que estas informações foram alteradas no inode." 
    13211608 
    13221609#: ../chap3.xml:283(para) 
    13231610msgid "Number of links to this file (see later in this chapter)." 
    1324 msgstr "" 
     1611msgstr "Número de links para este arquivo (veja mais adiante neste capítulo)." 
    13251612 
    13261613#: ../chap3.xml:284(para) 
    13271614msgid "File size" 
    1328 msgstr "" 
     1615msgstr "Tamanho do arquivo" 
    13291616 
    13301617#: ../chap3.xml:285(para) 
    13311618msgid "An address defining the actual location of the file data." 
    1332 msgstr "" 
     1619msgstr "Um endereço para o local onde os dados do arquivo estão de fato " 
     1620"armazenados." 
    13331621 
    13341622#: ../chap3.xml:288(para) 
    … …  
    13401628"option> option to ls. The inodes have their own separate space on the disk." 
    13411629msgstr "" 
     1630"A única informação que não está em um inode é o nome do arquivo e o diretório. " 
     1631"Estas informações são guardadas em arquivos diretórios especiais. Comparando " 
     1632"os nomes dos arquivos e os números de inode, o sistema pode construir uma " 
     1633"estrutura de árvora que os usuários possam entender. É possível exibir os " 
     1634"números de inode usando a opção <option>-i</option> ao comando ls. Os inodes " 
     1635"possuem seu próprio espaço em disco." 
    13421636 
    13431637#: ../chap3.xml:293(title) 
    13441638msgid "Orientation in the file system" 
    1345 msgstr "" 
     1639msgstr "Orientação no sistema de arquivos" 
    13461640 
    13471641#: ../chap3.xml:294(title) 
    13481642msgid "The path" 
    1349 msgstr "" 
     1643msgstr "O caminho (path)" 
    13501644 
    13511645#: ../chap3.xml:295(para) 
    … …  
    13601654"the current directory." 
    13611655msgstr "" 
     1656"Quando você quer que o sistema<indexterm><primary>file system</" 
     1657"primary><secondary>orientation</secondary></indexterm> execute um comando, " 
     1658"quase nunca é necessário informar o caminho completo para ele. Por exemplo, " 
     1659"nós sabemos que o comando <command>ls</command> está no diretório <filename>/" 
     1660"bin</filename> (verifique com o <command>which <option>-a</" 
     1661"option><parameter>ls</parameter></command>), porém não é necessário informar " 
     1662"o comando <command>/bin/ls</command> para que o computador exiba o conteúdo " 
     1663"do diretório atual." 
    13621664 
    13631665#: ../chap3.xml:296(para) 
    … …  
    13741676"secondary></indexterm></varname>:" 
    13751677msgstr "" 
     1678"A variável de ambiente <varname>PATH<indexterm><primary>PATH</primary></" 
     1679"indexterm></varname> toma conta disto. Esta variável lista os diretórios " 
     1680"no sistema onde arquivos executáveis podem ser encontrados, poupando ao " 
     1681"usuário o tempo de digitar e memorizar a localização dos comandos. Assim, " 
     1682"o caminho contém diversos diretórios que possuem <filename>bin</" 
     1683"filename> em alguma parte de seus nomes, como o usuário abaixo demonstra. " 
     1684"O comando <command>echo<indexterm><primary>echo</primary></indexterm></" 
     1685"command> é usado para exibir o conteúdo (<quote>$</quote>) da variável " 
     1686"<varname>PATH<indexterm><primary>PATH</primary><secondary>example</" 
     1687"secondary></indexterm></varname>:" 
    13761688 
    13771689#: ../chap3.xml:298(prompt) 
    13781690msgid "rogier:&gt;" 
    1379 msgstr "" 
     1691msgstr "rogier:&gt;" 
    13801692 
    13811693#: ../chap3.xml:298(command) ../chap3.xml:326(command) 
    13821694#: ../chap3.xml:975(command) 
    13831695msgid "echo $PATH" 
    1384 msgstr "" 
     1696msgstr "echo $PATH" 
    13851697 
    13861698#: ../chap3.xml:297(screen) 
    … …  
    13911703"/opt/local/bin:/usr/X11R6/bin:/usr/bin:/usr/sbin/:/bin\n" 
    13921704msgstr "" 
     1705"\n" 
     1706"<placeholder-1/> <placeholder-2/>\n" 
     1707"/opt/local/bin:/usr/X11R6/bin:/usr/bin:/usr/sbin/:/bin\n" 
    13931708 
    13941709#: ../chap3.xml:301(para) 
    … …  
    14051720"variable:" 
    14061721msgstr "" 
     1722"Neste exemplo, os diretórios <filename>/opt/local/bin</filename>, " 
     1723"<filename>/usr/X11R6/bin</filename>, <filename>/usr/bin</filename>, " 
     1724"<filename>/usr/sbin</filename> e <filename>/bin</filename> são " 
     1725"subseqÃŒencialmente pesquisados em busca do programa desejado. Assim que uma " 
     1726"ocorrência é encontrada a busca é interrompida, ainda que nem todos os " 
     1727"diretórios no caminho tenham sido pesquisados. Isto pode levar a alguns " 
     1728"percalços. No primeiro exemplo abaixo, a usuária sabe que existe um programa " 
     1729"chamado <command>sendsms</command> usado para o envio de mensagens SMS e que " 
     1730"outro usuário no mesmo sistema consegue usá-lo, porém ela não consegue. A " 
     1731"diferença está na configuração da variável <varname>PATH</varname>:" 
    14071732 
    14081733#: ../chap3.xml:303(prompt) 
    14091734msgid "[jenny@blob jenny]$" 
    1410 msgstr "" 
     1735msgstr "[jenny@blob jenny]$" 
    14111736 
    14121737#: ../chap3.xml:303(command) 
    14131738msgid "sendsms" 
    1414 msgstr "" 
     1739msgstr "sendsms" 
    14151740 
    14161741#: ../chap3.xml:302(screen) 
    … …  
    14311756"/usr/X11R6/bin:/usr/bin:/usr/sbin:/bin:/sbin\n" 
    14321757msgstr "" 
     1758"\n" 
     1759"<placeholder-1/> <placeholder-2/>\n" 
     1760"bash: sendsms: comando não encontrado\n" 
     1761"[jenny@blob jenny]$ echo $PATH\n" 
     1762"/bin:/usr/bin:/usr/bin/X11:/usr/X11R6/bin:/home/jenny/bin\n" 
     1763"[jenny@blob jenny]$ su - tony\n" 
     1764"Senha:\n" 
     1765"tony:~&gt;which sendsms\n" 
     1766"sendsms is /usr/local/bin/sendsms\n" 
     1767"\n" 
     1768"tony:~&gt;echo $PATH\n" 
     1769"/home/tony/bin.Linux:/home/tony/bin:/usr/local/bin:/usr/local/sbin:\\\n" 
     1770"/usr/X11R6/bin:/usr/bin:/usr/sbin:/bin:/sbin\n" 
    14331771 
    14341772#: ../chap3.xml:316(para) 
    … …  
    14391777"password." 
    14401778msgstr "" 
     1779"Perceba o uso do <command>su<indexterm><primary>su</primary></indexterm></" 
     1780"command> (switch user - alterar usuário), que permite a execução de um shell " 
     1781"no ambiente de outro usuário, desde que a senha deste usuário seja conhecida." 
    14411782 
    14421783#: ../chap3.xml:317(para) 
    … …  
    14481789"other." 
    14491790msgstr "" 
     1791"Uma barra invertida<indexterm><primary>slash</primary><secondary>backslash</" 
     1792"secondary></indexterm> indica a " 
     1793"continuação<indexterm><primary>backslash</primary></indexterm> de uma linha na " 
     1794"próxima, sem um <keycap>Enter</keycap> separando ambas." 
    14501795 
    14511796#: ../chap3.xml:318(para) 
    … …  
    14571802"+<keycap>C</keycap> combination:" 
    14581803msgstr "" 
     1804"No próximo exemplo, um usuário quer chamar o " 
     1805"<command>wc<indexterm><primary>wc</primary></indexterm></command> (word " 
     1806"count - contador de palavras) para verificar o número de linhas em um " 
     1807"arquivo, mas nada acontece e ele tem que desistir da ação usando a combinação " 
     1808"<keycap>Ctrl</keycap>+<keycap>C</keycap>." 
    14591809 
    14601810#: ../chap3.xml:320(prompt) ../chap3.xml:323(prompt) ../chap3.xml:326(prompt) 
    14611811#: ../chap3.xml:333(prompt) 
    14621812msgid "jumper:~&gt;" 
    1463 msgstr "" 
     1813msgstr "jumper:~&gt;" 
    14641814 
    14651815#: ../chap3.xml:320(command) 
    14661816msgid "wc -l test" 
    1467 msgstr "" 
     1817msgstr "wc -l test" 
    14681818 
    14691819#: ../chap3.xml:323(command) 
    14701820msgid "which wc" 
    1471 msgstr "" 
     1821msgstr "which wc" 
    14721822 
    14731823#: ../chap3.xml:319(screen) 
    … …  
    14851835"/usr/bin:/usr/sbin:/bin:/sbin\n" 
    14861836msgstr "" 
     1837"\n" 
     1838"<placeholder-1/> <placeholder-2/>\n" 
     1839"\n" 
     1840"(Ctrl-C)\n" 
     1841"<placeholder-3/> <placeholder-4/>\n" 
     1842"wc is hashed (/home/jumper/bin/wc)\n" 
     1843"\n" 
     1844"<placeholder-5/> <placeholder-6/>\n" 
     1845"/home/jumper/bin:/usr/local/bin:/usr/local/sbin:/usr/X11R6/bin:\\\n" 
     1846"/usr/bin:/usr/sbin:/bin:/sbin\n" 
    14871847 
    14881848#: ../chap3.xml:330(para) 
    … …  
    15011861"<command>which</command> command." 
    15021862msgstr "" 
     1863"O uso do comando <command>which<indexterm><primary>which</primary></" 
     1864"indexterm></command> demonstra que este usuário tem um diretório " 
     1865"<filename>bin</filename> em sua pasta home, a qual, por sua vez, também tem " 
     1866"um programa chamado <command>wc</command>. Uma vez que a sua pasta home " 
     1867"precede o restante do path, quando da chamada pelo <command>wc</command>, " 
     1868"este programa <quote>caseiro</quote> é executado, com uma entrada que ele " 
     1869"provavelmente não entende, de forma que é preciso interrompê-lo. Há diversas " 
     1870"formas de resolver este problema (sempre há diversas formas de resolver um " 
     1871"problema no UNIX/Linux): uma saída seria renomear o <command>wc</command> da " 
     1872"home do usuário, outra seria fornecer o caminho completo para o comando que " 
     1873"ele deseja executar, usando o <command>which</command>, com a opção " 
     1874"<option>-a</option> para saber os caminhos." 
    15031875 
    15041876#: ../chap3.xml:331(para) 
    … …  
    15081880"primary><secondary>configuration</secondary></indexterm> last:" 
    15091881msgstr "" 
     1882"Se o usuário usa os programas em outros diretórios com mais freqÌência, é " 
     1883"possível mudar o seu caminho para que ele busque em seus próprios diretórios " 
     1884"por último <indexterm><primary>PATH</primary><secondary>configuration</" 
     1885"secondary></indexterm>:" 
    15101886 
    15111887#: ../chap3.xml:333(command) 
    … …  
    15141890"sbin:/bin:/sbin:/home/jumper/bin" 
    15151891msgstr "" 
     1892"export PATH=/usr/local/bin:/usr/local/sbin:/usr/X11R6/bin:\\ /usr/bin:/usr/" 
     1893"sbin:/bin:/sbin:/home/jumper/bin" 
    15161894 
    15171895#: ../chap3.xml:336(title) 
    15181896msgid "Changes are not permanent!" 
    1519 msgstr "" 
     1897msgstr "Mudanças não são definitivas!" 
    15201898 
    15211899#: ../chap3.xml:337(para) 
    … …  
    15281906"permanent, adding these lines to the shell configuration files." 
    15291907msgstr "" 
     1908"Perceba que quando se usa o comando <command>export</command> em um shell, " 
     1909"as mudanças realizadas são temporárias, válidas apenas durante esta sessão " 
     1910"(até que você realize o logout). Ao abrir novas sessões, mesmo enquanto a " 
     1911"atual ainda está em execução, não importará o novo caminho para esta nova " 
     1912"sessão. Nós veremos na <xref linkend=\"sect_07_02\"/> como nós podemos " 
     1913"tornar permanentes estas mudanças ao ambiente, adicionando estas linhas aos " 
     1914"arquivos de configuração do shell." 
    15301915 
    15311916#: ../chap3.xml:340(title) 
    15321917msgid "Absolute and relative paths" 
    1533 msgstr "" 
     1918msgstr "Caminhos absolutos e relativos" 
    15341919 
    15351920#: ../chap3.xml:341(para) 
    … …  
    15431928"comply." 
    15441929msgstr "" 
     1930"Um caminho<indexterm><primary>paths</primary><secondary>types</secondary></" 
     1931"indexterm>, que é a trilha que você deve seguir pela estrutura de árvore para " 
     1932"alcançar um determinado arquivo, pode ser descrito como se começasse pelo " 
     1933"tronco da árvore (o / ou diretório raiz). Nesta hipótese, o caminho se inicia " 
     1934"com uma barra e denomina-se caminho absoluto<indexterm><primary>absolute paths</" 
     1935"primary></indexterm>, vez que não há possibilidade de erro: apenas um arquivo " 
     1936"no sistema pode se adequar àquela descrição." 
    15451937 
    15461938#: ../chap3.xml:342(para) 
    … …  
    15521944"relative<indexterm><primary>relative paths</primary></indexterm>." 
    15531945msgstr "" 
     1946"No outro caso, o caminho não se inicia com uma barra e há possibilidade de " 
     1947"confusão entre <filename>~/bin/wc</filename> (na pasta home do usuário) e " 
     1948"<filename>bin/wc</filename> no <filename>/usr</filename>, do exemplo " 
     1949"anterior. Caminhos que não se iniciam com uma barra são sempre relativos " 
     1950"<indexterm><primary>relative paths</primary></indexterm>." 
    15541951 
    15551952#: ../chap3.xml:343(para) 
    … …  
    15591956"primary><secondary>examples</secondary></indexterm> examples:" 
    15601957msgstr "" 
     1958"Nos caminhos relativos nós também usamos as indicações . e .. para os " 
     1959"diretórios atual e pai. Um par de exemplos práticos<indexterm><primary>paths</" 
     1960"primary><secondary>examples</secondary></indexterm>:" 
    15611961 
    15621962#: ../chap3.xml:346(para) 
    … …  
    15681968"program elsewhere on the system." 
    15691969msgstr "" 
     1970"Quando você quer compilar o código fonte, a documentação de instalação muitas " 
     1971"vezes o instrui a executar o comando <command>./configure</command>, que " 
     1972"executa o programa <command>configure</command> localizado no diretório " 
     1973"atual (que vem com novo código), ao invés de executar outro programa " 
     1974"configure localizado em outra parte do sistema." 
    15701975 
    15711976#: ../chap3.xml:347(para) 
    … …  
    15741979"movable to another place:" 
    15751980msgstr "" 
     1981"Em arquivos HTML, caminhos relativos são muitas vezes usados para tornar " 
     1982"um conjunto de páginas facilmente alocáveis em outro lugar:" 
    15761983 
    15771984#: ../chap3.xml:348(screen) 
    … …  
    15811988"&lt;img alt=\"Garden with trees\" src=\"../images/garden.jpg\"&gt;\n" 
    15821989msgstr "" 
     1990"\n" 
     1991"&lt;img alt=\"Jardim com árvores\" src=\"../imagens/jardim.jpg\"&gt;\n" 
    15831992 
    15841993#: ../chap3.xml:352(para) 
    15851994msgid "Notice the difference one more time:" 
    1586 msgstr "" 
     1995msgstr "Perceba a diferença mais uma vez:" 
    15871996 
    15881997#: ../chap3.xml:354(prompt) 
    15891998msgid "theo:~&gt;" 
    1590 msgstr "" 
     1999msgstr "theo:~&gt;" 
    15912000 
    15922001#: ../chap3.xml:354(command) 
    15932002msgid "ls /mp3" 
    1594 msgstr "" 
     2003msgstr "ls /mp3" 
    15952004 
    15962005#: ../chap3.xml:353(screen) 
    … …  
    16032012"oriental/  pop/  sixties/\n" 
    16042013msgstr "" 
     2014"\n" 
     2015"<placeholder-1/> <placeholder-2/>\n" 
     2016"ls: /mp3: O arquivo ou diretório não existe\n" 
     2017"theo:~&gt;ls mp3/\n" 
     2018"oriental/  pop/  sessenta/\n" 
    16052019 
    16062020#: ../chap3.xml:362(title) 
    16072021msgid "The most important files and directories" 
    1608 msgstr "" 
     2022msgstr "Os arquivos e diretórios mais importantes" 
    16092023 
    16102024#: ../chap3.xml:363(title) 
    16112025msgid "The kernel" 
    1612 msgstr "" 
     2026msgstr "O kernel" 
    16132027 
    16142028#: ../chap3.xml:364(para) 
    … …  
    16242038"to know that the kernel is the most important file on the system." 
    16252039msgstr "" 
     2040"O kernel<indexterm><primary>kernel</primary><secondary>functions</" 
     2041"secondary></indexterm> é o coração de um sistema. Ele gerencia as " 
     2042"comunicações entre o hardware e os periféricos. O kernel também garante que " 
     2043"os processos e daemons (processos de serviços) são iniciados e finalizados " 
     2044"exatamente quando necessário for. O kernel realiza uma série de outras " 
     2045"tarefas importantes, tantas que há uma lista de emails especial para os " 
     2046"desenvolvedores do kernel apenas para este assunto, na qual uma imensa " 
     2047"quantidade de informações é compartilhada. Por enquanto, é basta saber " 
     2048"que o kernel é o arquivo mais importante no sistema." 
    16262049 
    16272050#: ../chap3.xml:366(title) 
    16282051msgid "The shell" 
    1629 msgstr "" 
     2052msgstr "O shell" 
    16302053 
    16312054#: ../chap3.xml:367(title) 
    16322055msgid "What is a shell?" 
    1633 msgstr "" 
     2056msgstr "O que é um shell?" 
    16342057 
    16352058#: ../chap3.xml:368(para) 
    … …  
    16452068"its users</quote>. A shell is much more than that." 
    16462069msgstr "" 
     2070"Quando eu estava procurando<indexterm><primary>shell</primary><secondary>" 
     2071"definition</secondary></indexterm> por uma explicação apropriada do conceito " 
     2072"de <emphasis>shell</emphasis>, encontrei mais problemas do que o esperado. " 
     2073"Todos os tipos de definições estão disponíveis, desde simples ilustrações " 
     2074"como <quote>o shell é o volante do carro</quote>, até a vaga definição do " 
     2075"manual do Bash que diz que <quote>o bash é um intérprete da linha de comando " 
     2076"compatível com o sh</quote> ou a ainda mais obscura expressão, <quote>o " 
     2077"shell gerencia a interação entre o usuário e o sistema</quote>. Um shell é " 
     2078"muito mais do que isto." 
    16472079 
    16482080#: ../chap3.xml:369(para) 
    … …  
    16562088"always less capable than the command or commands that form the backend." 
    16572089msgstr "" 
     2090"A melhor comparação que se pode fazer é dizer que o shell é um meio de " 
     2091"falar com o computador, um idioma. A maior parte dos usuários conhece um " 
     2092"outro idioma, aquele de selecionar-clicar do desktop. Entretanto, naquele " 
     2093"idioma o computador é quem direciona a conversa, enquanto o usuário tem o " 
     2094"papel passivo de escolher as tarefas dentre as que lhe são apresentadas. " 
     2095"É muito difícil para um programador incluir todas as opções e possíveis " 
     2096"usos da linha de comando em um formato gráfico. Por conta disto, as " 
     2097"interfaces gráficas são, quase sempre, menos capazes do que o comando ou " 
     2098"os comandos que realizam as tarefas por detrás da casca." 
    16582099 
    16592100#: ../chap3.xml:370(para) 
    … …  
    16652106"additional asset is that the shell allows for task automation." 
    16662107msgstr "" 
     2108"O shell, por outro lado, é um meio avançado de comunicação com o sistema, " 
     2109"porquanto ele proporciona a possibilidade de uma comunicação verdadeiramente " 
     2110"bilateral, em que ambas as partes tomam iniciativas. Ambos os interlocutores " 
     2111"são iguais, de modo que é possível testar novas idéias. O shell permite que " 
     2112"o usuário manipule o sistema de uma forma bem flexível. Outro fator é a " 
     2113"possibilidade de automação de tarefas pelo shell." 
    16672114 
    16682115#: ../chap3.xml:372(title) 
    16692116msgid "Shell types" 
    1670 msgstr "" 
     2117msgstr "Tipos de shell" 
    16712118 
    16722119#: ../chap3.xml:373(para) 
    … …  
    16762123"secondary></indexterm> types:" 
    16772124msgstr "" 
     2125"Assim como as pessoas conhecem diferentes idiomas ou dialetos, o computador " 
     2126"conhece diferentes tipos de shells<indexterm><primary>shell</" 
     2127"primary><secondary>types</secondary></indexterm>:" 
    16782128 
    16792129#: ../chap3.xml:375(para) 
    … …  
    16862136"emulate this shell." 
    16872137msgstr "" 
     2138"<command>sh<indexterm><primary>sh</primary></indexterm></command> ou " 
     2139"<application>Bourne Shell<indexterm><primary>Bourne Shell</primary></" 
     2140"indexterm></application>: o shell original, ainda usado em sistemas UNIX e " 
     2141"em ambientes nele baseados. Este é o shell básico, um pequeno programa com " 
     2142"poucos recursos. Quando acionado em modo compatível com o POSIX, o " 
     2143"<command>bash</command> irá emular este shell." 
    16882144 
    16892145#: ../chap3.xml:376(para) 
    … …  
    17032159"command>." 
    17042160msgstr "" 
     2161"<command>bash<indexterm><primary>bash</primary></indexterm></command> ou " 
     2162"<application>Bourne Again SHell<indexterm><primary>Bourne Again SHell</" 
     2163"primary></indexterm></application>: é o shell padrão do GNU, intuitivo e " 
     2164"flexível. Provavelmente o mais indicado a usuários iniciantes, embora " 
     2165"também seja simultaneamente uma ferramenta poderosa para os usuários " 
     2166"avançados e profissionais. No Linux, o <command>bash</command> é o shell " 
     2167"padrão para usuários comuns. Este shell é chamado de <emphasis>sucessor</" 
     2168"emphasis> do shell <application>Bourne</application>, com o incremento de " 
     2169"muitos add-ons e plugins. Isto implica que o <application>Bourne " 
     2170"Again SHell</application> é compatível com o shell <application>Bourne</" 
     2171"application>: os comandos que funcionam no <command>sh</command> também " 
     2172"irão funcionar no <command>bash</command>. Entretanto, a recíproca nem " 
     2173"sempre é verdadeira. Todos os exemplos e exercícios neste livro usam o " 
     2174"<command>bash</command>." 
    17052175 
    17062176#: ../chap3.xml:377(para) 
    … …  
    17112181"language. Sometimes asked for by programmers." 
    17122182msgstr "" 
     2183"<command>csh<indexterm><primary>csh</primary></indexterm></command> ou " 
     2184"<application>C Shell<indexterm><primary>C shell</primary></indexterm></" 
     2185"application>: a sintaxe deste shell lembra aquela da linguagem de " 
     2186"programação C. Às vezes requisitada por programadores." 
    17132187 
    17142188#: ../chap3.xml:378(para) 
    … …  
    17182192"<application>C Shell</application>, enhancing user-friendliness and speed." 
    17192193msgstr "" 
     2194"<command>tcsh<indexterm><primary>tcsh</primary></indexterm></command> ou " 
     2195"<application>Turbo C Shell</application>: um aprimoramento do " 
     2196"<application>C Shell</application>, focado na agilidade e em uma interface " 
     2197"amigável com o usuário."  
    17202198 
    17212199#: ../chap3.xml:379(para) 
    … …  
    17272205"configuration a nightmare for beginning users." 
    17282206msgstr "" 
     2207"<command>ksh<indexterm><primary>ksh</primary></indexterm></command> ou o " 
     2208"shell <application>Korn<indexterm><primary>Korn shell</primary></indexterm></" 
     2209"application>:  
    17292210 
    17302211#: ../chap3.xml:382(para) 
    … …  
    17362217#: ../chap3.xml:384(prompt) ../chap3.xml:399(prompt) 
    17372218msgid "mia:~&gt;" 
    1738 msgstr "" 
     2219msgstr "mia:~&gt;" 
    17392220 
    17402221#: ../chap3.xml:384(command) 

  • trunk/l10n/guide/docbook/Intro-Linux/chap4.po

    r7 r33  
    33"Project-Id-Version: PACKAGE VERSION\n" 
    44"POT-Creation-Date: 2008-07-24 01:30-0300\n" 
    5 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" 
    6 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" 
     5"PO-Revision-Date: 2009-07-28 10:08-0300\n" 
     6"Last-Translator: Glauber Machado Rodrigues <glauber.rodrigues@gmail.com>\n" 
    77"Language-Team: LANGUAGE <LL@li.org>\n" 
    88"MIME-Version: 1.0\n" 
    … …  
    1313#. It doesn't matter what you translate it to: it's not used at all. 
    1414#: ../chap4.xml:241(None) 
    15 msgid "" 
    16 "@@image: 'images/fork-and-exec.eps'; md5=1ec6ecc8950dbc6b06a18c18ea652a8d" 
     15msgid "@@image: 'images/fork-and-exec.eps'; md5=1ec6ecc8950dbc6b06a18c18ea652a8d" 
    1716msgstr "" 
    1817 
    … …  
    2019#. It doesn't matter what you translate it to: it's not used at all. 
    2120#: ../chap4.xml:244(None) 
    22 msgid "" 
    23 "@@image: 'images/fork-and-exec.png'; md5=0143a730ef3c0cbd9a8a808cf1055f24" 
     21msgid "@@image: 'images/fork-and-exec.png'; md5=0143a730ef3c0cbd9a8a808cf1055f24" 
    2422msgstr "" 
    2523 
    … …  
    3937#. It doesn't matter what you translate it to: it's not used at all. 
    4038#: ../chap4.xml:595(None) 
    41 msgid "" 
    42 "@@image: 'images/system-monitor.eps'; md5=c452b82d57e598c45acdb23af20ce805" 
     39msgid "@@image: 'images/system-monitor.eps'; md5=c452b82d57e598c45acdb23af20ce805" 
    4340msgstr "" 
    4441 
    … …  
    4643#. It doesn't matter what you translate it to: it's not used at all. 
    4744#: ../chap4.xml:597(None) 
    48 msgid "" 
    49 "@@image: 'images/system-monitor.png'; md5=1377111df45b682b180d41bf8abed683" 
     45msgid "@@image: 'images/system-monitor.png'; md5=1377111df45b682b180d41bf8abed683" 
    5046msgstr "" 
    5147 
    5248#: ../chap4.xml:3(title) 
    5349msgid "Processes" 
    54 msgstr "" 
     50msgstr "Processos" 
    5551 
    5652#: ../chap4.xml:6(para) 
    57 msgid "" 
    58 "Next to files, processes are the most important things on a UNIX/Linux " 
    59 "system. In this chapter, we will take a closer look at those processes. We " 
    60 "will learn more about:" 
    61 msgstr "" 
     53msgid "Next to files, processes are the most important things on a UNIX/Linux system. In this chapter, we will take a closer look at those processes. We will learn more about:" 
     54msgstr "Depois de arquivos, processos são as coisas mais importantes em um sistema UNIX/Linux. Nesse capítulo iremos dar uma olhada em processos mais de perto. Iremos aprender mais sobre:" 
    6255 
    6356#: ../chap4.xml:9(para) 
    6457msgid "Multi-user processing and multi-tasking" 
    65 msgstr "" 
    66  
    67 #: ../chap4.xml:10(para) ../chap4.xml:30(title) 
     58msgstr "Processamento multiusuário e multitarefa" 
     59 
     60#: ../chap4.xml:10(para) 
     61#: ../chap4.xml:30(title) 
    6862msgid "Process types" 
    69 msgstr "" 
     63msgstr "Tipos de processos" 
    7064 
    7165#: ../chap4.xml:11(para) 
    7266msgid "Controlling processes with different signals" 
    73 msgstr "" 
    74  
    75 #: ../chap4.xml:12(para) ../chap4.xml:82(title) 
     67msgstr "Controlando processos com sinais diferentes" 
     68 
     69#: ../chap4.xml:12(para) 
     70#: ../chap4.xml:82(title) 
    7671msgid "Process attributes" 
    77 msgstr "" 
     72msgstr "Atributos de processos" 
    7873 
    7974#: ../chap4.xml:13(para) 
    8075msgid "The life cycle of a process" 
    81 msgstr "" 
     76msgstr "O ciclo de vida de um processo" 
    8277 
    8378#: ../chap4.xml:14(para) 
    8479msgid "System startup and shutdown" 
    85 msgstr "" 
    86  
    87 #: ../chap4.xml:15(para) ../chap4.xml:291(title) 
     80msgstr "Inicialização e desligamento do sistema" 
     81 
     82#: ../chap4.xml:15(para) 
     83#: ../chap4.xml:291(title) 
    8884msgid "SUID and SGID" 
    89 msgstr "" 
     85msgstr "SUID e SGID" 
    9086 
    9187#: ../chap4.xml:16(para) 
    9288msgid "System speed and response" 
    93 msgstr "" 
    94  
    95 #: ../chap4.xml:17(para) ../chap4.xml:645(title) 
     89msgstr "Velocidade e responsividade do sistema" 
     90 
     91#: ../chap4.xml:17(para) 
     92#: ../chap4.xml:645(title) 
    9693msgid "Scheduling processes" 
    97 msgstr "" 
     94msgstr "Agendamento de processos" 
    9895 
    9996#: ../chap4.xml:18(para) 
    10097msgid "The Vixie cron system" 
    101 msgstr "" 
     98msgstr "O sistema Vixie cron" 
    10299 
    103100#: ../chap4.xml:19(para) 
    104101msgid "How to get the most out of your system" 
    105 msgstr "" 
     102msgstr "Como extrair o máximo do seu sistema" 
    106103 
    107104#: ../chap4.xml:24(title) 
    108105msgid "Processes inside out" 
    109 msgstr "" 
     106msgstr "Processos virados do avesso" 
    110107 
    111108#: ../chap4.xml:25(title) 
    112109msgid "Multi-user and multi-tasking" 
    113 msgstr "" 
     110msgstr "Multiusuário e multitarefa" 
    114111 
    115112#: ../chap4.xml:26(para) 
    116 msgid "" 
    117 "Now that we are more used to our environment and we are able to communicate " 
    118 "a little bit with our system, it is time to study the processes we can start " 
    119 "in more detail. Not every command starts a single process. Some commands " 
    120 "initiate a series of processes, such as <command>mozilla</command>; others, " 
    121 "like <command>ls</command>, are executed as a single command." 
    122 msgstr "" 
     113msgid "Now that we are more used to our environment and we are able to communicate a little bit with our system, it is time to study the processes we can start in more detail. Not every command starts a single process. Some commands initiate a series of processes, such as <command>mozilla</command>; others, like <command>ls</command>, are executed as a single command." 
     114msgstr "Agora que estamos mais familiarizados com nosso ambiente e somos capazes de nos comunicar um pouco com nosso sistema, é hora de estudar com mais detalhes os processos que podemos iniciar. Nem todo comando inicia apenas um processo. Alguns comandos iniciam uma série de processos, como o <command>mozilla</command>; outros, como <command>ls</command>, são executados como um único comando." 
    123115 
    124116#: ../chap4.xml:27(para) 
    125 msgid "" 
    126 "Furthermore, Linux is based on UNIX, where it has been common policy to have " 
    127 "multiple users running multiple commands, at the same time and on the same " 
    128 "system. It is obvious that measures have to be taken to have the CPU manage " 
    129 "all these processes, and that functionality has to be provided so users can " 
    130 "switch between processes. In some cases, processes will have to continue to " 
    131 "run even when the user who started them logs out. And users need a means to " 
    132 "reactivate interrupted processes." 
    133 msgstr "" 
     117msgid "Furthermore, Linux is based on UNIX, where it has been common policy to have multiple users running multiple commands, at the same time and on the same system. It is obvious that measures have to be taken to have the CPU manage all these processes, and that functionality has to be provided so users can switch between processes. In some cases, processes will have to continue to run even when the user who started them logs out. And users need a means to reactivate interrupted processes." 
     118msgstr "Além do mais, Linux é baseado em UNIX, onde tem sido comum ter múltiplos usuários executando múltiplos comandos ao mesmo tempo e no mesmo sistema. É claro que algumas medidas devem ser tomadas para que a CPU gerencie todos esses processos, e que alguma funcionalidade deve ser fornecida para que os usuários possam alternar entre os processos. Em alguns casos, um processo deve continuar mesmo que o usuário que o iniciou desconecte do sistema. E os usuários devem ter meios de reativar processos interrompidos." 
    134119 
    135120#: ../chap4.xml:28(para) 
    136121msgid "We will explain the structure of Linux processes in the next sections." 
    137 msgstr "" 
     122msgstr "Iremos explicar a estrutura dos processos em Linux nas próximas seções." 
    138123 
    139124#: ../chap4.xml:31(title) 
    140125msgid "Interactive processes" 
    141 msgstr "" 
     126msgstr "Processos interativos" 
    142127 
    143128#: ../chap4.xml:32(para) 
    144 msgid "" 
    145 "Interactive processes<indexterm><primary>processes</" 
    146 "primary><secondary>interactive</secondary></indexterm> are initialized and " 
    147 "controlled through a terminal session. In other words, there has to be " 
    148 "someone connected to the system to start these processes; they are not " 
    149 "started automatically as part of the system functions. These processes can " 
    150 "run in the foreground<indexterm><primary>processes</" 
    151 "primary><secondary>foreground</secondary></indexterm>, occupying the " 
    152 "terminal that started the program, and you can't start other applications as " 
    153 "long as this process is running in the foreground. Alternatively, they can " 
    154 "run in the background, so that the terminal in which you started the program " 
    155 "can accept new commands while the program is running. Until now, we mainly " 
    156 "focussed on programs running in the foreground - the length of time taken to " 
    157 "run them was too short to notice - but viewing a file with the " 
    158 "<command>less</command> command is a good example of a command occupying the " 
    159 "terminal session. In this case, the activated program is waiting for you to " 
    160 "do something. The program is still connected to the terminal from where it " 
    161 "was started, and the terminal is only useful for entering commands this " 
    162 "program can understand. Other commands will just result in errors or " 
    163 "unresponsiveness of the system." 
    164 msgstr "" 
     129msgid "Interactive processes<indexterm><primary>processes</primary><secondary>interactive</secondary></indexterm> are initialized and controlled through a terminal session. In other words, there has to be someone connected to the system to start these processes; they are not started automatically as part of the system functions. These processes can run in the foreground<indexterm><primary>processes</primary><secondary>foreground</secondary></indexterm>, occupying the terminal that started the program, and you can't start other applications as long as this process is running in the foreground. Alternatively, they can run in the background, so that the terminal in which you started the program can accept new commands while the program is running. Until now, we mainly focussed on programs running in the foreground - the length of time taken to run them was too short to notice - but viewing a file with the <command>less</command> command is a good example of a command occupying the terminal session. In this case, the activated program is waiting for you to do something. The program is still connected to the terminal from where it was started, and the terminal is only useful for entering commands this program can understand. Other commands will just result in errors or unresponsiveness of the system." 
     130msgstr "Processos interativos<indexterm><primary>processos</primary><secondary>interativos</secondary></indexterm> são iniciados e controlados através de uma sessão de terminal. Em outras palavras, deve haver alguém conectado ao sistema para que inicie estes processos; eles não iniciam automaticamente como parte das funções do sistema. Esses processos podem executar em primeiro plano<indexterm><primary>processos</primary><secondary>primeiro plano</secondary></indexterm>, ocupando o terminal que iniciou o programa, e você não pode iniciar outros aplicativos enquanto esse processo estiver executando em primeiro plano. Como alternativa, eles podem executar em plano de fundo, de forma que o terminal que você iniciou o programa possa aceitar novos comandos enquanto o programa executa. Até agora, nós tratamos principalmente de programas executando em primeiro plano – o tempo para executá-los era muito curto para perceber – mas visualizar um arquivo com o comando <command>less</command> é um bom exemplo de um comando ocupando uma sessão de terminal. Nesse caso, o pragrama ativado está esperando você fazer alguma coisa. O programa ainda está conectado ao terminal de onde ele iniciou, e o terminal só serve para inserir comandos entendidos por esse programa. Outros comandos apenas irão resultar em erros ou em falta de resposta do sistema." 
    165131 
    166132#: ../chap4.xml:33(para) 
    167 msgid "" 
    168 "While a process runs in the background<indexterm><primary>processes</" 
    169 "primary><secondary>background</secondary></indexterm>, however, the user is " 
    170 "not prevented from doing other things in the terminal in which he started " 
    171 "the program, while it is running." 
    172 msgstr "" 
     133msgid "While a process runs in the background<indexterm><primary>processes</primary><secondary>background</secondary></indexterm>, however, the user is not prevented from doing other things in the terminal in which he started the program, while it is running." 
     134msgstr "Enquando o processo executa em plano de fundo<indexterm><primary>processos</primary><secondary>plano de fundo</secondary></indexterm>, diferentemente, o usuário não é impedido de fazer outras coisas no terminal o qual iniciou o programa, durante sua execução." 
    173135 
    174136#: ../chap4.xml:34(para) 
    175 msgid "" 
    176 "The shell offers a feature called <emphasis>job " 
    177 "control<indexterm><primary>job control</primary></indexterm></emphasis> " 
    178 "which allows easy handling of multiple processes. This " 
    179 "mechanism<indexterm><primary>processes</primary><secondary>job control</" 
    180 "secondary></indexterm> switches processes between the foreground and the " 
    181 "background. Using this system, programs can also be started in the " 
    182 "background immediately." 
    183 msgstr "" 
     137msgid "The shell offers a feature called <emphasis>job control<indexterm><primary>job control</primary></indexterm></emphasis> which allows easy handling of multiple processes. This mechanism<indexterm><primary>processes</primary><secondary>job control</secondary></indexterm> switches processes between the foreground and the background. Using this system, programs can also be started in the background immediately." 
     138msgstr "O shell oferece um recurso chamado <emphasis>controle de trabalho<indexterm><primary>controle de trabalho</primary></indexterm></emphasis> que permite fácil manipulação de múltiplos processos. Esse mecanismo <indexterm><primary>processes</primary><secondary>job control</secondary></indexterm> alterna processos entre o primeiro plano e o de fundo. Por esse sistema os programas também podem iniciar em plano de fundo imediatamente." 
    184139 
    185140#: ../chap4.xml:35(para) 
    186 msgid "" 
    187 "Running a process in the background is only useful for programs that don't " 
    188 "need user input (via the shell). Putting a job in the background is " 
    189 "typically done when execution of a job is expected to take a long time. In " 
    190 "order to free the issuing terminal after entering the command, a trailing " 
    191 "ampersand is added. In the example, using graphical mode, we open an extra " 
    192 "terminal window from the existing one:" 
    193 msgstr "" 
    194  
    195 #: ../chap4.xml:37(prompt) ../chap4.xml:40(prompt) ../chap4.xml:734(prompt) 
    196 #: ../chap4.xml:742(prompt) ../chap4.xml:750(prompt) 
     141msgid "Running a process in the background is only useful for programs that don't need user input (via the shell). Putting a job in the background is typically done when execution of a job is expected to take a long time. In order to free the issuing terminal after entering the command, a trailing ampersand is added. In the example, using graphical mode, we open an extra terminal window from the existing one:" 
     142msgstr "Executar em plano de fundo é util apenas para programas que não precisam de interação com o usuário (via shell). Um trabalho é colocado em plano de fundo geralmente quando é esperado que demore bastante para terminar de executar. Para liberar o terminal em questão depois de inserir um comando, um caractere & (letra 'E' comercial) é adicionado no final. No exemplo, no modo gráfico, abrimos uma janela terminal extra a partir de uma existente:" 
     143 
     144#: ../chap4.xml:37(prompt) 
     145#: ../chap4.xml:40(prompt) 
     146#: ../chap4.xml:734(prompt) 
     147#: ../chap4.xml:742(prompt) 
     148#: ../chap4.xml:750(prompt) 
    197149msgid "billy:~&gt;" 
    198 msgstr "" 
     150msgstr "billy:~&gt;" 
    199151 
    200152#: ../chap4.xml:37(command) 
    201153msgid "xterm &amp;" 
    202 msgstr "" 
    203  
    204 #: ../chap4.xml:40(primary) ../chap4.xml:56(command) ../chap4.xml:791(command) 
     154msgstr "xterm &amp;" 
     155 
     156#: ../chap4.xml:40(primary) 
     157#: ../chap4.xml:56(command) 
     158#: ../chap4.xml:791(command) 
    205159msgid "jobs" 
    206 msgstr "" 
     160msgstr "jobs" 
    207161 
    208162#: ../chap4.xml:40(command) 
    209163msgid "jobs<indexterm><placeholder-1/></indexterm>" 
    210 msgstr "" 
     164msgstr "jobs<indexterm><placeholder-1/></indexterm>" 
    211165 
    212166#: ../chap4.xml:36(screen) 
    … …  
    220174"[1]+  Running                 xterm &amp;\n" 
    221175msgstr "" 
     176"\n" 
     177"<placeholder-1/> <placeholder-2/>\n" 
     178"[1] 26558\n" 
     179"\n" 
     180"<placeholder-3/> <placeholder-4/>\n" 
     181"[1]+  Running                 xterm &amp;\n" 
    222182 
    223183#: ../chap4.xml:43(para) 
    224 msgid "" 
    225 "The full job control features are explained in detail in the <command>bash</" 
    226 "command><application>Info</application> pages, so only the frequently used " 
    227 "job control<indexterm><primary>Bash</primary><secondary>job control</" 
    228 "secondary></indexterm> applications are listed " 
    229 "here<indexterm><primary>processes</primary><secondary>job control overview</" 
    230 "secondary></indexterm>:" 
    231 msgstr "" 
     184msgid "The full job control features are explained in detail in the <command>bash</command><application>Info</application> pages, so only the frequently used job control<indexterm><primary>Bash</primary><secondary>job control</secondary></indexterm> applications are listed here<indexterm><primary>processes</primary><secondary>job control overview</secondary></indexterm>:" 
     185msgstr "Todos os recursos de controle de trabalhos são explicados em detalhe nas páginas <application>Info</application> do <command>bash<command>, então apenas os usos mais frequentes do controle de trabalhos <indexterm><primary>Bash</primary><secondary>job control</secondary></indexterm> são listados aqui <indexterm><primary>processes</primary><secondary>job control overview</secondary></indexterm>:" 
    232186 
    233187#: ../chap4.xml:45(title) 
    234188msgid "Controlling processes" 
    235 msgstr "" 
     189msgstr "Controlando processos" 
    236190 
    237191#: ../chap4.xml:49(entry) 
    238192msgid "(part of) command" 
    239 msgstr "" 
    240  
    241 #: ../chap4.xml:50(entry) ../chap4.xml:266(entry) ../chap4.xml:765(entry) 
     193msgstr "(parte do) comando" 
     194 
     195#: ../chap4.xml:50(entry) 
     196#: ../chap4.xml:266(entry) 
     197#: ../chap4.xml:765(entry) 
    242198msgid "Meaning" 
    243 msgstr "" 
     199msgstr "Significado" 
    244200 
    245201#: ../chap4.xml:54(command) 
    246202msgid "regular_command" 
    247 msgstr "" 
     203msgstr "comando_qualquer" 
    248204 
    249205#: ../chap4.xml:54(entry) 
    250206msgid "Runs this command in the foreground." 
    251 msgstr "" 
     207msgstr "Executa o comando em primeiro plano." 
    252208 
    253209#: ../chap4.xml:55(command) 
    254210msgid "command &amp;" 
    255 msgstr "" 
     211msgstr "comando_qualquer &amp;" 
    256212 
    257213#: ../chap4.xml:55(entry) 
    258214msgid "Run this command in the background (release the terminal)" 
    259 msgstr "" 
     215msgstr "Executa este comando em plano de fundo (libera o terminal)" 
    260216 
    261217#: ../chap4.xml:56(entry) 
    262218msgid "Show commands running in the background." 
    263 msgstr "" 
    264  
    265 #: ../chap4.xml:57(keycap) ../chap4.xml:58(keycap) 
     219msgstr "(trabalhos) Mostra os comandos que estão executando em plano de fundo." 
     220 
     221#: ../chap4.xml:57(keycap) 
     222#: ../chap4.xml:58(keycap) 
    266223msgid "Ctrl" 
    267 msgstr "" 
     224msgstr "Ctrl" 
    268225 
    269226#: ../chap4.xml:57(keycap) 
    270227msgid "Z" 
    271 msgstr "" 
    272  
    273 #: ../chap4.xml:57(entry) ../chap4.xml:58(entry) 
     228msgstr "Z" 
     229 
     230#: ../chap4.xml:57(entry) 
     231#: ../chap4.xml:58(entry) 
    274232msgid "<placeholder-1/>+<placeholder-2/>" 
    275 msgstr "" 
     233msgstr "<placeholder-1/>+<placeholder-2/>" 
    276234 
    277235#: ../chap4.xml:57(entry) 
    278 msgid "" 
    279 "Suspend (stop, but not quit) a process running in the foreground (suspend)." 
    280 msgstr "" 
     236msgid "Suspend (stop, but not quit) a process running in the foreground (suspend)." 
     237msgstr "Suspende (pausa, mas não fecha) um processo executando em primeiro plano." 
    281238 
    282239#: ../chap4.xml:58(keycap) 
    283240msgid "C" 
    284 msgstr "" 
     241msgstr "C" 
    285242 
    286243#: ../chap4.xml:58(entry) 
    287244msgid "Interrupt (terminate and quit) a process running in the foreground." 
    288 msgstr "" 
     245msgstr "Interrompe(elimina e fecha) um processo executando em primeiro plano." 
    289246 
    290247#: ../chap4.xml:59(parameter) 
    291248msgid "%n" 
    292 msgstr "" 
     249msgstr "%n" 
    293250 
    294251#: ../chap4.xml:59(parameter) 
    295252msgid "%2" 
    296 msgstr "" 
     253msgstr "%2" 
    297254 
    298255#: ../chap4.xml:59(command) 
    299256msgid "fg <placeholder-1/>" 
    300 msgstr "" 
     257msgstr "fg <placeholder-1/>" 
    301258 
    302259#: ../chap4.xml:59(entry) 
    303 msgid "" 
    304 "Every process running in the background gets a number assigned to it. By " 
    305 "using the % expression a job can be referred to using its number, for " 
    306 "instance <placeholder-1/>." 
    307 msgstr "" 
     260msgid "Every process running in the background gets a number assigned to it. By using the % expression a job can be referred to using its number, for instance <placeholder-1/>." 
     261msgstr "Cada processo executando no plano de fundo recebe um número atribuido a ele. Usando a expressão %, um trabalho pode ser referido pelo seu número, por exemplo <placeholder-1/>." 
    308262 
    309263#: ../chap4.xml:60(primary) 
    310264msgid "bg" 
    311 msgstr "" 
     265msgstr "bg" 
    312266 
    313267#: ../chap4.xml:60(command) 
    314268msgid "bg<indexterm><placeholder-1/></indexterm>" 
    315 msgstr "" 
     269msgstr "bg<indexterm><placeholder-1/></indexterm>" 
    316270 
    317271#: ../chap4.xml:60(entry) 
    318272msgid "Reactivate a suspended program in the background." 
    319 msgstr "" 
     273msgstr "Reativa um programa suspenso no plano de fundo (\"bg\" vem de \"background\", traduzido do inglês para \"plano de fundo\")." 
    320274 
    321275#: ../chap4.xml:61(primary) 
    322276msgid "fg" 
    323 msgstr "" 
     277msgstr "fg" 
    324278 
    325279#: ../chap4.xml:61(command) 
    326280msgid "fg<indexterm><placeholder-1/></indexterm>" 
    327 msgstr "" 
     281msgstr "fg<indexterm><placeholder-1/></indexterm>" 
    328282 
    329283#: ../chap4.xml:61(entry) 
    330284msgid "Puts the job back in the foreground." 
    331 msgstr "" 
    332  
    333 #: ../chap4.xml:62(primary) ../chap4.xml:794(command) 
     285msgstr "Coloca o trabalho de volta em primeiro plano (\"fg\" vem de \"foreground\", traduzido do inglês para \"primeiro plano\")." 
     286 
     287#: ../chap4.xml:62(primary) 
     288#: ../chap4.xml:794(command) 
    334289msgid "kill" 
    335 msgstr "" 
     290msgstr "kill" 
    336291 
    337292#: ../chap4.xml:62(command) 
    338293msgid "kill<indexterm><placeholder-1/></indexterm>" 
    339 msgstr "" 
     294msgstr "kill<indexterm><placeholder-1/></indexterm>" 
    340295 
    341296#: ../chap4.xml:62(command) 
    342297msgid "bash" 
    343 msgstr "" 
     298msgstr "bash" 
    344299 
    345300#: ../chap4.xml:62(entry) 
    346 msgid "" 
    347 "End a process (also see Shell Builtin Commands in the Info pages of " 
    348 "<placeholder-1/>)" 
    349 msgstr "" 
     301msgid "End a process (also see Shell Builtin Commands in the Info pages of <placeholder-1/>)" 
     302msgstr "(matar) Finaliza um processo (veja também os comandos internos das páginas Info do <command>bash</command>)" 
    350303 
    351304#: ../chap4.xml:66(para) 
    352305msgid "More practical examples can be found in the exercises." 
    353 msgstr "" 
     306msgstr "Exemplos mais práticos podem ser encontrados nos exercícios." 
    354307 
    355308#: ../chap4.xml:67(para) 
    356 msgid "" 
    357 "Most UNIX systems are likely to be able to run " 
    358 "<command>screen<indexterm><primary>screen</primary></indexterm></command>, " 
    359 "which is useful when you actually want another shell to execute commands. " 
    360 "Upon calling <command>screen</command>, a new session is created with an " 
    361 "accompanying shell and/or commands as specified, which you can then put out " 
    362 "of the way. In this new session you may do whatever it is you want to do. " 
    363 "All programs and operations will run independent of the issuing shell. You " 
    364 "can then detach this session, while the programs you started in it continue " 
    365 "to run, even when you log out of the originating shell, and pick your " 
    366 "<emphasis>screen</emphasis> up again any time you like." 
    367 msgstr "" 
     309msgid "Most UNIX systems are likely to be able to run <command>screen<indexterm><primary>screen</primary></indexterm></command>, which is useful when you actually want another shell to execute commands. Upon calling <command>screen</command>, a new session is created with an accompanying shell and/or commands as specified, which you can then put out of the way. In this new session you may do whatever it is you want to do. All programs and operations will run independent of the issuing shell. You can then detach this session, while the programs you started in it continue to run, even when you log out of the originating shell, and pick your <emphasis>screen</emphasis> up again any time you like." 
     310msgstr "Provavelmente a maioria dos sistemas UNIX são capazes de executar o comando <command>screen<indexterm><primary>screen</primary></indexterm></command>, o qual é útil quando você realmente quer outro shell para executar comandos. Ao chamar <command>screen</command>, uma nova sessão é criada acompanhada de um shell, e/ou comandos especificados, e você pode então movê-la da sua frente. Nessa nova sessão você pode fazer o que quiser. Todos os programas e operacoes vão executar idependentemente do shell em questão. Você pode então desconectar esta sessão, enquanto os programas que você iniciou continuarão executando, e voltar para seu <emphasis>screen</emphasis> quando quiser." 
    368311 
    369312#: ../chap4.xml:68(para) 
    370 msgid "" 
    371 "This program originates from a time when virtual consoles were not invented " 
    372 "yet, and everything needed to be done using one text terminal. To addicts, " 
    373 "it still has meaning in Linux, even though we've had virtual consoles for " 
    374 "almost ten years." 
    375 msgstr "" 
     313msgid "This program originates from a time when virtual consoles were not invented yet, and everything needed to be done using one text terminal. To addicts, it still has meaning in Linux, even though we've had virtual consoles for almost ten years." 
     314msgstr "Este programa vem de um tempo quando os consoles vituais ainda não haviam sido inventados, e tudo tinha que ser feito com apenas um terminal de texto. Para os devotos, ainda significa muito em Linux, apesar de já termos consoles virtuais por quase dez anos." 
    376315 
    377316#: ../chap4.xml:70(title) 
    378317msgid "Automatic processes" 
    379 msgstr "" 
     318msgstr "Processos automáticos" 
    380319 
    381320#: ../chap4.xml:71(para) 
    382 msgid "" 
    383 "Automatic<indexterm><primary>processes</primary><secondary>automatic</" 
    384 "secondary></indexterm> or batch processes are not connected to a terminal. " 
    385 "Rather, these are tasks that can be queued into a spooler area, where they " 
    386 "wait to be executed on a FIFO (first-in, first-out) basis. Such tasks can be " 
    387 "executed using one of two criteria:" 
    388 msgstr "" 
     321msgid "Automatic<indexterm><primary>processes</primary><secondary>automatic</secondary></indexterm> or batch processes are not connected to a terminal. Rather, these are tasks that can be queued into a spooler area, where they wait to be executed on a FIFO (first-in, first-out) basis. Such tasks can be executed using one of two criteria:" 
     322msgstr "Processos automáticos<indexterm><primary>processes</primary><secondary>automatic</secondary></indexterm>, ou em lotes, não estão conectados a terminais. Ao invés, são tarefas que podem ser enfileiradas numa área de spooler, onde podem esperar para serem executadas numa política FIFO (\"first-in, first-out\", traduzido do inglês para \"o primeiro a entrar é o primeiro a sair\"). Tais tarefas podem ser executadas por um desses dois critérios:" 
    389323 
    390324#: ../chap4.xml:73(para) 
    391 msgid "" 
    392 "At a certain date and time: done using the <command>at</command> command, " 
    393 "which we will discuss in the second part of this chapter." 
    394 msgstr "" 
     325msgid "At a certain date and time: done using the <command>at</command> command, which we will discuss in the second part of this chapter." 
     326msgstr "Em uma data e hora determinada: pelo comando <command>at</command>, o qual iremos discutir na segunda parte desse capítulo." 
    395327 
    396328#: ../chap4.xml:74(para) 
    397 msgid "" 
    398 "At times when the total system load is low enough to accept extra jobs: done " 
    399 "using the <command>batch<indexterm><primary>batch</primary></indexterm></" 
    400 "command> command. By default, tasks are put in a queue where they wait to be " 
    401 "executed until the system load is lower than 0.8. In large environments, the " 
    402 "system administrator may prefer batch processing when large amounts of data " 
    403 "have to be processed or when tasks demanding a lot of system resources have " 
    404 "to be executed on an already loaded system. Batch processing is also used " 
    405 "for optimizing system performance." 
    406 msgstr "" 
     329msgid "At times when the total system load is low enough to accept extra jobs: done using the <command>batch<indexterm><primary>batch</primary></indexterm></command> command. By default, tasks are put in a queue where they wait to be executed until the system load is lower than 0.8. In large environments, the system administrator may prefer batch processing when large amounts of data have to be processed or when tasks demanding a lot of system resources have to be executed on an already loaded system. Batch processing is also used for optimizing system performance." 
     330msgstr "Quando a carga total do sistema é baixa o bastante para aceitar trabalhos extras: pelo comando <command>batch<indexterm><primary>batch</primary></indexterm></command>.  Por padrão, as tarefas são colocadas em filas onde esperam para serem executadas quando a carga do sistema for inferior a 0.8. Em ambientes grandes, o administrador do sistema pode preferir processamento em lotes quando o processamento envolver grandes quantidades de dados ou quando requerer muitos recursos de um sistema já aterefado.Processamento em lotes também é usado para otimizar a performance do sistema." 
    407331 
    408332#: ../chap4.xml:77(title) 
    409333msgid "Daemons" 
    410 msgstr "" 
     334msgstr "Daemons" 
    411335 
    412336#: ../chap4.xml:78(para) 
    413 msgid "" 
    414 "Daemons<indexterm><primary>daemons</primary><secondary>definition</" 
    415 "secondary></indexterm> are server processes<indexterm><primary>processes</" 
    416 "primary><secondary>daemons</secondary></indexterm> that run continuously. " 
    417 "Most of the time, they are initialized at system startup and then wait in " 
    418 "the background until their service is required. A typical example is the " 
    419 "networking daemon, <emphasis>xinetd</emphasis>, which is started in almost " 
    420 "every boot procedure. After the system is booted, the network daemon just " 
    421 "sits and waits until a client program, such as an FTP client, needs to " 
    422 "connect." 
    423 msgstr "" 
     337msgid "Daemons<indexterm><primary>daemons</primary><secondary>definition</secondary></indexterm> are server processes<indexterm><primary>processes</primary><secondary>daemons</secondary></indexterm> that run continuously. Most of the time, they are initialized at system startup and then wait in the background until their service is required. A typical example is the networking daemon, <emphasis>xinetd</emphasis>, which is started in almost every boot procedure. After the system is booted, the network daemon just sits and waits until a client program, such as an FTP client, needs to connect." 
     338msgstr "Daemons (???) <indexterm><primary>daemons</primary><secondary>definição</secondary></indexterm> são processos de servidor <indexterm><primary>processos</primary><secondary>daemons</secondary></indexterm>que executam continuamente. É comum que sejam iniciados junto com o computador, e então esperam em plano de fundo até que o serviço seja requisitado. Um exemplo típico é o daemon de rede <emphasis>xinetd</emphasis>, que faz parte da maioria dos processos de inicialização. Depois que o sistema é inicializado, o daemon de rede apenas senta e espera até que um programa cliente, como um cliente de FTP, queira conectar." 
    424339 
    425340#: ../chap4.xml:83(para) 
    426 msgid "" 
    427 "A process has a series of characteristics<indexterm><primary>processes</" 
    428 "primary><secondary>properties</secondary></indexterm>, which can be viewed " 
    429 "with the <command>ps<indexterm><primary>processes</" 
    430 "primary><secondary>displaying</secondary></indexterm></command> command:" 
    431 msgstr "" 
     341msgid "A process has a series of characteristics<indexterm><primary>processes</primary><secondary>properties</secondary></indexterm>, which can be viewed with the <command>ps<indexterm><primary>processes</primary><secondary>displaying</secondary></indexterm></command> command:" 
     342msgstr "Um processo tem uma série de características <indexterm><primary>processos</primary><secondary>propriedade</secondary></indexterm>, que podem ser visualizadas com o comando <command>ps<indexterm><primary>processos</primary><secondary>exibindo</secondary></indexterm></command>:" 
    432343 
    433344#: ../chap4.xml:85(para) 
    434 msgid "" 
    435 "The process ID or PID<indexterm><primary>PID</primary></indexterm>: a unique " 
    436 "identification number used to refer to the process." 
    437 msgstr "" 
     345msgid "The process ID or PID<indexterm><primary>PID</primary></indexterm>: a unique identification number used to refer to the process." 
     346msgstr "O ID de processo, ou PID,<indexterm><primary>PID</primary></indexterm>: um número de identidade usado para identificar o processo como único." 
    438347 
    439348#: ../chap4.xml:86(para) 
    440 msgid "" 
    441 "The parent process ID or PPID<indexterm><primary>PPID</primary></indexterm>: " 
    442 "the number of the process (PID) that started this process." 
    443 msgstr "" 
     349msgid "The parent process ID or PPID<indexterm><primary>PPID</primary></indexterm>: the number of the process (PID) that started this process." 
     350msgstr "O ID do processo pai,  ou PPID<indexterm><primary>PPID</primary></indexterm>: o número do processo (PID) que originou este processo." 
    444351 
    445352#: ../chap4.xml:87(para) 
    446 msgid "" 
    447 "Nice number: the degree of friendliness<indexterm><primary>processes</" 
    448 "primary><secondary>nice number</secondary></indexterm> of this process " 
    449 "toward other processes (not to be confused with process priority, which is " 
    450 "calculated based on this nice number and recent CPU usage of the process)." 
    451 msgstr "" 
     353#, fuzzy 
     354msgid "Nice number: the degree of friendliness<indexterm><primary>processes</primary><secondary>nice number</secondary></indexterm> of this process toward other processes (not to be confused with process priority, which is calculated based on this nice number and recent CPU usage of the process)." 
     355msgstr "Número nice (generoso): o grau de generosidade <indexterm><primary>processos</primary><secondary>numero nice</secondary></indexterm> desse processo diante dos outros processos (não confundir com prioridade do processo, que é cauculado baseado nesse número nice e o quanto o processo usou a CPU recentemente)." 
    452356 
    453357#: ../chap4.xml:88(para) 
    454 msgid "" 
    455 "Terminal or TTY<indexterm><primary>TTY</primary></indexterm>: terminal to " 
    456 "which the process is connected." 
    457 msgstr "" 
     358msgid "Terminal or TTY<indexterm><primary>TTY</primary></indexterm>: terminal to which the process is connected." 
     359msgstr "Terminal, ou TTY<indexterm><primary>TTY</primary></indexterm>: terminal ao qual o processo está conectado." 
    458360 
    459361#: ../chap4.xml:89(para) 
    460 msgid "" 
    461 "User name of the real and effective user (RUID<indexterm><primary>RUID</" 
    462 "primary></indexterm> and EUID<indexterm><primary>EUID</primary></" 
    463 "indexterm>): the owner of the process. The real owner is the user issuing " 
    464 "the command, the effective user is the one determining access to system " 
    465 "resources. RUID and EUID are usually the same, and the process has the same " 
    466 "access rights the issuing user would have. An example to clarify this: the " 
    467 "browser <command>mozilla</command> in <filename>/usr/bin</filename> is owned " 
    468 "by user <emphasis>root</emphasis>:" 
    469 msgstr "" 
    470  
    471 #: ../chap4.xml:91(prompt) ../chap4.xml:94(prompt) ../chap4.xml:97(prompt) 
     362msgid "User name of the real and effective user (RUID<indexterm><primary>RUID</primary></indexterm> and EUID<indexterm><primary>EUID</primary></indexterm>): the owner of the process. The real owner is the user issuing the command, the effective user is the one determining access to system resources. RUID and EUID are usually the same, and the process has the same access rights the issuing user would have. An example to clarify this: the browser <command>mozilla</command> in <filename>/usr/bin</filename> is owned by user <emphasis>root</emphasis>:" 
     363msgstr "Usuário real e usuário efetivo (RUID<indexterm><primary>RUID</primary></indexterm> e EUID<indexterm><primary>EUID</primary></indexterm>): o dono do processo. O real é o usuário que executou o comando, o usuário efetivo determina o acesso aos recursos do sistema. O RUID e o EUID geralmente são iguais, e o processo tem os mesmos direitos de acesso que o usuário que executou o comando. Um exemplo para deixar isso claro: o navegador <command>mozilla</command> em <filename>/usr/bin</filename> pertence ao usuário <emphasis>root</emphasis>:" 
     364 
     365#: ../chap4.xml:91(prompt) 
     366#: ../chap4.xml:94(prompt) 
     367#: ../chap4.xml:97(prompt) 
    472368#: ../chap4.xml:111(prompt) 
    473369msgid "theo:~&gt;" 
    474 msgstr "" 
     370msgstr "theo:~&gt;" 
    475371 
    476372#: ../chap4.xml:91(command) 
    477373msgid "ls -l /usr/bin/mozilla" 
    478 msgstr "" 
     374msgstr "ls -l /usr/bin/mozilla" 
    479375 
    480376#: ../chap4.xml:94(command) 
    481377msgid "mozilla &amp;" 
    482 msgstr "" 
     378msgstr "mozilla &amp;" 
    483379 
    484380#: ../chap4.xml:97(command) 
    485381msgid "ps -af" 
    486 msgstr "" 
     382msgstr "ps -af" 
    487383 
    488384#: ../chap4.xml:90(screen) 
    … …  
    501397"theo  26613 26569 0 15:04 pts/5 00:00:00 ps -af\n" 
    502398msgstr "" 
     399"\n" 
     400"<placeholder-1/> <placeholder-2/>\n" 
     401"-rwxr-xr-x  1 root   root      4996 Nov 20 18:28 /usr/bin/mozilla*\n" 
     402"\n" 
     403"<placeholder-3/> <placeholder-4/>\n" 
     404"[1] 26595\n" 
     405"\n" 
     406"<placeholder-5/> <placeholder-6/>\n" 
     407"UID     PID  PPID C STIME TTY       TIME CMD\n" 
     408"theo  26601 26599 0 15:04 pts/5 00:00:00 /usr/lib/mozilla/mozilla-bin\n" 
     409"theo  26613 26569 0 15:04 pts/5 00:00:00 ps -af\n" 
    503410 
    504411#: ../chap4.xml:102(para) 
    505 msgid "" 
    506 "When user<indexterm><primary>EUID</primary><secondary>example</secondary></" 
    507 "indexterm><emphasis>theo</emphasis> starts this program, the process itself " 
    508 "and all processes started by the initial process, will be owned by user " 
    509 "<emphasis>theo</emphasis> and not by the system administrator. When " 
    510 "<command>mozilla</command> needs access to certain files, that access will " 
    511 "be determined by <emphasis>theo</emphasis>'s permissions and not by " 
    512 "<emphasis>root</emphasis>'s." 
    513 msgstr "" 
     412msgid "When user<indexterm><primary>EUID</primary><secondary>example</secondary></indexterm><emphasis>theo</emphasis> starts this program, the process itself and all processes started by the initial process, will be owned by user <emphasis>theo</emphasis> and not by the system administrator. When <command>mozilla</command> needs access to certain files, that access will be determined by <emphasis>theo</emphasis>'s permissions and not by <emphasis>root</emphasis>'s." 
     413msgstr "Quando o usuário<indexterm><primary>EUID</primary><secondary>exemplo</secondary></indexterm><emphasis>theo</emphasis> inicia este programa, o próprio processo e todos os processos iniciados por este processo pertencerão ao usuário <emphasis>theo</emphasis>, e não pelo administrador do sistema. Quando o <command>mozilla</command> solicita o acesso a certos arquivos, esse acesso vai ser determinado pelas permissões de <emphasis>theo</emphasis> e não de <emphasis>root</emphasis>." 
    514414 
    515415#: ../chap4.xml:104(para) 
    516 msgid "" 
    517 "Real and effective group owner (RGID<indexterm><primary>RGID</primary></" 
    518 "indexterm> and EGID<indexterm><primary>EGID</primary></indexterm>): The real " 
    519 "group owner of a process is the primary group of the user who started the " 
    520 "process. The effective group owner is usually the same, except when SGID " 
    521 "access mode has been applied to a file." 
    522 msgstr "" 
     416msgid "Real and effective group owner (RGID<indexterm><primary>RGID</primary></indexterm> and EGID<indexterm><primary>EGID</primary></indexterm>): The real group owner of a process is the primary group of the user who started the process. The effective group owner is usually the same, except when SGID access mode has been applied to a file." 
     417msgstr "Grupo real e efetivo do dono(RGID<indexterm><primary>RGID</primary></indexterm> e EGID<indexterm><primary>EGID</primary></indexterm>): O grupo real do dono de um processo é o grupo primário do usuário que iniciou o processo. O grupo efetivo geralmente é o mesmo, exceto quando o modo de acesso SGID é aplicado ao arquivo executável do programa." 
    523418 
    524419#: ../chap4.xml:107(title) 
    525420msgid "Displaying process information" 
    526 msgstr "" 
     421msgstr "Exibindo informações de processos" 
    527422 
    528423#: ../chap4.xml:108(para) 
    529 msgid "" 
    530 "The <command>ps</command> command is one of the tools for " 
    531 "visualizing<indexterm><primary>processes</primary><secondary>displaying</" 
    532 "secondary></indexterm> processes. This command has several options which can " 
    533 "be combined to display different process attributes." 
    534 msgstr "" 
     424msgid "The <command>ps</command> command is one of the tools for visualizing<indexterm><primary>processes</primary><secondary>displaying</secondary></indexterm> processes. This command has several options which can be combined to display different process attributes." 
     425msgstr "O comando <command>ps</command> é uma das ferramentas para visualizar <indexterm><primary>processos</primary><secondary>visualisar</secondary></indexterm> processos. Esse comando tem várias opções que podem ser combinadas para exibir diferentes atributos de processos." 
    535426 
    536427#: ../chap4.xml:109(para) 
    537 msgid "" 
    538 "With no options specified, <command>ps</command> only gives information " 
    539 "about the current shell and eventual processes<indexterm><primary>ps</" 
    540 "primary><secondary>simple example</secondary></indexterm>:" 
    541 msgstr "" 
    542  
    543 #: ../chap4.xml:111(command) ../chap4.xml:809(command) 
     428msgid "With no options specified, <command>ps</command> only gives information about the current shell and eventual processes<indexterm><primary>ps</primary><secondary>simple example</secondary></indexterm>:" 
     429msgstr "Se nenhuma opção for especificada, o <command>ps</command> apenas informa sobre o shell atual e eventuais processos<indexterm><primary>ps</primary><secondary>exemplo simples</secondary></indexterm>:" 
     430 
     431#: ../chap4.xml:111(command) 
     432#: ../chap4.xml:809(command) 
    544433msgid "ps" 
    545 msgstr "" 
     434msgstr "ps" 
    546435 
    547436#: ../chap4.xml:110(screen) 
    … …  
    554443" 5314 pts/7    00:00:00 ps\n" 
    555444msgstr "" 
     445"\n" 
     446"<placeholder-1/> <placeholder-2/>\n" 
     447"  PID TTY          TIME CMD\n" 
     448" 4245 pts/7    00:00:00 bash\n" 
     449" 5314 pts/7    00:00:00 ps\n" 
    556450 
    557451#: ../chap4.xml:116(para) 
    558 msgid "" 
    559 "Since this does not give enough information - generally, at least a hundred " 
    560 "processes are running on your system - we will usually select particular " 
    561 "processes out of the list of all processes, using the <command>grep</" 
    562 "command> command in a <emphasis>pipe</emphasis>, see <xref linkend=" 
    563 "\"sect_05_01_02_01\"/>, as in this line, which will select and display all " 
    564 "processes owned by a particular<indexterm><primary>ps</" 
    565 "primary><secondary>example with options</secondary></indexterm> user:" 
    566 msgstr "" 
    567  
    568 #: ../chap4.xml:117(option) ../chap4.xml:618(option) ../chap4.xml:626(option) 
     452msgid "Since this does not give enough information - generally, at least a hundred processes are running on your system - we will usually select particular processes out of the list of all processes, using the <command>grep</command> command in a <emphasis>pipe</emphasis>, see <xref linkend=\"sect_05_01_02_01\"/>, as in this line, which will select and display all processes owned by a particular<indexterm><primary>ps</primary><secondary>example with options</secondary></indexterm> user:" 
     453msgstr "Já que isso não fornece informação o suficiente - geralmente, pelo menos centenas de processos estão executando no seu sistema - normalmente iremos selecionar processos em particular na lista de todos os processos com o comando <command>grep</command> em um <emphasis>pipe</emphasis>, veja <xref linkend=\"sect_05_01_02_01\"/>, como nessa linha, que irá exibir todos os processos pertencentes<indexterm><primary>ps</primary><secondary>example with options</secondary></indexterm> a um usuário particular:" 
     454 
     455#: ../chap4.xml:117(option) 
     456#: ../chap4.xml:618(option) 
     457#: ../chap4.xml:626(option) 
    569458#: ../chap4.xml:631(option) 
    570459msgid "-ef" 
    571 msgstr "" 
     460msgstr "-ef" 
    572461 
    573462#: ../chap4.xml:117(parameter) 
    574463msgid "username" 
    575 msgstr "" 
     464msgstr "username" 
    576465 
    577466#: ../chap4.xml:117(command) 
    578467msgid "ps <placeholder-1/> | grep <placeholder-2/>" 
    579 msgstr "" 
     468msgstr "ps <placeholder-1/> | grep <placeholder-2/>" 
    580469 
    581470#: ../chap4.xml:118(para) 
    582 msgid "" 
    583 "This example shows all processes with a process name of <command>bash</" 
    584 "command>, the most common login shell on Linux systems:" 
    585 msgstr "" 
     471msgid "This example shows all processes with a process name of <command>bash</command>, the most common login shell on Linux systems:" 
     472msgstr "Este exemplo exibe todos os processos com um nome de processo <command>bash</command>, o shell de login mais comum em sistemas Linux:" 
    586473 
    587474#: ../chap4.xml:120(prompt) 
    588475msgid "theo:&gt;" 
    589 msgstr "" 
     476msgstr "theo:&gt;" 
    590477 
    591478#: ../chap4.xml:120(command) 
    592479msgid "ps auxw | grep bash" 
    593 msgstr "" 
     480msgstr "ps auxw | grep bash" 
    594481 
    595482#: ../chap4.xml:119(screen) 
    596 #, no-wrap 
     483#, fuzzy, no-wrap 
    597484msgid "" 
    598485"\n" 
    … …  
    607494"theo      5427  0.0  0.1  3720  548 pts/7  S  19:22   0:00 grep bash\n" 
    608495msgstr "" 
     496"\n" 
     497"<placeholder-1/> <placeholder-2/>\n" 
     498"brenda   31970  0.0  0.3  6080 1556 tty2   S  Feb23   0:00 -bash\n" 
     499"root     32043  0.0  0.3  6112 1600 tty4   S  Feb23   0:00 -bash\n" 
     500"theo     32581  0.0  0.3  6384 1864 pts/1  S  Feb23   0:00 bash\n" 
     501"theo     32616  0.0  0.3  6396 1896 pts/2  S  Feb23   0:00 bash\n" 
     502"theo     32629  0.0  0.3  6380 1856 pts/3  S  Feb23   0:00 bash\n" 
     503"theo      2214  0.0  0.3  6412 1944 pts/5  S  16:18   0:02 bash\n" 
     504"theo      4245  0.0  0.3  6392 1888 pts/7  S  17:26   0:00 bash\n" 
     505"theo      5427  0.0  0.1  3720  548 pts/7  S  19:22   0:00 grep bash\n" 
    609506 
    610507#: ../chap4.xml:130(para) 
    611 msgid "" 
    612 "In these cases, the <command>grep</command> command finding lines containing " 
    613 "the string <emphasis>bash</emphasis> is often displayed as well on systems " 
    614 "that have a lot of idletime. If you don't want this to happen, use the " 
    615 "<command>pgrep<indexterm><primary>pgrep</primary></indexterm></command> " 
    616 "command." 
    617 msgstr "" 
     508msgid "In these cases, the <command>grep</command> command finding lines containing the string <emphasis>bash</emphasis> is often displayed as well on systems that have a lot of idletime. If you don't want this to happen, use the <command>pgrep<indexterm><primary>pgrep</primary></indexterm></command> command." 
     509msgstr "Nesses casos, o comando <command>grep</command> que está procurando as linhas com <emphasis>bash</emphasis> também é exibido em sistemas com muito tempo ocioso. Se você não quer que isso aconteça, use o comando <command>pgrep<indexterm><primary>pgrep</primary></indexterm></command>." 
    618510 
    619511#: ../chap4.xml:131(para) 
    620 msgid "" 
    621 "Bash shells are a special case: this process list also shows which ones are " 
    622 "login shells (where you have to give your username and password, such as " 
    623 "when you log in in textmode or do a remote login, as opposed to non-login " 
    624 "shells, started up for instance by clicking a terminal window icon). Such " 
    625 "login shells are preceded with a dash (-)." 
    626 msgstr "" 
     512msgid "Bash shells are a special case: this process list also shows which ones are login shells (where you have to give your username and password, such as when you log in in textmode or do a remote login, as opposed to non-login shells, started up for instance by clicking a terminal window icon). Such login shells are preceded with a dash (-)." 
     513msgstr "Shells bash são um caso especial: essa lista de processos também mostra quais são shells com identificação de usuário na entrada (onde você tem que fornecer nome de usuário e senha, como quando você inicia em modo texto ou numa conexão remota, o contrário de shells que, por exemplo, são iniciados ao clicar no ícone de uma janela de tarminal). Tais shells com identificação na entrada do usuário são precedidos com um traço (-)." 
    627514 
    628515#: ../chap4.xml:133(title) 
    629516msgid "|?" 
    630 msgstr "" 
     517msgstr "|?" 
    631518 
    632519#: ../chap4.xml:134(para) 
    633 msgid "" 
    634 "We will explain about the | operator in the next chapter, see <xref linkend=" 
    635 "\"chap_05\"/>." 
    636 msgstr "" 
     520msgid "We will explain about the | operator in the next chapter, see <xref linkend=\"chap_05\"/>." 
     521msgstr "Iremos tratar do operador | no próximo capítulo, veja <xref linkend=\"chap_05\"/>." 
    637522 
    638523#: ../chap4.xml:137(para) 
    639 msgid "" 
    640 "More info can be found the usual way: <command>ps <option>--help</option></" 
    641 "command> or <command>man <parameter>ps</parameter></command>. GNU " 
    642 "<command>ps</command> supports different styles of option formats; the above " 
    643 "examples don't contain errors." 
    644 msgstr "" 
     524msgid "More info can be found the usual way: <command>ps <option>--help</option></command> or <command>man <parameter>ps</parameter></command>. GNU <command>ps</command> supports different styles of option formats; the above examples don't contain errors." 
     525msgstr "Mais informações podem ser obtidas da maneira usual: <command>ps <option>--help</option></command> ou <command>man <parameter>ps</parameter></command>. O GNU <command>ps</command> oferece suporte a diferentes tipos de formatos de opções; os exemplos acima não contém erros." 
    645526 
    646527#: ../chap4.xml:138(para) 
    647 msgid "" 
    648 "Note that <command>ps</command> only gives a momentary state of the active " 
    649 "processes, it is a one-time recording. The " 
    650 "<command>top<indexterm><primary>top</primary></indexterm></command> program " 
    651 "displays a more precise view by updating the results given by <command>ps</" 
    652 "command> (with a bunch of options) once every five seconds, generating a new " 
    653 "list of the processes causing the heaviest<indexterm><primary>processes</" 
    654 "primary><secondary>continuous display</secondary></indexterm> load " 
    655 "periodically, meanwhile integrating more information about the swap space in " 
    656 "use and the state of the CPU, from the <filename>proc</filename> file " 
    657 "system<indexterm><primary>top</primary><secondary>example</secondary></" 
    658 "indexterm>:" 
    659 msgstr "" 
     528msgid "Note that <command>ps</command> only gives a momentary state of the active processes, it is a one-time recording. The <command>top<indexterm><primary>top</primary></indexterm></command> program displays a more precise view by updating the results given by <command>ps</command> (with a bunch of options) once every five seconds, generating a new list of the processes causing the heaviest<indexterm><primary>processes</primary><secondary>continuous display</secondary></indexterm> load periodically, meanwhile integrating more information about the swap space in use and the state of the CPU, from the <filename>proc</filename> file system<indexterm><primary>top</primary><secondary>example</secondary></indexterm>:" 
     529msgstr "Note que o comando <command>ps</command> apenas fornece o estado momentaneo dos processos, é uma lembrança única. O programa <command>top<indexterm><primary>top</primary></indexterm></command> exibe uma visão mais precisa ao atualizar os resultados fornecidos pelo comando <command>ps</command> (com um monte de opções) uma vez a cada cinco segundos, gerando  periodicamente uma lista dos processos <indexterm><primary>processos</primary><secondary>exibição contínua</secondary></indexterm> que estão usando mais recursos." 
    660530 
    661531#: ../chap4.xml:139(screen) 
    662 #, no-wrap 
     532#, fuzzy, no-wrap 
    663533msgid "" 
    664534"\n" 
    … …  
    688558"  220 root   9  0     0    0     0 SW   0.0  0.0  0:00 kjournald\n" 
    689559msgstr "" 
     560"\n" 
     561" 12:40pm up 9 days, 6:00, 4 users, load average: 0.21, 0.11, 0.03\n" 
     562"89 processes: 86 sleeping, 3 running, 0 zombie, 0 stopped\n" 
     563"CPU states:  2.5% user,  1.7% system,  0.0% nice, 95.6% idle\n" 
     564"Mem:   255120K av, 239412K used, 15708K free, 756K shrd, 22620K buff\n" 
     565"Swap: 1050176K av, 76428K used, 973748K free, 82756K cached\n" 
     566"\n" 
     567"  PID USER  PRI NI SIZE  RSS SHARE STAT %CPU %MEM TIME COMMAND\n" 
     568" 5005 root  14  0 91572  15M 11580 R    1.9  6.0  7:53 X\n" 
     569"19599 jeff  14  0  1024 1024   796 R    1.1  0.4  0:01 top\n" 
     570"19100 jeff   9  0  5288 4948  3888 R    0.5  1.9  0:24 gnome-terminal\n" 
     571"19328 jeff   9  0 37884  36M 14724 S    0.5 14.8  1:30 mozilla-bin\n" 
     572"    1 root   8  0   516  472   464 S    0.0  0.1  0:06 init\n" 
     573"    2 root   9  0     0    0     0 SW   0.0  0.0  0:02 keventd\n" 
     574"    3 root   9  0     0    0     0 SW   0.0  0.0  0:00 kapm-idled\n" 
     575"    4 root  19 19     0    0     0 SWN  0.0  0.0  0:00 ksoftirqd_CPU0\n" 
     576"    5 root   9  0     0    0     0 SW   0.0  0.0  0:33 kswapd\n" 
     577"    6 root   9  0     0    0     0 SW   0.0  0.0  0:00 kreclaimd\n" 
     578"    7 root   9  0     0    0     0 SW   0.0  0.0  0:00 bdflush\n" 
     579"    8 root   9  0     0    0     0 SW   0.0  0.0  0:05 kupdated\n" 
     580"    9 root  -1-20     0    0     0 SW&lt;  0.0  0.0  0:00 mdrecoveryd\n" 
     581"   13 root   9  0     0    0     0 SW   0.0  0.0  0:01 kjournald\n" 
     582"   89 root   9  0     0    0     0 SW   0.0  0.0  0:00 khubd\n" 
     583"  219 root   9  0     0    0     0 SW   0.0  0.0  0:00 kjournald\n" 
     584"  220 root   9  0     0    0     0 SW   0.0  0.0  0:00 kjournald\n" 
    690585 
    691586#: ../chap4.xml:165(para) 
    692 msgid "" 
    693 "The first line of <command>top</command> contains the same information " 
    694 "displayed by the <command>uptime<indexterm><primary>uptime</primary></" 
    695 "indexterm></command> command:" 
    696 msgstr "" 
     587msgid "The first line of <command>top</command> contains the same information displayed by the <command>uptime<indexterm><primary>uptime</primary></indexterm></command> command:" 
     588msgstr "A primeira linha do comando <command>top</command> contém a mesma informação exibida pelo comando <command>uptime<indexterm><primary>uptime</primary></indexterm></command>:" 
    697589 
    698590#: ../chap4.xml:167(prompt) 
    699591msgid "jeff:~&gt;" 
    700 msgstr "" 
    701  
    702 #: ../chap4.xml:167(command) ../chap4.xml:833(command) 
     592msgstr "jeff:~&gt;" 
     593 
     594#: ../chap4.xml:167(command) 
     595#: ../chap4.xml:833(command) 
     596#, fuzzy 
    703597msgid "uptime" 
    704 msgstr "" 
     598msgstr "uptime" 
    705599 
    706600#: ../chap4.xml:166(screen) 
    707 #, no-wrap 
     601#, fuzzy, no-wrap 
    708602msgid "" 
    709603"\n" 
    … …  
    711605"  3:30pm, up 12 days, 23:29, 6 users, load average: 0.01, 0.02, 0.00\n" 
    712606msgstr "" 
     607"\n" 
     608"<placeholder-1/> <placeholder-2/>\n" 
     609"  3:30pm, up 12 days, 23:29, 6 users, load average: 0.01, 0.02, 0.00\n" 
    713610 
    714611#: ../chap4.xml:170(para) 
    715 msgid "" 
    716 "The data for these programs is stored among others in <filename>/var/run/" 
    717 "utmp</filename> (information about currently connected users) and in the " 
    718 "virtual file system <filename>/proc<indexterm><primary>proc</primary></" 
    719 "indexterm></filename>, for example <filename>/proc/loadavg</filename> " 
    720 "(average load information). There are all sorts of graphical applications to " 
    721 "view this data, such as the <application>Gnome System " 
    722 "Monitor<indexterm><primary>Gnome System Monitor</primary></indexterm></" 
    723 "application> and <emphasis>lavaps</emphasis>. Over at <ulink url=\"http://" 
    724 "www.freshmeat.net\">FreshMeat</ulink> and <ulink url=\"http://www." 
    725 "sourceforge.org\">SourceForge</ulink> you will find tens of applications " 
    726 "that centralize this information along with other server data and logs from " 
    727 "multiple servers on one (web) server, allowing monitoring of the entire IT " 
    728 "infrastructure from one workstation." 
    729 msgstr "" 
     612msgid "The data for these programs is stored among others in <filename>/var/run/utmp</filename> (information about currently connected users) and in the virtual file system <filename>/proc<indexterm><primary>proc</primary></indexterm></filename>, for example <filename>/proc/loadavg</filename> (average load information). There are all sorts of graphical applications to view this data, such as the <application>Gnome System Monitor<indexterm><primary>Gnome System Monitor</primary></indexterm></application> and <emphasis>lavaps</emphasis>. Over at <ulink url=\"http://www.freshmeat.net\">FreshMeat</ulink> and <ulink url=\"http://www.sourceforge.org\">SourceForge</ulink> you will find tens of applications that centralize this information along with other server data and logs from multiple servers on one (web) server, allowing monitoring of the entire IT infrastructure from one workstation." 
     613msgstr "Os dados para estes programas são armazenados, entre outros, em <filename>/var/run/utmp</filename> (informações sobre usuários conectados no momento) e no sistema de arquivos virtual <filename>/proc<indexterm><primary>proc</primary></indexterm></filename> - por exemplo <filename>/proc/loadavg</filename> (informação sobre carga média do sistema). Há todo o tipo de aplicativos gráficos para visualizar estes dados, tal como o  <application>Monitor de Sistema do Gnome<indexterm><primary>Monitor de Sistemas do Gnome</primary></indexterm></application> e emphasis>lavaps</emphasis>. No <ulink url=\"http://www.freshmeat.net\">FreshMeat</ulink> e no <ulink url=\"http://www.sourceforge.org\">SourceForge</ulink> você vai encontrar dezenas de aplicativos que centralizam esta informação juntamente com outros dados de servidores e logs de vários serviços em um único servidor (web), possibilitando o monitoramento de infraestrutura de TI inteira a partir de uma única estação de trabalho." 
    730614 
    731615#: ../chap4.xml:172(para) 
    732 msgid "" 
    733 "The relations<indexterm><primary>processes</primary><secondary>relations</" 
    734 "secondary></indexterm> between processes can be visualized using the " 
    735 "<command>pstree<indexterm><primary>pstree</primary></indexterm></command> " 
    736 "command:" 
    737 msgstr "" 
     616msgid "The relations<indexterm><primary>processes</primary><secondary>relations</secondary></indexterm> between processes can be visualized using the <command>pstree<indexterm><primary>pstree</primary></indexterm></command> command:" 
     617msgstr "As relações <indexterm><primary>processos</primary><secondary>relações</secondary></indexterm> entre os processos pode ser visualizada com o comando <command>pstree<indexterm><primary>pstree</primary></indexterm></command>:" 
    738618 
    739619#: ../chap4.xml:174(prompt) 
    740620msgid "sophie:~&gt;" 
    741 msgstr "" 
    742  
    743 #: ../chap4.xml:174(command) ../chap4.xml:812(command) 
     621msgstr "sophie:~&gt;" 
     622 
     623#: ../chap4.xml:174(command) 
     624#: ../chap4.xml:812(command) 
    744625msgid "pstree" 
    745 msgstr "" 
     626msgstr "pstree" 
    746627 
    747628#: ../chap4.xml:173(screen) 
    … …  
    803684"     `-xinetd-ipv6\n" 
    804685msgstr "" 
     686"\n" 
     687"<placeholder-1/> <placeholder-2/>\n" 
     688"init-+-amd\n" 
     689"     |-apmd\n" 
     690"     |-2*[artsd]\n" 
     691"     |-atd\n" 
     692"     |-crond\n" 
     693"     |-deskguide_apple\n" 
     694"     |-eth0\n" 
     695"     |-gdm---gdm-+-X\n" 
     696"     |           `-gnome-session-+-Gnome\n" 
     697"     |                           |-ssh-agent\n" 
     698"     |                           `-true\n" 
     699"     |-geyes_applet\n" 
     700"     |-gkb_applet\n" 
     701"     |-gnome-name-serv\n" 
     702"     |-gnome-smproxy\n" 
     703"     |-gnome-terminal-+-bash---vim\n" 
     704"     |                |-bash\n" 
     705"     |                |-bash---pstree\n" 
     706"     |                |-bash---ssh\n" 
     707"     |                |-bash---mozilla-bin---mozilla-bin---3*[mozilla-bin]\n" 
     708"     |                `-gnome-pty-helper\n" 
     709"     |-gpm\n" 
     710"     |-gweather\n" 
     711"     |-kapm-idled\n" 
     712"     |-3*[kdeinit]\n" 
     713"     |-keventd\n" 
     714"     |-khubd\n" 
     715"     |-5*[kjournald]\n" 
     716"     |-klogd\n" 
     717"     |-lockd---rpciod\n" 
     718"     |-lpd\n" 
     719"     |-mdrecoveryd\n" 
     720"     |-6*[mingetty]\n" 
     721"     |-8*[nfsd]\n" 
     722"     |-nscd---nscd---5*[nscd]\n" 
     723"     |-ntpd\n" 
     724"     |-3*[oafd]\n" 
     725"     |-panel\n" 
     726"     |-portmap\n" 
     727"     |-rhnsd\n" 
     728"     |-rpc.mountd\n" 
     729"     |-rpc.rquotad\n" 
     730"     |-rpc.statd\n" 
     731"     |-sawfish\n" 
     732"     |-screenshooter_a\n" 
     733"     |-sendmail\n" 
     734"     |-sshd---sshd---bash---su---bash\n" 
     735"     |-syslogd\n" 
     736"     |-tasklist_applet\n" 
     737"     |-vmnet-bridge\n" 
     738"     |-xfs\n" 
     739"     `-xinetd-ipv6\n" 
    805740 
    806741#: ../chap4.xml:228(para) 
    807 msgid "" 
    808 "The <option>-u</option> and <option>-a</option> options give additional " 
    809 "information. For more options and what they do, refer to the " 
    810 "<application>Info</application> pages." 
    811 msgstr "" 
     742msgid "The <option>-u</option> and <option>-a</option> options give additional information. For more options and what they do, refer to the <application>Info</application> pages." 
     743msgstr "As opções <option>-u</option> e <option>-a</option> dão informações adicionais. Para mais opções e o que elas fazem, consulte as páginas <application>Info</application>." 
    812744 
    813745#: ../chap4.xml:229(para) 
    814746msgid "In the next section, we will see how one process can create another." 
    815 msgstr "" 
     747msgstr "Na proxima seção, veremos como um processo pode criar um outro." 
    816748 
    817749#: ../chap4.xml:232(title) 
    818750msgid "Life and death of a process" 
    819 msgstr "" 
     751msgstr "Vida e morte de um processo" 
    820752 
    821753#: ../chap4.xml:233(title) 
    822754msgid "Process creation" 
    823 msgstr "" 
     755msgstr "Criação de processos" 
    824756 
    825757#: ../chap4.xml:234(para) 
    826 msgid "" 
    827 "A new process<indexterm><primary>processes</primary><secondary>creation</" 
    828 "secondary></indexterm> is created because an existing process makes an exact " 
    829 "copy of itself. This child process has the same environment as its parent, " 
    830 "only the process ID number is different. This procedure is called " 
    831 "<emphasis>forking<indexterm><primary>processes</primary><secondary>forking</" 
    832 "secondary></indexterm></emphasis>." 
    833 msgstr "" 
     758msgid "A new process<indexterm><primary>processes</primary><secondary>creation</secondary></indexterm> is created because an existing process makes an exact copy of itself. This child process has the same environment as its parent, only the process ID number is different. This procedure is called <emphasis>forking<indexterm><primary>processes</primary><secondary>forking</secondary></indexterm></emphasis>." 
     759msgstr "Um processo novo <indexterm><primary>processos</primary><secondary>criação</secondary></indexterm> é criado quando um processo existente cria uma cópia de si mesmo. Este processo filho tem o mesmo ambiente que seu pai, apenas o número ID do processo é diferente. Este procedimento é chamado de <emphasis>fork<indexterm><primary>processos</primary><secondary>bifurcar</secondary></indexterm></emphasis> (bifurcar)." 
    834760 
    835761#: ../chap4.xml:235(para) 
    836 msgid "" 
    837 "After the forking process, the address space of the child process is " 
    838 "overwritten with the new process data. This is done through an " 
    839 "<emphasis>exec<indexterm><primary>processes</primary><secondary>exec</" 
    840 "secondary></indexterm></emphasis> call to the system." 
    841 msgstr "" 
     762msgid "After the forking process, the address space of the child process is overwritten with the new process data. This is done through an <emphasis>exec<indexterm><primary>processes</primary><secondary>exec</secondary></indexterm></emphasis> call to the system." 
     763msgstr "Depois da bifurcação do processo, o espaço de endereçamento do processo filho é sobrescrito com os dados do novo processo. Isso é feito através da chamada de sistema<emphasis>exec<indexterm><primary>processos</primary><secondary>exec</secondary></indexterm></emphasis> (executar)." 
    842764 
    843765#: ../chap4.xml:236(para) 
    844 msgid "" 
    845 "The <emphasis>fork-and-exec<indexterm><primary>fork-and-exec</primary></" 
    846 "indexterm></emphasis> mechanism thus switches an old command with a new, " 
    847 "while the environment in which the new program is executed remains the same, " 
    848 "including configuration of input and output devices, environment variables " 
    849 "and priority. This mechanism is used to create all UNIX processes, so it " 
    850 "also applies to the Linux operating system. Even the first process, " 
    851 "<command>init<indexterm><primary>init</primary></indexterm></command>, with " 
    852 "process ID 1, is forked during the boot procedure in the so-called " 
    853 "<emphasis>bootstrapping<indexterm><primary>bootstrapping</primary></" 
    854 "indexterm></emphasis> procedure." 
    855 msgstr "" 
     766msgid "The <emphasis>fork-and-exec<indexterm><primary>fork-and-exec</primary></indexterm></emphasis> mechanism thus switches an old command with a new, while the environment in which the new program is executed remains the same, including configuration of input and output devices, environment variables and priority. This mechanism is used to create all UNIX processes, so it also applies to the Linux operating system. Even the first process, <command>init<indexterm><primary>init</primary></indexterm></command>, with process ID 1, is forked during the boot procedure in the so-called <emphasis>bootstrapping<indexterm><primary>bootstrapping</primary></indexterm></emphasis> procedure." 
     767msgstr "Assim o mecanismo <emphasis>bifurcar-e-executar<indexterm><primary>bifurcar-e-executar</primary></indexterm></emphasis> troca um comando antigo por um novo, enquanto o ambiente no qual o programa estava executando continua o mesmo, incluindo configuração de dispositivos de entrada e saída, variáveis de embiente e prioridade. Em UNIX esse mecanismo é usado para criar todos os processos, logo isto se aplica também ao sistema operacional Linux. Até mesmo o primeiro processo, com ID de processo 1, é bifurcado durante a inicialização do sistema, no famoso procedimento chamado <emphasis>bootstrapping<indexterm><primary>bootstrapping</primary></indexterm></emphasis>." 
    856768 
    857769#: ../chap4.xml:237(para) 
    858 msgid "" 
    859 "This scheme illustrates the fork-and-exec mechanism. The process ID changes " 
    860 "after the fork procedure:" 
    861 msgstr "" 
     770msgid "This scheme illustrates the fork-and-exec mechanism. The process ID changes after the fork procedure:" 
     771msgstr "Este esquema ilustra o mecanismo bifurcar-e-executar. O ID do processo muda depois do procedimento fork:" 
    862772 
    863773#: ../chap4.xml:238(title) 
    864774msgid "Fork-and-exec mechanism" 
    865 msgstr "" 
     775msgstr "Mecanismo bifurcar-e-executar" 
    866776 
    867777#: ../chap4.xml:247(phrase) 
    868 msgid "" 
    869 "Fork creates a new process with the same content as the parent in memory but " 
    870 "a different PID, exec replaces the content with the actual data to be " 
    871 "processed, PID stays the same." 
    872 msgstr "" 
     778msgid "Fork creates a new process with the same content as the parent in memory but a different PID, exec replaces the content with the actual data to be processed, PID stays the same." 
     779msgstr "Fork (bifurcar) cria um novo processo com o mesmo conteúdo de memória do seu pai, mas com um PID diferente. Exec (executar) substitui o conteúdo com os dados a serem processados de verdade, o PID continua o mesmo." 
    873780 
    874781#: ../chap4.xml:252(para) 
    875 msgid "" 
    876 "There are a couple of cases in which <command>init</command> becomes the " 
    877 "parent of a process, while the process was not started by <command>init</" 
    878 "command>, as we already saw in the <command>pstree</command> example. Many " 
    879 "programs, for instance, <emphasis>daemonize<indexterm><primary>processes</" 
    880 "primary><secondary>daemonizing</secondary></indexterm></emphasis> their " 
    881 "child processes, so they can keep on running when the parent stops or is " 
    882 "being stopped. A window manager is a typical example; it starts an " 
    883 "<command>xterm</command> process that generates a shell that accepts " 
    884 "commands. The window manager then denies any further responsibility and " 
    885 "passes the child process to <command>init</command>. Using this mechanism, " 
    886 "it is possible to change window managers without interrupting running " 
    887 "applications." 
    888 msgstr "" 
     782msgid "There are a couple of cases in which <command>init</command> becomes the parent of a process, while the process was not started by <command>init</command>, as we already saw in the <command>pstree</command> example. Many programs, for instance, <emphasis>daemonize<indexterm><primary>processes</primary><secondary>daemonizing</secondary></indexterm></emphasis> their child processes, so they can keep on running when the parent stops or is being stopped. A window manager is a typical example; it starts an <command>xterm</command> process that generates a shell that accepts commands. The window manager then denies any further responsibility and passes the child process to <command>init</command>. Using this mechanism, it is possible to change window managers without interrupting running applications." 
     783msgstr "Existem uma ou duas situações onde o <command>init</command> se torna o pai direto de um processo, sendo que o processo não foi iniciado diretamente pelo processo <command>init</command>, como já vimos no exemplo do comando <command>pstree</command>. Muitos programas, por exemplo, transformam seus filhos em <emphasis>daemons<indexterm><primary>processos</primary><secondary>transformar em daemon</secondary></indexterm></emphasis>, de forma que eles possam continuar a executar quando o seu pai finaliza ou é finalizado. Um gerenciador de janelas é um exemplo típico; ele inicia um processo <command>xterm</command> que cria um shell que aceita comandos. Então o gerenciador de janelas nega qualquer responsabilidade futura e passa a guarda do processo filho para o <command>init</command>. Com esse mecanismo, é possível trocar de gerenciador de janelas sem interromper os aplicativos que foram iniciados por eles." 
    889784 
    890785#: ../chap4.xml:253(para) 
    891 msgid "" 
    892 "Every now and then things go wrong, even in good families. In an exceptional " 
    893 "case, a process might finish while the parent does not wait for the " 
    894 "completion of this process. Such an unburied process is called a " 
    895 "<emphasis>zombie</emphasis> process<indexterm><primary>processes</" 
    896 "primary><secondary>zombie</secondary></indexterm>." 
    897 msgstr "" 
     786msgid "Every now and then things go wrong, even in good families. In an exceptional case, a process might finish while the parent does not wait for the completion of this process. Such an unburied process is called a <emphasis>zombie</emphasis> process<indexterm><primary>processes</primary><secondary>zombie</secondary></indexterm>." 
     787msgstr "Vez ou outra as coisas vão mal, até nas melhores famílias. Num caso à parte, um processo pode finalizar enquanto o pai não esperou pelo términio desse processo. Um processo sem enterro assim é chamando de processo <emphasis>zumbi</emphasis><indexterm><primary>processos</primary><secondary>zumbi</secondary></indexterm>." 
    898788 
    899789#: ../chap4.xml:255(title) 
    900790msgid "Ending processes" 
    901 msgstr "" 
     791msgstr "Finalizando processos" 
    902792 
    903793#: ../chap4.xml:256(para) 
    904 msgid "" 
    905 "When a process<indexterm><primary>processes</primary><secondary>ending</" 
    906 "secondary></indexterm> ends normally (it is not killed or otherwise " 
    907 "unexpectedly interrupted), the program returns its <emphasis>exit " 
    908 "status<indexterm><primary>exit status</primary></indexterm></emphasis> to " 
    909 "the parent. This exit status is a number returned by the program providing " 
    910 "the results of the program's execution. The system of returning information " 
    911 "upon executing a job has its origin in the C programming language in which " 
    912 "UNIX has been written." 
    913 msgstr "" 
     794#, fuzzy 
     795msgid "When a process<indexterm><primary>processes</primary><secondary>ending</secondary></indexterm> ends normally (it is not killed or otherwise unexpectedly interrupted), the program returns its <emphasis>exit status<indexterm><primary>exit status</primary></indexterm></emphasis> to the parent. This exit status is a number returned by the program providing the results of the program's execution. The system of returning information upon executing a job has its origin in the C programming language in which UNIX has been written." 
     796msgstr "Quando um processo <indexterm><primary>processo</primary><secondary>finalizando</secondary></indexterm> finaliza normalmente (não é morto e nem interrompido de maneira inesperada de alguma outra forma), o programa retorna seu <emphasis>status de finalização<indexterm><primary>status de finalização</primary></indexterm></emphasis> para seu processo pai. O status de finalização é um número que provê os resultados da execução do programa. O esquema de retornar informação sempre que executar uma tarefa tem sua origem na linguagem de programação C na a qual o UNIX tem sido escrito." 
    914797 
    915798#: ../chap4.xml:257(para) 
    916 msgid "" 
    917 "The return codes<indexterm><primary>processes</primary><secondary>return " 
    918 "codes</secondary></indexterm> can then be interpreted by the parent, or in " 
    919 "scripts. The values of the return codes are program-specific. This " 
    920 "information can usually be found in the man pages of the specified program, " 
    921 "for example the <command>grep</command> command returns <computeroutput>-1</" 
    922 "computeroutput> if no matches are found, upon which a message on the lines " 
    923 "of <quote>No files found</quote> can be printed. Another example is the " 
    924 "<application>Bash</application> builtin command <command>true</command>, " 
    925 "which does nothing except return an exit status of 0, meaning success." 
    926 msgstr "" 
     799msgid "The return codes<indexterm><primary>processes</primary><secondary>return codes</secondary></indexterm> can then be interpreted by the parent, or in scripts. The values of the return codes are program-specific. This information can usually be found in the man pages of the specified program, for example the <command>grep</command> command returns <computeroutput>-1</computeroutput> if no matches are found, upon which a message on the lines of <quote>No files found</quote> can be printed. Another example is the <application>Bash</application> builtin command <command>true</command>, which does nothing except return an exit status of 0, meaning success." 
     800msgstr "Os códigos de retorno <indexterm><primary>processos</primary><secondary>códigos de retorno</secondary></indexterm> podem então serem interpretados pelo pai, ou em scripts. Os valores dos códigos de retorno são específicos a cada programa. Geralmente essa informação pode ser encontrada nos manuais do programa em questão, por exemplo, o comando <command>grep</command> retorna <computeroutput>-1</computeroutput> se nenhum padrão coincidente for encontrado, baseada na qual a mensagem <quote>No files found</quote> pode ser impressa. Outro exemplo é o comando interno <command>true</command> do <application>Bash</application>, que não faz nada além de retornar 0, que significa sucesso." 
    927801 
    928802#: ../chap4.xml:259(title) 
    929803msgid "Signals" 
    930 msgstr "" 
     804msgstr "Sinais" 
    931805 
    932806#: ../chap4.xml:260(para) 
    933 msgid "" 
    934 "Processes end<indexterm><primary>processes</primary><secondary>stopping</" 
    935 "secondary></indexterm> because they receive a " 
    936 "signal<indexterm><primary>processes</primary><secondary>signal</secondary></" 
    937 "indexterm>. There are multiple signals that you can send to a process. Use " 
    938 "the <command>kill<indexterm><primary>kill</primary></indexterm></command> " 
    939 "command to send a signal to a process. The command <command>kill <option>-l</" 
    940 "option></command> shows a list of signals. Most signals are for internal use " 
    941 "by the system, or for programmers when they write code. As a user, you will " 
    942 "need the following signals<indexterm><primary>signals</" 
    943 "primary><secondary>overview</secondary></indexterm>:" 
    944 msgstr "" 
     807msgid "Processes end<indexterm><primary>processes</primary><secondary>stopping</secondary></indexterm> because they receive a signal<indexterm><primary>processes</primary><secondary>signal</secondary></indexterm>. There are multiple signals that you can send to a process. Use the <command>kill<indexterm><primary>kill</primary></indexterm></command> command to send a signal to a process. The command <command>kill <option>-l</option></command> shows a list of signals. Most signals are for internal use by the system, or for programmers when they write code. As a user, you will need the following signals<indexterm><primary>signals</primary><secondary>overview</secondary></indexterm>:" 
     808msgstr "Processos finalizam <indexterm><primary>processos</primary><secondary>parando</secondary></indexterm> porque eles recebem um sinal <indexterm><primary>processos</primary><secondary>sinal</secondary></indexterm>. São vários os sinais que podem ser enviados a um processo. Uso o comando <command>kill<indexterm><primary>kill</primary></indexterm></command> (matar) para enviar um sinal para um processo. O comando <command>kill <option>-l</option></command> exibe uma lista de sinais. A maoria dos sinais são para uso interno do sistema, ou para programadores quando escrevem programas. Enquanto usuário, você precisará apenas da seguinte visão geral <indexterm><primary>signais</primary><secondary>visão geral</secondary></indexterm>:" 
    945809 
    946810#: ../chap4.xml:262(title) 
    947811msgid "Common signals" 
    948 msgstr "" 
     812msgstr "Sinais comuns" 
    949813 
    950814#: ../chap4.xml:266(entry) 
    951815msgid "Signal name" 
    952 msgstr "" 
     816msgstr "Nome do sinal" 
    953817 
    954818#: ../chap4.xml:266(entry) 
    955819msgid "Signal number" 
    956 msgstr "" 
     820msgstr "Número do sinal" 
    957821 
    958822#: ../chap4.xml:271(primary) 
    959823msgid "SIGTERM" 
    960 msgstr "" 
     824msgstr "SIGTERM" 
    961825 
    962826#: ../chap4.xml:271(entry) 
    963827msgid "SIGTERM<indexterm><placeholder-1/></indexterm>" 
    964 msgstr "" 
     828msgstr "SIGTERM<indexterm><placeholder-1/></indexterm>" 
    965829 
    966830#: ../chap4.xml:271(entry) 
    967831msgid "15" 
    968 msgstr "" 
     832msgstr "15" 
    969833 
    970834#: ../chap4.xml:271(entry) 
    971835msgid "Terminate the process in an orderly way." 
    972 msgstr "" 
     836msgstr "Termina o processo de forma organizada." 
    973837 
    974838#: ../chap4.xml:274(primary) 
    975839msgid "SIGINT" 
    976 msgstr "" 
     840msgstr "SIGINT" 
    977841 
    978842#: ../chap4.xml:274(entry) 
    979843msgid "SIGINT<indexterm><placeholder-1/></indexterm>" 
    980 msgstr "" 
     844msgstr "SIGINT<indexterm><placeholder-1/></indexterm>" 
    981845 
    982846#: ../chap4.xml:274(entry) 
    983847msgid "2" 
    984 msgstr "" 
     848msgstr "2" 
    985849 
    986850#: ../chap4.xml:274(entry) 
    987851msgid "Interrupt the process. A process can ignore this signal." 
    988 msgstr "" 
     852msgstr "Interrompe o processo. Um processo pode ignorar esse sinal." 
    989853 
    990854#: ../chap4.xml:278(primary) 
    991855msgid "SIGKILL" 
    992 msgstr "" 
     856msgstr "SIGKILL" 
    993857 
    994858#: ../chap4.xml:278(entry) 
    995859msgid "SIGKILL<indexterm><placeholder-1/></indexterm>" 
    996 msgstr "" 
     860msgstr "SIGKILL<indexterm><placeholder-1/></indexterm>" 
    997861 
    998862#: ../chap4.xml:278(entry) 
    999863msgid "9" 
    1000 msgstr "" 
     864msgstr "9" 
    1001865 
    1002866#: ../chap4.xml:278(entry) 
    1003867msgid "Interrupt the process. A process can not ignore this signal." 
    1004 msgstr "" 
     868msgstr "Interrompe o processo. Um processo não pode ignorar esse sinal." 
    1005869 
    1006870#: ../chap4.xml:282(primary) 
    1007871msgid "SIGHUP" 
    1008 msgstr "" 
     872msgstr "SIGHUP" 
    1009873 
    1010874#: ../chap4.xml:282(entry) 
    1011875msgid "SIGHUP<indexterm><placeholder-1/></indexterm>" 
    1012 msgstr "" 
     876msgstr "SIGHUP<indexterm><placeholder-1/></indexterm>" 
    1013877 
    1014878#: ../chap4.xml:282(entry) 
    1015879msgid "1" 
    1016 msgstr "" 
     880msgstr "1" 
    1017881 
    1018882#: ../chap4.xml:282(entry) 
    1019883msgid "For daemons: reread the configuration file." 
    1020 msgstr "" 
     884msgstr "Para daemons: que releiam suas configurações." 
    1021885 
    1022886#: ../chap4.xml:288(para) 
    1023 msgid "" 
    1024 "You can read more about default actions that are taken when sending a signal " 
    1025 "to a process in <command>man <option>7</option><parameter>signal</" 
    1026 "parameter></command>." 
    1027 msgstr "" 
     887msgid "You can read more about default actions that are taken when sending a signal to a process in <command>man <option>7</option><parameter>signal</parameter></command>." 
     888msgstr "Você pode ler mais sobre as ações padrões quando um sinal é enviado a um processo em <command>man <option>7</option><parameter>sinal</parameter></command>." 
    1028889 
    1029890#: ../chap4.xml:292(para) 
    1030 msgid "" 
    1031 "As promised in the previous chapter, we will now discuss the special modes " 
    1032 "SUID<indexterm><primary>SUID</primary></indexterm> and " 
    1033 "SGID<indexterm><primary>SGID</primary></indexterm> in more detail. These " 
    1034 "modes exist to provide normal users the ability to execute tasks they would " 
    1035 "normally not be able to do because of the tight file permission scheme used " 
    1036 "on UNIX based systems. In the ideal situation special modes are used as " 
    1037 "sparsely as possible, since they include security risks. Linux developers " 
    1038 "have generally tried to avoid them as much as possible. The Linux " 
    1039 "<command>ps</command> version, for example, uses the information stored in " 
    1040 "the <filename>/proc</filename> file system, which is accessible to everyone, " 
    1041 "thus avoiding exposition of sensitive system data and resources to the " 
    1042 "general public. Before that, and still on older UNIX systems, the " 
    1043 "<command>ps</command> program needed access to files such as <filename>/dev/" 
    1044 "mem<indexterm><primary>mem</primary></indexterm></filename> and <filename>/" 
    1045 "dev/kmem<indexterm><primary>kmem</primary></indexterm></filename>, which had " 
    1046 "disadvantages because of the permissions and ownerships on these files:" 
    1047 msgstr "" 
     891msgid "As promised in the previous chapter, we will now discuss the special modes SUID<indexterm><primary>SUID</primary></indexterm> and SGID<indexterm><primary>SGID</primary></indexterm> in more detail. These modes exist to provide normal users the ability to execute tasks they would normally not be able to do because of the tight file permission scheme used on UNIX based systems. In the ideal situation special modes are used as sparsely as possible, since they include security risks. Linux developers have generally tried to avoid them as much as possible. The Linux <command>ps</command> version, for example, uses the information stored in the <filename>/proc</filename> file system, which is accessible to everyone, thus avoiding exposition of sensitive system data and resources to the general public. Before that, and still on older UNIX systems, the <command>ps</command> program needed access to files such as <filename>/dev/mem<indexterm><primary>mem</primary></indexterm></filename> and <filename>/dev/kmem<indexterm><primary>kmem</primary></indexterm></filename>, which had disadvantages because of the permissions and ownerships on these files:" 
     892msgstr "Como prometido no capítulo anterior, iremos agora discutir os modos especiais SUID<indexterm><primary>SUID</primary></indexterm> e SGID<indexterm><primary>SGID</primary></indexterm> em mais detalhes. Estes modos existem para permitir que usuários normais executem tarefas que normalmente não poderiam devido ao rigoroso esquema de permissões usado em sistemas baseados em UNIX. O ideal é que os modos especias sejam usados o mínimo possível, já que acrescentam riscos à segurança. Desenvolvedores Linux geralmente têm tentado evitá-los o quanto podem. A versão Linux do comando <command>ps</command>, por exemplo, usa a informação armazenada nos arquivos <filename>/proc</filename>, que são acessíveis a todos, mas evita expor recursos e informações sensíveis do sistema para o público geral. Antes disso, e ainda nos sistemas UNIX mais velhos, o programa <command>ps</command> precisava do acesso a arquivos como <filename>/dev/mem<indexterm><primary>mem</primary></indexterm></filename> e <filename>/dev/kmem<indexterm><primary>kmem</primary></indexterm></filename>, o qual tinha desvantagens por causa das permissões e posses desses arquivos:" 
    1048893 
    1049894#: ../chap4.xml:294(prompt) 
    1050895msgid "rita:~&gt;" 
    1051 msgstr "" 
     896msgstr "rita:~&gt;" 
    1052897 
    1053898#: ../chap4.xml:294(command) 
    1054899msgid "ls -l /dev/*mem" 
    1055 msgstr "" 
     900msgstr "ls -l /dev/*mem" 
    1056901 
    1057902#: ../chap4.xml:293(screen) 
    1058 #, no-wrap 
     903#, fuzzy, no-wrap 
    1059904msgid "" 
    1060905"\n" 
    … …  
    1063908"crw-r-----    1 root     kmem       1,   1 Aug 30 22:30 /dev/mem\n" 
    1064909msgstr "" 
     910"\n" 
     911"<placeholder-1/> <placeholder-2/>\n" 
     912"crw-r-----    1 root     kmem       1,   2 Aug 30 22:30 /dev/kmem\n" 
     913"crw-r-----    1 root     kmem       1,   1 Aug 30 22:30 /dev/mem\n" 
    1065914 
    1066915#: ../chap4.xml:298(para) 
    1067 msgid "" 
    1068 "With older versions of <command>ps</command>, it was not possible to start " 
    1069 "the program as a common user, unless special modes were applied to it." 
    1070 msgstr "" 
     916msgid "With older versions of <command>ps</command>, it was not possible to start the program as a common user, unless special modes were applied to it." 
     917msgstr "Com as versões mais antigas do comando <command>ps</command>, não é possível iniciar o programa como um usuário comum, a não ser que os modos especiais tenham sido aplicados." 
    1071918 
    1072919#: ../chap4.xml:299(para) 
    1073 msgid "" 
    1074 "While we generally try to avoid applying any special modes, it is sometimes " 
    1075 "necessary to use an SUID. An example is the mechanism for changing " 
    1076 "passwords. Of course users will want to do this themselves instead of having " 
    1077 "their password set by the system administrator. As we know, user names and " 
    1078 "passwords are listed in the <filename>/etc/passwd<indexterm><primary>passwd</" 
    1079 "primary></indexterm></filename> file, which has these access permissions and " 
    1080 "owners:" 
    1081 msgstr "" 
     920msgid "While we generally try to avoid applying any special modes, it is sometimes necessary to use an SUID. An example is the mechanism for changing passwords. Of course users will want to do this themselves instead of having their password set by the system administrator. As we know, user names and passwords are listed in the <filename>/etc/passwd<indexterm><primary>passwd</primary></indexterm></filename> file, which has these access permissions and owners:" 
     921msgstr "Apesar de geralmente tentamos evitar aplicar qualquer modo especial, algumas vezes é necessário usar um SUID. Um exemplo é o mecanismo para torcar de senhas. É claro que os usuários vão querer fazer isso eles mesmos ao invés de ter suas senhas definidas pelo administrador do sistema. Como nós sabemos, nomes de usuários e senhas são listados no arquivo <filename>/etc/passwd<indexterm><primary>passwd</primary></indexterm></filename>, o qual tem estes donos e permissões:" 
    1082922 
    1083923#: ../chap4.xml:301(prompt) 
    1084924msgid "bea:~&gt;" 
    1085 msgstr "" 
     925msgstr "bea:~&gt;" 
    1086926 
    1087927#: ../chap4.xml:301(command) 
    1088928msgid "ls -l /etc/passwd" 
    1089 msgstr "" 
     929msgstr "ls -l /etc/passwd" 
    1090930 
    1091931#: ../chap4.xml:300(screen) 
    … …  
    1096936"-rw-r--r--    1 root     root     1267 Jan 16 14:43 /etc/passwd\n" 
    1097937msgstr "" 
     938"\n" 
     939"<placeholder-1/> <placeholder-2/>\n" 
     940"-rw-r--r--    1 root     root     1267 Jan 16 14:43 /etc/passwd\n" 
    1098941 
    1099942#: ../chap4.xml:304(para) 
    1100 msgid "" 
    1101 "Still, users need to be able to change their own information in this file. " 
    1102 "This is achieved by giving the <command>passwd</command> program special " 
    1103 "permissions:" 
    1104 msgstr "" 
    1105  
    1106 #: ../chap4.xml:306(prompt) ../chap4.xml:309(prompt) 
     943msgid "Still, users need to be able to change their own information in this file. This is achieved by giving the <command>passwd</command> program special permissions:" 
     944msgstr "Os usuários precisam poder alterar suas próprias informações nesse arquivo. Isto é alcançado ao dar permições especiais ao comando <command>passwd</command>:" 
     945 
     946#: ../chap4.xml:306(prompt) 
     947#: ../chap4.xml:309(prompt) 
    1107948msgid "mia:~&gt;" 
    1108 msgstr "" 
     949msgstr "mia:~&gt;" 
    1109950 
    1110951#: ../chap4.xml:306(command) 
    1111952msgid "which passwd" 
    1112 msgstr "" 
     953msgstr "which passwd" 
    1113954 
    1114955#: ../chap4.xml:309(command) 
    1115956msgid "ls -l /usr/bin/passwd" 
    1116 msgstr "" 
     957msgstr "ls -l /usr/bin/passwd" 
    1117958 
    1118959#: ../chap4.xml:305(screen) 
    … …  
    1126967"-r-s--x--x    1 root     root    13476 Aug  7 06:03 /usr/bin/passwd*\n" 
    1127968msgstr "" 
     969"\n" 
     970"<placeholder-1/> <placeholder-2/>\n" 
     971"passwd is /usr/bin/passwd\n" 
     972"\n" 
     973"<placeholder-3/> <placeholder-4/>\n" 
     974"-r-s--x--x    1 root     root    13476 Aug  7 06:03 /usr/bin/passwd*\n" 
    1128975 
    1129976#: ../chap4.xml:312(para) 
    1130 msgid "" 
    1131 "When called, the <command>passwd</command> command will run using the access " 
    1132 "permissions<indexterm><primary>file permissions</primary><secondary>SUID</" 
    1133 "secondary></indexterm> of <emphasis>root</emphasis>, thus enabling a common " 
    1134 "user to edit the password file which is owned by the system admin." 
    1135 msgstr "" 
     977msgid "When called, the <command>passwd</command> command will run using the access permissions<indexterm><primary>file permissions</primary><secondary>SUID</secondary></indexterm> of <emphasis>root</emphasis>, thus enabling a common user to edit the password file which is owned by the system admin." 
     978msgstr "Quando chamado, o comando <command>passwd</command> irá executar usando as permissões de acesso <indexterm><primary>permissões de arquivo</primary><secondary>SUID</secondary></indexterm> de <emphasis>root</emphasis>, e assim permitindo um usuário comum editar o arquivo de senhas, o qual pertence ao administrador do sistema." 
    1136979 
    1137980#: ../chap4.xml:313(para) 
    1138 msgid "" 
    1139 "SGID modes on a file don't occur nearly as frequently as SUID, because SGID " 
    1140 "often involves the creation of extra groups. In some cases, however, we have " 
    1141 "to go through this trouble in order to build an elegant solution (don't " 
    1142 "worry about this too much - the necessary groups are usually created upon " 
    1143 "installation). This is the case for the " 
    1144 "<command>write<indexterm><primary>write</primary>4dwx<secondary/></" 
    1145 "indexterm></command> and <command>wall<indexterm><primary>wall</primary></" 
    1146 "indexterm></command> programs, which are used to send messages to other " 
    1147 "users' terminals<indexterm><primary>terminal</primary><secondary>send a " 
    1148 "message</secondary></indexterm> (ttys). The <command>write</command> command " 
    1149 "writes a message to a single user, while <command>wall</command> writes to " 
    1150 "all connected users." 
    1151 msgstr "" 
     981msgid "SGID modes on a file don't occur nearly as frequently as SUID, because SGID often involves the creation of extra groups. In some cases, however, we have to go through this trouble in order to build an elegant solution (don't worry about this too much - the necessary groups are usually created upon installation). This is the case for the <command>write<indexterm><primary>write</primary>4dwx<secondary/></indexterm></command> and <command>wall<indexterm><primary>wall</primary></indexterm></command> programs, which are used to send messages to other users' terminals<indexterm><primary>terminal</primary><secondary>send a message</secondary></indexterm> (ttys). The <command>write</command> command writes a message to a single user, while <command>wall</command> writes to all connected users." 
     982msgstr "Modos SGID não são usados com tanta frequência quanto o SUID, porque SGID geralmente envolve a criação de grupos extras. Em alguns casos, no entanto, nós temos que encarar esse problema no intuito de construir uma solução elegante (não se preocupe tanto com isso - os grupos necessários geralmente são criados durante a instalação). Esse é o caso do comando <command>write<indexterm><primary>write</primary>4dwx<secondary/></indexterm></command> " 
    1152983 
    1153984#: ../chap4.xml:314(para) 
    1154 msgid "" 
    1155 "Sending text to another user's terminal or graphical display is normally not " 
    1156 "allowed. In order to bypass this problem, a group has been created, which " 
    1157 "owns all terminal devices. When the <command>write</command> and " 
    1158 "<command>wall</command> commands are granted SGID permissions, the commands " 
    1159 "will run using the access rights as applicable to this group, <emphasis>tty</" 
    1160 "emphasis> in the example. Since this group has write access to the " 
    1161 "destination terminal, also a user having no permissions to use that terminal " 
    1162 "in any way can send messages to it." 
    1163 msgstr "" 
     985msgid "Sending text to another user's terminal or graphical display is normally not allowed. In order to bypass this problem, a group has been created, which owns all terminal devices. When the <command>write</command> and <command>wall</command> commands are granted SGID permissions, the commands will run using the access rights as applicable to this group, <emphasis>tty</emphasis> in the example. Since this group has write access to the destination terminal, also a user having no permissions to use that terminal in any way can send messages to it." 
     986msgstr "Enviar texto para o terminal ou dispositivo gráfico de outro usuário não é permitido. Para contornar esse problema, um grupo que possui todos os dispositivos de terminal foi criado. Quando são dadas permissões SGID aos comandos <command>write</command> e <command>wall</command>, os comandos executarão com os direitos de acessos aplicaveis para este grupo, <emphasis>tty</emphasis> no caso do exemplo. Já que o grupo tem direito de escrita para o terminal de destino, um usuário sem permissões para usar o terminal também pode enviar mensagens a ele." 
    1164987 
    1165988#: ../chap4.xml:315(para) 
    1166 msgid "" 
    1167 "In the example below, user <emphasis>joe</emphasis> first finds out on which " 
    1168 "terminal his correspondent is connected, using the <command>who</command> " 
    1169 "command. Then he sends her a message using the <command>write</command> " 
    1170 "command. Also illustrated are the access rights on the <command>write</" 
    1171 "command> program and on the terminals occupied by the receiving user: it is " 
    1172 "clear that others than the user owner have no " 
    1173 "permissions<indexterm><primary>file permissions</primary><secondary>SGID</" 
    1174 "secondary></indexterm> on the device, except for the group owner, which can " 
    1175 "write to it." 
    1176 msgstr "" 
    1177  
    1178 #: ../chap4.xml:317(prompt) ../chap4.xml:320(prompt) ../chap4.xml:323(prompt) 
    1179 #: ../chap4.xml:330(prompt) ../chap4.xml:333(prompt) ../chap4.xml:618(prompt) 
    1180 #: ../chap4.xml:621(prompt) ../chap4.xml:626(prompt) ../chap4.xml:629(prompt) 
     989msgid "In the example below, user <emphasis>joe</emphasis> first finds out on which terminal his correspondent is connected, using the <command>who</command> command. Then he sends her a message using the <command>write</command> command. Also illustrated are the access rights on the <command>write</command> program and on the terminals occupied by the receiving user: it is clear that others than the user owner have no permissions<indexterm><primary>file permissions</primary><secondary>SGID</secondary></indexterm> on the device, except for the group owner, which can write to it." 
     990msgstr "No exemplo abaixo, o usuário <emphasis>joe</emphasis> primeiro descobre qual terminal a sua destinatária está conectada, usando o comando <command>who</command>. Então ele a envia uma mensagem usando o comando <command>write</command>. Estão ilustrados também os direitos de acesso do programa <command>write</command> e dos terminais ocupados pelo usuário receptor: está claro que outros além do usuário não tem acesso <indexterm><primary>permissões de arquivo</primary><secondary>SGID</secondary></indexterm> ao dispositivo, exceto para o grupo, que pode escrever nele." 
     991 
     992#: ../chap4.xml:317(prompt) 
     993#: ../chap4.xml:320(prompt) 
     994#: ../chap4.xml:323(prompt) 
     995#: ../chap4.xml:330(prompt) 
     996#: ../chap4.xml:333(prompt) 
     997#: ../chap4.xml:618(prompt) 
     998#: ../chap4.xml:621(prompt) 
     999#: ../chap4.xml:626(prompt) 
     1000#: ../chap4.xml:629(prompt) 
    11811001#: ../chap4.xml:631(prompt) 
    11821002msgid "joe:~&gt;" 
    1183 msgstr "" 
     1003msgstr "joe:~&gt;" 
    11841004 
    11851005#: ../chap4.xml:317(command) 
    11861006msgid "which write" 
    1187 msgstr "" 
     1007msgstr "which write" 
    11881008 
    11891009#: ../chap4.xml:320(command) 
    11901010msgid "ls -l /usr/bin/write" 
    1191 msgstr "" 
    1192  
    1193 #: ../chap4.xml:323(primary) ../chap4.xml:845(command) 
     1011msgstr "ls -l /usr/bin/write" 
     1012 
     1013#: ../chap4.xml:323(primary) 
     1014#: ../chap4.xml:845(command) 
    11941015msgid "who" 
    1195 msgstr "" 
     1016msgstr "who" 
    11961017 
    11971018#: ../chap4.xml:323(secondary) 
    11981019msgid "example" 
    1199 msgstr "" 
     1020msgstr "exemplo" 
    12001021 
    12011022#: ../chap4.xml:323(command) 
    12021023msgid "who<indexterm><placeholder-1/><placeholder-2/></indexterm>" 
    1203 msgstr "" 
     1024msgstr "who<indexterm><placeholder-1/><placeholder-2/></indexterm>" 
    12041025 
    12051026#: ../chap4.xml:330(command) 
    12061027msgid "ls -l /dev/tty1" 
    1207 msgstr "" 
     1028msgstr "ls -l /dev/tty1" 
    12081029 
    12091030#: ../chap4.xml:333(command) 
    12101031msgid "write jenny tty1" 
    1211 msgstr "" 
     1032msgstr "write jenny tty1" 
    12121033 
    12131034#: ../chap4.xml:316(screen) 
    … …  
    12351056"^C\n" 
    12361057msgstr "" 
     1058"\n" 
     1059"<placeholder-1/> <placeholder-2/>\n" 
     1060"write is /usr/bin/write\n" 
     1061"\n" 
     1062"<placeholder-3/> <placeholder-4/>\n" 
     1063"-rwxr-sr-x    1 root     tty      8744 Dec  5 00:55 /usr/bin/write*\n" 
     1064"\n" 
     1065"<placeholder-5/> <placeholder-6/>\n" 
     1066"jenny     tty1     Jan 23 11:41\n" 
     1067"jenny     pts/1    Jan 23 12:21 (:0)\n" 
     1068"jenny     pts/2    Jan 23 12:22 (:0)\n" 
     1069"jenny     pts/3    Jan 23 12:22 (:0)\n" 
     1070"joe       pts/0    Jan 20 10:13 (lo.callhost.org)\n" 
     1071"\n" 
     1072"<placeholder-7/> <placeholder-8/>\n" 
     1073"crw--w----    1 jenny   tty  4,     1 Jan 23 11:41 /dev/tty1\n" 
     1074"\n" 
     1075"<placeholder-9/> <placeholder-10/>\n" 
     1076"ei Jenny, vamos almoçar juntos?\n" 
     1077"^C\n" 
    12371078 
    12381079#: ../chap4.xml:337(para) 
    12391080msgid "User <emphasis>jenny</emphasis> gets this on her screen:" 
    1240 msgstr "" 
     1081msgstr "Usuária <emphasis>jenny</emphasis> recebe em sua tela:" 
    12411082 
    12421083#: ../chap4.xml:338(screen) 
    … …  
    12481089"EOF\n" 
    12491090msgstr "" 
     1091"\n" 
     1092"Mensagem de joe@lo.callhost.org em ptys/1 às 12:36 ...\n" 
     1093"ei Jenny, vamos almoçar juntos?\n" 
     1094"EOF\n" 
    12501095 
    12511096#: ../chap4.xml:343(para) 
    1252 msgid "" 
    1253 "After receiving a message, the terminal can be cleared using the " 
    1254 "<keycap>Ctrl</keycap>+<keycap>L</keycap> key combination. In order to " 
    1255 "receive no messages at all (except from the system administrator), use the " 
    1256 "<command>mesg</command> command. To see which connected users accept " 
    1257 "messages from others use <command>who <option>-w</option></command>. All " 
    1258 "features are fully explained in the <application>Info</application> pages of " 
    1259 "each command." 
    1260 msgstr "" 
     1097msgid "After receiving a message, the terminal can be cleared using the <keycap>Ctrl</keycap>+<keycap>L</keycap> key combination. In order to receive no messages at all (except from the system administrator), use the <command>mesg</command> command. To see which connected users accept messages from others use <command>who <option>-w</option></command>. All features are fully explained in the <application>Info</application> pages of each command." 
     1098msgstr "fApós receber a mensagem, o terminal pode ser limpo com a combinação de teclas <keycap>Ctrl</keycap>+<keycap>L</keycap>. Para não receber nenhuma mensagem (exceto do administrador do sistema), use o comando <command>mesg</command>. Para ver quais usuários conectados aceitas mensagens de outros, use o comando <command>who <option>-w</option></command>. Todos os recursos são explicados por completo nas páginas <application>Info</application> de cada comando." 
    12611099 
    12621100#: ../chap4.xml:344(title) 
    12631101msgid "Group names may vary" 
    1264 msgstr "" 
     1102msgstr "Nomes de grupos podem variar" 
    12651103 
    12661104#: ../chap4.xml:345(para) 
    1267 msgid "" 
    1268 "The group scheme is specific to the distribution. Other distributions may " 
    1269 "use other names or other solutions." 
    1270 msgstr "" 
     1105msgid "The group scheme is specific to the distribution. Other distributions may use other names or other solutions." 
     1106msgstr "O esquema de grupos é próprio da distribuição sendo usada. Outras distribuições podem usar outros nomes ou outras soluções." 
    12711107 
    12721108#: ../chap4.xml:350(title) 
    12731109msgid "Boot process, Init and shutdown" 
    1274 msgstr "" 
     1110msgstr "Processo de inicialização, iniciar e desligar" 
    12751111 
    12761112#: ../chap4.xml:351(title) 
    12771113msgid "Introduction" 
    1278 msgstr "" 
     1114msgstr "Introdução" 
    12791115 
    12801116#: ../chap4.xml:352(para) 
    1281 msgid "" 
    1282 "One of the most powerful aspects of Linux concerns its open method of " 
    1283 "starting<indexterm><primary>boot</primary></indexterm> and " 
    1284 "stopping<indexterm><primary>shutdown</primary></indexterm> the operating " 
    1285 "system, where it loads specified programs using their particular " 
    1286 "configurations, permits you to change those configurations to control the " 
    1287 "boot process, and shuts down in a graceful and organized way." 
    1288 msgstr "" 
     1117msgid "One of the most powerful aspects of Linux concerns its open method of starting<indexterm><primary>boot</primary></indexterm> and stopping<indexterm><primary>shutdown</primary></indexterm> the operating system, where it loads specified programs using their particular configurations, permits you to change those configurations to control the boot process, and shuts down in a graceful and organized way." 
     1118msgstr "Um dos aspectos mais poderosos do Linux é a respeito dos seus métodos abertos de inicialização  <indexterm><primary>inicialização</primary></indexterm> e desligamento <indexterm><primary>desligamento</primary></indexterm> do sistema operacional, onde são carregados programas específicos com suas configurações particulares, que permitem mudar estas configurações para controlar o processo de inicialização, e também desligar de uma forma organizada e graciosa." 
    12891119 
    12901120#: ../chap4.xml:353(para) 
    1291 msgid "" 
    1292 "Beyond the question of controlling the boot or shutdown process, the open " 
    1293 "nature of Linux makes it much easier to determine the exact source of most " 
    1294 "problems associated with starting up or shutting down your system. A basic " 
    1295 "understanding of this process is quite beneficial to everybody who uses a " 
    1296 "Linux system." 
    1297 msgstr "" 
     1121msgid "Beyond the question of controlling the boot or shutdown process, the open nature of Linux makes it much easier to determine the exact source of most problems associated with starting up or shutting down your system. A basic understanding of this process is quite beneficial to everybody who uses a Linux system." 
     1122msgstr "Além da questão de controlar o processo de inicialização ou desligamento, a natureza aberta do Linux torna bem mais fácil determinar a fonte exata de muitos problemas associados com a inicialização ou desligamento do seu sistema. Um entendimento básico desse processo é bastante benéfico para todos que usam um sistema Linux." 
    12981123 
    12991124#: ../chap4.xml:354(para) 
    1300 msgid "" 
    1301 "A lot of Linux systems use <command>lilo<indexterm><primary>boot</" 
    1302 "primary><secondary>LILO</secondary></indexterm></command>, the " 
    1303 "<application>LInux LOader<indexterm><primary>LILO</primary></indexterm></" 
    1304 "application> for booting operating systems. We will only discuss " 
    1305 "GRUB<indexterm><primary>boot</primary><secondary>GRUB</secondary></" 
    1306 "indexterm>, however, which is easier to use and more flexible. Should you " 
    1307 "need information about <command>lilo</command>, refer to the man pages and " 
    1308 "HOWTOs. Both systems support dual boot installations, we refer to the HOWTOs " 
    1309 "on this subject for practical examples and background information." 
    1310 msgstr "" 
     1125msgid "A lot of Linux systems use <command>lilo<indexterm><primary>boot</primary><secondary>LILO</secondary></indexterm></command>, the <application>LInux LOader<indexterm><primary>LILO</primary></indexterm></application> for booting operating systems. We will only discuss GRUB<indexterm><primary>boot</primary><secondary>GRUB</secondary></indexterm>, however, which is easier to use and more flexible. Should you need information about <command>lilo</command>, refer to the man pages and HOWTOs. Both systems support dual boot installations, we refer to the HOWTOs on this subject for practical examples and background information." 
     1126msgstr "Muitos sistemas Linux usam o <command>lilo<indexterm><primary>inicialização</primary><secondary>LILO</secondary></indexterm></command>, o <application>LInux LOader<indexterm><primary>LILO</primary></indexterm></application> para inicializar sistemas operacionais. Porém, iremos discutir apenas o GRUB<indexterm><primary>inicialização</primary><secondary>GRUB</secondary></indexterm>, que é mais flexível e fácil de usar. Caso necessite de informações sobre o <command>lilo</command>, consulte as páginas de manuais e guias. Ambos sistemas suportam instalações duplas de sistemas operacionais na mesma máquina. Nesse assunto, confiamos os exemplos práticos e informações complementares à outros guias." 
    13111127 
    13121128#: ../chap4.xml:356(title) 
    13131129msgid "The boot process" 
    1314 msgstr "" 
     1130msgstr "O processo de inicialização" 
    13151131 
    13161132#: ../chap4.xml:357(para) 
    1317 msgid "" 
    1318 "When an x86 computer is booted, the processor looks at the end of the system " 
    1319 "memory for the BIOS<indexterm><primary>boot</primary><secondary>BIOS</" 
    1320 "secondary></indexterm> (Basic Input/Output System<indexterm><primary>BIOS</" 
    1321 "primary></indexterm>) and runs it. The BIOS program is written into " 
    1322 "permanent read-only memory and is always available for use. The BIOS " 
    1323 "provides the lowest level interface to peripheral devices and controls the " 
    1324 "first step of the boot process." 
    1325 msgstr "" 
     1133msgid "When an x86 computer is booted, the processor looks at the end of the system memory for the BIOS<indexterm><primary>boot</primary><secondary>BIOS</secondary></indexterm> (Basic Input/Output System<indexterm><primary>BIOS</primary></indexterm>) and runs it. The BIOS program is written into permanent read-only memory and is always available for use. The BIOS provides the lowest level interface to peripheral devices and controls the first step of the boot process." 
     1134msgstr "Quando um computador x86 é inicializado, o processador busca pelo BIOS no final da memória do sistema<indexterm><primary>inicialização</primary><secondary>BIOS</secondary></indexterm> (Basic Input/Output System<indexterm><primary>BIOS</primary></indexterm> - Sistema Básico de Entrada e Saída) e o executa. O programa BIOS é escrito em memória permanente de apenas leitura e está sempre disponível para uso. O BIOS provê a interface de menor nível para os dispositivos periféricos e controla o primeiro passo no processo de inicialização." 
    13261135 
    13271136#: ../chap4.xml:358(para) 
    1328 msgid "" 
    1329 "The BIOS tests the system, looks for and checks peripherals, and then looks " 
    1330 "for a drive to use to boot the system. Usually it checks the floppy drive " 
    1331 "(or CD-ROM drive on many newer systems) for bootable media, if present, and " 
    1332 "then it looks to the hard drive. The order of the drives used for booting is " 
    1333 "usually controlled by a particular BIOS setting on the system. Once Linux is " 
    1334 "installed on the hard drive of a system, the BIOS looks for a Master Boot " 
    1335 "Record<indexterm><primary>MBR</primary></indexterm> (MBR) starting at the " 
    1336 "first sector on the first hard drive, loads its contents into memory, then " 
    1337 "passes control to it." 
    1338 msgstr "" 
     1137msgid "The BIOS tests the system, looks for and checks peripherals, and then looks for a drive to use to boot the system. Usually it checks the floppy drive (or CD-ROM drive on many newer systems) for bootable media, if present, and then it looks to the hard drive. The order of the drives used for booting is usually controlled by a particular BIOS setting on the system. Once Linux is installed on the hard drive of a system, the BIOS looks for a Master Boot Record<indexterm><primary>MBR</primary></indexterm> (MBR) starting at the first sector on the first hard drive, loads its contents into memory, then passes control to it." 
     1138msgstr "O BIOS testa o sistema, procura e verifica periféricos, e então procura por um drive para usar na inicialização do sistema. Geralmente verifica drive de disquete (ou drive de CD-ROM em muitos sistemas mais novos) em busca de mídia inicializável, quando presentes, e então verifica o disco rígido. A ordem dos drives usados para inicialização é geralmente controlada por uma configuração particular no BIOS do sistema. Uma vez que o Linux estiver instalado no disco rígido de um sistema, o BIOS procura um MBR (Master Boot Record - registro mestre de inicialização) <indexterm><primary>MBR</primary></indexterm> iniciando no primeiro setor do primeiro disco rígido, carrega seu conteúdo na memória, e então passa o controle para ele." 
    13391139 
    13401140#: ../chap4.xml:359(para) 
    1341 msgid "" 
    1342 "This MBR<indexterm><primary>boot</primary><secondary>MBR</secondary></" 
    1343 "indexterm> contains instructions on how to load the " 
    1344 "GRUB<indexterm><primary>GRUB</primary><secondary/></indexterm> (or LILO) " 
    1345 "boot-loader, using a pre-selected operating system. The MBR then loads the " 
    1346 "boot-loader<indexterm><primary>boot</primary><secondary>boot-loader</" 
    1347 "secondary></indexterm>, which takes over the process (if the boot-loader is " 
    1348 "installed in the MBR). In the default Red Hat Linux configuration, GRUB uses " 
    1349 "the settings in the MBR to display boot options in a menu. Once GRUB has " 
    1350 "received the correct instructions for the operating system to start, either " 
    1351 "from its command line or configuration file, it finds the necessary boot " 
    1352 "file and hands off control of the machine to that operating system." 
    1353 msgstr "" 
     1141msgid "This MBR<indexterm><primary>boot</primary><secondary>MBR</secondary></indexterm> contains instructions on how to load the GRUB<indexterm><primary>GRUB</primary><secondary/></indexterm> (or LILO) boot-loader, using a pre-selected operating system. The MBR then loads the boot-loader<indexterm><primary>boot</primary><secondary>boot-loader</secondary></indexterm>, which takes over the process (if the boot-loader is installed in the MBR). In the default Red Hat Linux configuration, GRUB uses the settings in the MBR to display boot options in a menu. Once GRUB has received the correct instructions for the operating system to start, either from its command line or configuration file, it finds the necessary boot file and hands off control of the machine to that operating system." 
     1142msgstr "Esse MBR<indexterm><primary>inicialização</primary><secondary>MBR</secondary></indexterm> contém instruções sobre como iniciar o carregador de inicialização GRUB<indexterm><primary>GRUB</primary><secondary/></indexterm> (ou LILO), com um sistema operacional pré-selecionado. O MBR inicia o carregador de inicialização<indexterm><primary>inicialização</primary><secondary>carregador de inicialização</secondary></indexterm>, o qual assume o processo (se o carregador de inicalização está instalado no MBR). Em uma configuração Linux Red Hat padrão, o GRUP utiliza as configurações contidas na MBR para exibir opções de inicialização em um menu. Uma vez que o GRUB tenha recebido instruções corretas para iniciar o sistema operacional, seja por linha de comando ou arquivo de configuração, ele encontra o arquivo de inicialização necessário e entrega o controle da máquina para o sistema operacional." 
    13541143 
    13551144#: ../chap4.xml:361(title) 
    13561145msgid "GRUB features" 
    1357 msgstr "" 
     1146msgstr "Recursos do GRUB" 
    13581147 
    13591148#: ../chap4.xml:362(para) 
    1360 msgid "" 
    1361 "This boot method is called <emphasis>direct loading<indexterm><primary>boot</" 
    1362 "primary><secondary>direct loading</secondary></indexterm></emphasis> because " 
    1363 "instructions are used to directly load the operating system, with no " 
    1364 "intermediary code between the boot-loaders and the operating system's main " 
    1365 "files (such as the kernel). The boot process used by other operating systems " 
    1366 "may differ slightly from the above, however. For example, Microsoft's DOS " 
    1367 "and Windows operating systems completely overwrite anything on the MBR when " 
    1368 "they are installed without incorporating any of the current MBR's " 
    1369 "configuration. This destroys any other information stored in the MBR by " 
    1370 "other operating systems, such as Linux. The Microsoft operating systems, as " 
    1371 "well as various other proprietary operating systems, are loaded using a " 
    1372 "chain loading boot method. With this method, the MBR points to the first " 
    1373 "sector of the partition holding the operating system, where it finds the " 
    1374 "special files necessary to actually boot that operating system." 
    1375 msgstr "" 
     1149msgid "This boot method is called <emphasis>direct loading<indexterm><primary>boot</primary><secondary>direct loading</secondary></indexterm></emphasis> because instructions are used to directly load the operating system, with no intermediary code between the boot-loaders and the operating system's main files (such as the kernel). The boot process used by other operating systems may differ slightly from the above, however. For example, Microsoft's DOS and Windows operating systems completely overwrite anything on the MBR when they are installed without incorporating any of the current MBR's configuration. This destroys any other information stored in the MBR by other operating systems, such as Linux. The Microsoft operating systems, as well as various other proprietary operating systems, are loaded using a chain loading boot method. With this method, the MBR points to the first sector of the partition holding the operating system, where it finds the special files necessary to actually boot that operating system." 
     1150msgstr "Esse método de inicialização é chamado <emphasis>carregamento direto<indexterm><primary>inicialização</primary><secondary>carregamento direto</secondary></indexterm></emphasis> porque as instruções são usadas para carregar o sistema operacional diretamente, sem nenhum código intermediário entre os carregadores de inicialização e os arquivos principais do sistema operacional (como o kernel). Porém, o processo de inicialização de outros sistemas operacionais podem diferir ligeiramente do descrito acima. Por exemplo, os sistestemas operacionais DOS e Windows, da Microsoft, sobrescrevem completamente qualquer coisa na MBR quando são instalados, sem considerar a configuração presente na MBR no momento. Isso destrói qualquer outra informação armazenada na MBR por outros sistemas oparacionais, como Linux. Os sistemas operacionais da Microsoft, assim como vários outros sistemas operacionais proprietários, são carregados usando um método de carregamento de inicialização em corrente. Com esse método, o MBR aponta para o primeiro setor da partição que contém o sistema operacional, onde encontra os arquivos especiais necessários para realmente inicializar aquele sistema operacional" 
    13761151 
    13771152#: ../chap4.xml:363(para) 
    1378 msgid "" 
    1379 "GRUB<indexterm><primary>GRUB</primary><secondary>features</secondary></" 
    1380 "indexterm> supports both boot methods, allowing you to use it with almost " 
    1381 "any operating system, most popular file systems, and almost any hard disk " 
    1382 "your BIOS can recognize." 
    1383 msgstr "" 
     1153msgid "GRUB<indexterm><primary>GRUB</primary><secondary>features</secondary></indexterm> supports both boot methods, allowing you to use it with almost any operating system, most popular file systems, and almost any hard disk your BIOS can recognize." 
     1154msgstr "O GRUB<indexterm><primary>GRUB</primary><secondary>features</secondary></indexterm> funciona com os dois métodos, permitindo você usá-lo com quase qualquer sistema operacional, com grande parte dos sistemas de arquivos mais importantes, e com quase qualquer disco rígido que seu BIOS possa reconhecer." 
    13841155 
    13851156#: ../chap4.xml:365(para) 
    13861157msgid "GRUB contains a number of other features; the most important include:" 
    1387 msgstr "" 
     1158msgstr "O GRUB tem vários outros recursos; os mais importantes incluem:" 
    13881159 
    13891160#: ../chap4.xml:367(para) 
    1390 msgid "" 
    1391 "GRUB provides a true command-based, pre-OS environment on x86 machines to " 
    1392 "allow maximum flexibility in loading operating systems with certain options " 
    1393 "or gathering information about the system." 
    1394 msgstr "" 
     1161msgid "GRUB provides a true command-based, pre-OS environment on x86 machines to allow maximum flexibility in loading operating systems with certain options or gathering information about the system." 
     1162msgstr "O GRUB oferece um verdadeiro ambiente de comando pré sistema operacional em máquinas x86 que permite máxima flexibilidade ao carregar sistemas operacionais com certas opções, ou reunir informações sobre o sistema." 
    13951163 
    13961164#: ../chap4.xml:368(para) 
    1397 msgid "" 
    1398 "GRUB supports Logical Block Addressing (LBA<indexterm><primary>LBA</" 
    1399 "primary></indexterm>) mode, needed to access many IDE and all SCSI hard " 
    1400 "disks. Before LBA, hard drives could encounter a 1024-cylinder limit, where " 
    1401 "the BIOS could not find a file after that point." 
    1402 msgstr "" 
     1165msgid "GRUB supports Logical Block Addressing (LBA<indexterm><primary>LBA</primary></indexterm>) mode, needed to access many IDE and all SCSI hard disks. Before LBA, hard drives could encounter a 1024-cylinder limit, where the BIOS could not find a file after that point." 
     1166msgstr "GRUB aceita modo LBA  (Logical Block Addressing - endereçamento lógico de blocos) (LBA<indexterm><primary>LBA</primary></indexterm>), necessário para acessar alguns discos IDE e quaisquer discos SCSI. Antes do LBA, discos rígidos tinham um limite de 1024 cilindros, no qual o BIOS não seria capaz de encontrar um arquivo após esse limite." 
    14031167 
    14041168#: ../chap4.xml:369(para) 
    1405 msgid "" 
    1406 "GRUB's configuration file is read from the disk every time the system boots, " 
    1407 "preventing you from having to write over the MBR every time you change the " 
    1408 "boot options." 
    1409 msgstr "" 
     1169msgid "GRUB's configuration file is read from the disk every time the system boots, preventing you from having to write over the MBR every time you change the boot options." 
     1170msgstr "O arquivo de configuração do GRUB é lido do disco toda vez que o sistema inicializa, fazendo com que você não precise escrever no MBR toda vez que você muda as opções de BOOT." 
    14101171 
    14111172#: ../chap4.xml:371(para) 
    1412 msgid "" 
    1413 "A full description of GRUB may be found by issuing the <command>info " 
    1414 "<parameter>grub</parameter></command> command or at <ulink url=\"http://www." 
    1415 "gnu.org/software/grub/\">the GRUB site</ulink>. The Linux Documentation " 
    1416 "Project has a <ulink url=\"http://www.tldp.org/HOWTO/mini/Multiboot-with-" 
    1417 "GRUB.html\">Multiboot with GRUB Mini-HOWTO</ulink>." 
    1418 msgstr "" 
     1173msgid "A full description of GRUB may be found by issuing the <command>info <parameter>grub</parameter></command> command or at <ulink url=\"http://www.gnu.org/software/grub/\">the GRUB site</ulink>. The Linux Documentation Project has a <ulink url=\"http://www.tldp.org/HOWTO/mini/Multiboot-with-GRUB.html\">Multiboot with GRUB Mini-HOWTO</ulink>." 
     1174msgstr "Uma descrição completa do GRUB pode ser acessada pelo comando <command>info <parameter>grub</parameter></command> ou no <ulink url=\"http://www.gnu.org/software/grub/\">site do GRUB</ulink>. O Projeto de Documentação do Linux tem um <ulink url=\"http://www.tldp.org/HOWTO/mini/Multiboot-with-GRUB.html\">mini-guia de inicialização com GRUB em máquinas com mais de um sistema oparacional instalado</ulink>." 
    14191175 
    14201176#: ../chap4.xml:373(title) 
    14211177msgid "Init" 
    1422 msgstr "" 
     1178msgstr "Init" 
    14231179 
    14241180#: ../chap4.xml:374(para) 
    1425 msgid "" 
    1426 "The kernel, once it is loaded, finds <command>init<indexterm><primary>boot</" 
    1427 "primary><secondary>init</secondary></indexterm></command> in <filename>sbin</" 
    1428 "filename> and executes<indexterm><primary>init</primary></indexterm> it." 
    1429 msgstr "" 
     1181msgid "The kernel, once it is loaded, finds <command>init<indexterm><primary>boot</primary><secondary>init</secondary></indexterm></command> in <filename>sbin</filename> and executes<indexterm><primary>init</primary></indexterm> it." 
     1182msgstr "O kernel, uma vez carregado, encontra o programa <command>init<indexterm><primary>inicialização</primary><secondary>init</secondary></indexterm></command> no diretório <filename>sbin</filename> e o executa<indexterm><primary>init</primary></indexterm>." 
    14301183 
    14311184#: ../chap4.xml:375(para) 
    1432 msgid "" 
    1433 "When <command>init</command> starts, it becomes the parent or grandparent of " 
    1434 "all of the processes that start up automatically on your Linux system. The " 
    1435 "first thing <command>init</command> does, is reading its initialization " 
    1436 "file, <filename>/etc/inittab<indexterm><primary>inittab</primary></" 
    1437 "indexterm></filename>. This instructs <command>init</command> to read an " 
    1438 "initial configuration script for the environment, which sets the path, " 
    1439 "starts swapping, checks the file systems, and so on. Basically, this step " 
    1440 "takes care of everything that your system needs to have done at system " 
    1441 "initialization: setting the clock, initializing serial ports and so forth." 
    1442 msgstr "" 
     1185msgid "When <command>init</command> starts, it becomes the parent or grandparent of all of the processes that start up automatically on your Linux system. The first thing <command>init</command> does, is reading its initialization file, <filename>/etc/inittab<indexterm><primary>inittab</primary></indexterm></filename>. This instructs <command>init</command> to read an initial configuration script for the environment, which sets the path, starts swapping, checks the file systems, and so on. Basically, this step takes care of everything that your system needs to have done at system initialization: setting the clock, initializing serial ports and so forth." 
     1186msgstr "Quando o <command>init</command> inicia, ele se torna o pai ou avÃŽ de todos os processos que iniciam automaticamente no seu sistema Linux. A primeira coisa que o <command>init</command> faz é ler seu arquivo de inicialização, <filename>/etc/inittab<indexterm><primary>inittab</primary></indexterm></filename>. Isso instrui o <command>init</command> a ler um script de configuração inicial do ambiente, que configura os caminhos de busca, inicia a memória virtual, verifica os sistemas de arquivos, e por aí vai. Basicamente, esse passo cuida de tudo que seu sistema precisa que seja feito durante a sua inicialização: configura o relógio, incializa portas seriais e adiante." 
    14431187 
    14441188#: ../chap4.xml:376(para) 
    1445 msgid "" 
    1446 "Then <command>init</command> continues to read the <filename>/etc/inittab</" 
    1447 "filename> file, which describes how the system should be set up in each run " 
    1448 "level and sets the default <emphasis>run level<indexterm><primary>run level</" 
    1449 "primary></indexterm></emphasis>. A run level is a configuration of " 
    1450 "processes. All UNIX-like systems can be run in different process " 
    1451 "configurations, such as the single user mode<indexterm><primary>single user " 
    1452 "mode</primary></indexterm>, which is referred to as run level 1 or run level " 
    1453 "S (or s). In this mode, only the system administrator can connect to the " 
    1454 "system. It is used to perform maintenance tasks without risks of damaging " 
    1455 "the system or user data. Naturally, in this configuration we don't need to " 
    1456 "offer user services, so they will all be disabled. Another run level is the " 
    1457 "reboot run level, or run level 6, which shuts down all running services " 
    1458 "according to the appropriate procedures and then restarts the system." 
    1459 msgstr "" 
     1189msgid "Then <command>init</command> continues to read the <filename>/etc/inittab</filename> file, which describes how the system should be set up in each run level and sets the default <emphasis>run level<indexterm><primary>run level</primary></indexterm></emphasis>. A run level is a configuration of processes. All UNIX-like systems can be run in different process configurations, such as the single user mode<indexterm><primary>single user mode</primary></indexterm>, which is referred to as run level 1 or run level S (or s). In this mode, only the system administrator can connect to the system. It is used to perform maintenance tasks without risks of damaging the system or user data. Naturally, in this configuration we don't need to offer user services, so they will all be disabled. Another run level is the reboot run level, or run level 6, which shuts down all running services according to the appropriate procedures and then restarts the system." 
     1190msgstr "Quando o <command>init</command> segue lendo o arquivo <filename>/etc/inittab</filename>, que descreve como o sistema deve ser configurado em cada nível de execução qual o <emphasis>nível de execução<indexterm><primary>nível de execução</primary></indexterm></emphasis> padrão. Um nível de execução é uma configuração de processo. Todos os sistemas do tipo UNIX podem operar em diferentes configurações de processo, tais como o modo com um único usuário<indexterm><primary>modo com um único usuário</primary></indexterm>, o qual é chamado nível de execução 1 ou nível de execução S (ou s). Nesso modo, apenas o administrador do sistema pode acessar o sistema. É usado para realizar tarefas de manutenção, sem o risco de danificar dados do sistema ou de usuários. Naturalmente, nessa configuração nós não precisamos oferecer serviços aos usuários, então, eles são todos desabilitados. Outro nível de execução é o de reinicialização, ou nível de execução 6, que desliga todos os serviços em execução de acordo com os procedimentos apropriados e então reinicia o sistema." 
    14601191 
    14611192#: ../chap4.xml:377(para) 
    1462 msgid "" 
    1463 "Use the <command>who<indexterm><primary>run level</" 
    1464 "primary><secondary>display</secondary></indexterm></command> to check what " 
    1465 "your current<indexterm><primary>who</primary></indexterm> run level is:" 
    1466 msgstr "" 
     1193msgid "Use the <command>who<indexterm><primary>run level</primary><secondary>display</secondary></indexterm></command> to check what your current<indexterm><primary>who</primary></indexterm> run level is:" 
     1194msgstr "Use o comando <command>who<indexterm><primary>nível de execução</primary><secondary>exibir</secondary></indexterm></command> para verificar qual o seu <indexterm><primary>who</primary></indexterm> nível de execução atual:" 
    14671195 
    14681196#: ../chap4.xml:379(prompt) 
    14691197msgid "willy@ubuntu:~$" 
    1470 msgstr "" 
     1198msgstr "willy@ubuntu:~$" 
    14711199 
    14721200#: ../chap4.xml:379(option) 
    14731201msgid "-r" 
    1474 msgstr "" 
     1202msgstr "-r" 
    14751203 
    14761204#: ../chap4.xml:379(command) 
    14771205msgid "who <placeholder-1/>" 
    1478 msgstr "" 
     1206msgstr "who <placeholder-1/>" 
    14791207 
    14801208#: ../chap4.xml:378(screen) 
    1481 #, no-wrap 
     1209#, fuzzy, no-wrap 
    14821210msgid "" 
    14831211"\n" 
    … …  
    14851213"\trun-level 2 2006-10-17 23:22\t\tlast=S\n" 
    14861214msgstr "" 
     1215"\n" 
     1216"<placeholder-1/><placeholder-2/>\n" 
     1217"\tnivel de execução 2 2006-10-17 23:22\t\tlast=S\n" 
    14871218 
    14881219#: ../chap4.xml:383(para) 
    1489 msgid "" 
    1490 "More about run levels in the next section, see <xref linkend=\"sect_04_02_05" 
    1491 "\"/>." 
    1492 msgstr "" 
     1220msgid "More about run levels in the next section, see <xref linkend=\"sect_04_02_05\"/>." 
     1221msgstr "Mais a respeito de níveis de execução na próxima sessão, veja <xref linkend=\"sect_04_02_05\"/>." 
    14931222 
    14941223#: ../chap4.xml:384(para) 
    1495 msgid "" 
    1496 "After having determined the default run level for your system, " 
    1497 "<command>init</command> starts all of the background processes necessary for " 
    1498 "the system to run by looking in the appropriate <filename>rc</filename> " 
    1499 "directory<indexterm><primary>run level</primary><secondary>rc files</" 
    1500 "secondary></indexterm> for that run level. <command>init</command> runs each " 
    1501 "of the kill<indexterm><primary>init</primary><secondary>kill scripts</" 
    1502 "secondary></indexterm> scripts (their file names start with a K) with a stop " 
    1503 "parameter. It then runs all of the start<indexterm><primary>init</" 
    1504 "primary><secondary>start scripts</secondary></indexterm> scripts (their file " 
    1505 "names start with an S) in the appropriate run level directory so that all " 
    1506 "services and applications are started correctly. In fact, you can execute " 
    1507 "these same scripts manually after the system is finished booting with a " 
    1508 "command like <command>/etc/init.d/httpd <parameter>stop</parameter></" 
    1509 "command> or <command>service <parameter>httpd</parameter><parameter>stop</" 
    1510 "parameter></command> logged in as <emphasis>root</emphasis>, in this case " 
    1511 "stopping the web server." 
     1224msgid "After having determined the default run level for your system, <command>init</command> starts all of the background processes necessary for the system to run by looking in the appropriate <filename>rc</filename> directory<indexterm><primary>run level</primary><secondary>rc files</secondary></indexterm> for that run level. <command>init</command> runs each of the kill<indexterm><primary>init</primary><secondary>kill scripts</secondary></indexterm> scripts (their file names start with a K) with a stop parameter. It then runs all of the start<indexterm><primary>init</primary><secondary>start scripts</secondary></indexterm> scripts (their file names start with an S) in the appropriate run level directory so that all services and applications are started correctly. In fact, you can execute these same scripts manually after the system is finished booting with a command like <command>/etc/init.d/httpd <parameter>stop</parameter></command> or <command>service <parameter>httpd</parameter><parameter>stop</parameter></command> logged in as <emphasis>root</emphasis>, in this case stopping the web server." 
    15121225msgstr "" 
    15131226 
    15141227#: ../chap4.xml:385(title) 
    15151228msgid "Special case" 
    1516 msgstr "" 
     1229msgstr "Caso especial" 
    15171230 
    15181231#: ../chap4.xml:386(para) 
    1519 msgid "" 
    1520 "Note that on system startup, the scripts in <filename>rc2.d</filename> and " 
    1521 "<filename>rc3.d</filename> are usually executed. In that case, no services " 
    1522 "are stopped (at least not permanently). There are only services that are " 
    1523 "started." 
     1232msgid "Note that on system startup, the scripts in <filename>rc2.d</filename> and <filename>rc3.d</filename> are usually executed. In that case, no services are stopped (at least not permanently). There are only services that are started." 
    15241233msgstr "" 
    15251234 
    15261235#: ../chap4.xml:388(para) 
    1527 msgid "" 
    1528 "None of the scripts<indexterm><primary>processes</primary><secondary>init " 
    1529 "scripts</secondary></indexterm> that actually start and stop the services " 
    1530 "are located<indexterm><primary>rc*.d</primary></indexterm> in <filename>/etc/" 
    1531 "rc&lt;x&gt;.d</filename>. Rather, all of the files in <filename>/etc/rc&lt;" 
    1532 "x&gt;.d</filename> are symbolic links that point to the actual scripts " 
    1533 "located in <filename>/etc/init.d</filename>. A symbolic link is nothing more " 
    1534 "than a file that points to another file, and is used in this case because it " 
    1535 "can be created and deleted without affecting the actual scripts that kill or " 
    1536 "start the services. The symbolic links to the various scripts are numbered " 
    1537 "in a particular order so that they start in that order. You can change the " 
    1538 "order in which the services start up or are killed by changing the name of " 
    1539 "the symbolic link that refers to the script that actually controls the " 
    1540 "service. You can use the same number multiple times if you want a particular " 
    1541 "service started or stopped right before or after another service, as in the " 
    1542 "example below, listing the content of <filename>/etc/rc5.d</filename>, where " 
    1543 "<command>crond</command> and <command>xfs</command> are both started from a " 
    1544 "linkname starting with <quote>S90</quote>. In this case, the scripts are " 
    1545 "started in alphabetical order." 
     1236msgid "None of the scripts<indexterm><primary>processes</primary><secondary>init scripts</secondary></indexterm> that actually start and stop the services are located<indexterm><primary>rc*.d</primary></indexterm> in <filename>/etc/rc&lt;x&gt;.d</filename>. Rather, all of the files in <filename>/etc/rc&lt;x&gt;.d</filename> are symbolic links that point to the actual scripts located in <filename>/etc/init.d</filename>. A symbolic link is nothing more than a file that points to another file, and is used in this case because it can be created and deleted without affecting the actual scripts that kill or start the services. The symbolic links to the various scripts are numbered in a particular order so that they start in that order. You can change the order in which the services start up or are killed by changing the name of the symbolic link that refers to the script that actually controls the service. You can use the same number multiple times if you want a particular service started or stopped right before or after another service, as in the example below, listing the content of <filename>/etc/rc5.d</filename>, where <command>crond</command> and <command>xfs</command> are both started from a linkname starting with <quote>S90</quote>. In this case, the scripts are started in alphabetical order." 
    15461237msgstr "" 
    15471238 
    15481239#: ../chap4.xml:391(prompt) 
    15491240msgid "[jean@blub /etc/rc5.d]" 
    1550 msgstr "" 
     1241msgstr "[jean@blub /etc/rc5.d]" 
    15511242 
    15521243#: ../chap4.xml:391(command) 
    15531244msgid "ls" 
    1554 msgstr "" 
     1245msgstr "ls" 
    15551246 
    15561247#: ../chap4.xml:390(screen) 
    … …  
    15691260"K34yppasswdd@  S05kudzu@    S20random@    S80sendmail@\n" 
    15701261msgstr "" 
     1262"\n" 
     1263"<placeholder-1/> <placeholder-2/>\n" 
     1264"K15httpd@     K45named@    S08ipchains@  S25netfs@      S85gpm@\n" 
     1265"K16rarpd@     K46radvd@    S08iptables@  S26apmd@       S90crond@\n" 
     1266"K20nfs@       K61ldap@     S09isdn@      S28autofs@     S90xfs@\n" 
     1267"K20rstatd@    K65identd@   S10network@   S30nscd@       S95anacron@\n" 
     1268"K20rusersd@   K74ntpd@     S12syslog@    S55sshd@       S95atd@\n" 
     1269"K20rwalld@    K74ypserv@   S13portmap@   S56rawdevices@ S97rhnsd@\n" 
     1270"K20rwhod@     K74ypxfrd@   S14nfslock@   S56xinetd@     S99local@\n" 
     1271"K25squid@     K89bcm5820@  S17keytable@  S60lpd@\n" 
     1272"K34yppasswdd@  S05kudzu@    S20random@    S80sendmail@\n" 
    15711273 
    15721274#: ../chap4.xml:402(para) 
    1573 msgid "" 
    1574 "After <command>init</command> has progressed through the run levels to get " 
    1575 "to the default run level, the <filename>/etc/inittab</filename> script forks " 
    1576 "a <command>getty<indexterm><primary>getty</primary></indexterm></command> " 
    1577 "process for each virtual console (login prompt in text mode). " 
    1578 "<command>getty</command> opens tty lines, sets their modes, prints the login " 
    1579 "prompt, gets the user's name, and then initiates a login process for that " 
    1580 "user. This allows users to authenticate themselves to the system and use it. " 
    1581 "By default, most systems offer 6 virtual consoles, but as you can see from " 
    1582 "the <filename>inittab</filename> file, this is configurable." 
     1275msgid "After <command>init</command> has progressed through the run levels to get to the default run level, the <filename>/etc/inittab</filename> script forks a <command>getty<indexterm><primary>getty</primary></indexterm></command> process for each virtual console (login prompt in text mode). <command>getty</command> opens tty lines, sets their modes, prints the login prompt, gets the user's name, and then initiates a login process for that user. This allows users to authenticate themselves to the system and use it. By default, most systems offer 6 virtual consoles, but as you can see from the <filename>inittab</filename> file, this is configurable." 
    15831276msgstr "" 
    15841277 
    15851278#: ../chap4.xml:403(para) 
    1586 msgid "" 
    1587 "<filename>/etc/inittab</filename> can also tell <command>init</command> how " 
    1588 "it should handle a user pressing <keycap>Ctrl</keycap>+<keycap>Alt</keycap>" 
    1589 "+<keycap>Delete</keycap> at the console. As the system should be properly " 
    1590 "shut down and restarted rather than immediately power-cycled, <command>init</" 
    1591 "command> is told to execute<indexterm><primary>shutdown</primary></" 
    1592 "indexterm> the command <command>/sbin/shutdown <option>-t3 -r</" 
    1593 "option><parameter>now</parameter></command>, for instance, when a user hits " 
    1594 "those keys. In addition, <filename>/etc/inittab</filename> states what " 
    1595 "<command>init</command> should do in case of power failures, if your system " 
    1596 "has a UPS unit attached to it." 
     1279msgid "<filename>/etc/inittab</filename> can also tell <command>init</command> how it should handle a user pressing <keycap>Ctrl</keycap>+<keycap>Alt</keycap>+<keycap>Delete</keycap> at the console. As the system should be properly shut down and restarted rather than immediately power-cycled, <command>init</command> is told to execute<indexterm><primary>shutdown</primary></indexterm> the command <command>/sbin/shutdown <option>-t3 -r</option><parameter>now</parameter></command>, for instance, when a user hits those keys. In addition, <filename>/etc/inittab</filename> states what <command>init</command> should do in case of power failures, if your system has a UPS unit attached to it." 
    15971280msgstr "" 
    15981281 
    15991282#: ../chap4.xml:405(para) 
    1600 msgid "" 
    1601 "On most RPM-based systems the graphical login screen is started in run level " 
    1602 "5, where <filename>/etc/inittab</filename> runs a script called <filename>/" 
    1603 "etc/X11/prefdm<indexterm><primary>prefdm</primary></indexterm></filename>. " 
    1604 "The <filename>prefdm</filename> script runs the preferred X display manager, " 
    1605 "based on the contents of the <filename>/etc/sysconfig/desktop</filename> " 
    1606 "directory. This is typically <command>gdm<indexterm><primary>gdm</primary></" 
    1607 "indexterm></command> if you run GNOME or " 
    1608 "<command>kdm<indexterm><primary>kdm</primary></indexterm></command> if you " 
    1609 "run KDE, but they can be mixed, and there's also the <command>xdm</command> " 
    1610 "that comes with a standard X installation." 
     1283msgid "On most RPM-based systems the graphical login screen is started in run level 5, where <filename>/etc/inittab</filename> runs a script called <filename>/etc/X11/prefdm<indexterm><primary>prefdm</primary></indexterm></filename>. The <filename>prefdm</filename> script runs the preferred X display manager, based on the contents of the <filename>/etc/sysconfig/desktop</filename> directory. This is typically <command>gdm<indexterm><primary>gdm</primary></indexterm></command> if you run GNOME or <command>kdm<indexterm><primary>kdm</primary></indexterm></command> if you run KDE, but they can be mixed, and there's also the <command>xdm</command> that comes with a standard X installation." 
    16111284msgstr "" 
    16121285 
    16131286#: ../chap4.xml:407(para) 
    1614 msgid "" 
    1615 "But there are other possibilities as well. On Debian, for instance, there is " 
    1616 "an initscript for each of the display managers, and the content of the " 
    1617 "<filename>/etc/X11/default-display-manager</filename> is used to determine " 
    1618 "which one to start. More about the graphical interface can be read in <xref " 
    1619 "linkend=\"sect_07_03\"/>. Ultimately, your system documentation will explain " 
    1620 "the details about the higher level aspects of <command>init</command>." 
     1287msgid "But there are other possibilities as well. On Debian, for instance, there is an initscript for each of the display managers, and the content of the <filename>/etc/X11/default-display-manager</filename> is used to determine which one to start. More about the graphical interface can be read in <xref linkend=\"sect_07_03\"/>. Ultimately, your system documentation will explain the details about the higher level aspects of <command>init</command>." 
    16211288msgstr "" 
    16221289 
    16231290#: ../chap4.xml:408(para) 
    1624 msgid "" 
    1625 "The <filename>/etc/default<indexterm><primary>default</primary></indexterm></" 
    1626 "filename> and/or <filename>/etc/sysconfig<indexterm><primary>sysconfig</" 
    1627 "primary></indexterm></filename> directories contain entries for a range of " 
    1628 "functions and services, these are all read at boot time. The location of the " 
    1629 "directory containing system defaults might be somewhat different depending " 
    1630 "on your Linux distribution." 
     1291msgid "The <filename>/etc/default<indexterm><primary>default</primary></indexterm></filename> and/or <filename>/etc/sysconfig<indexterm><primary>sysconfig</primary></indexterm></filename> directories contain entries for a range of functions and services, these are all read at boot time. The location of the directory containing system defaults might be somewhat different depending on your Linux distribution." 
    16311292msgstr "" 
    16321293 
    16331294#: ../chap4.xml:409(para) 
    1634 msgid "" 
    1635 "Besides the graphical user environment, a lot of other services may be " 
    1636 "started as well. But if all goes well, you should be looking at a login " 
    1637 "prompt or login screen when the boot process has finished." 
     1295msgid "Besides the graphical user environment, a lot of other services may be started as well. But if all goes well, you should be looking at a login prompt or login screen when the boot process has finished." 
    16381296msgstr "" 
    16391297 
    16401298#: ../chap4.xml:411(title) 
    16411299msgid "Other procedures" 
    1642 msgstr "" 
     1300msgstr "Outros procedimentos" 
    16431301 
    16441302#: ../chap4.xml:412(para) 
    1645 msgid "" 
    1646 "We explained how SysV<indexterm><primary>init</primary><secondary>SysV/BSD</" 
    1647 "secondary></indexterm><command>init</command> works on x86 based machines. " 
    1648 "Startup procedures may vary on other architectures and distributions. Other " 
    1649 "systems may use the BSD-style <command>init</command>, where startup files " 
    1650 "are not split up into multiple <filename>/etc/rc&lt;LEVEL&gt;.d</filename> " 
    1651 "directories. It might also be possible that your system uses <filename>/etc/" 
    1652 "rc.d/init.d</filename> instead of <filename>/etc/init.d</filename>." 
     1303msgid "We explained how SysV<indexterm><primary>init</primary><secondary>SysV/BSD</secondary></indexterm><command>init</command> works on x86 based machines. Startup procedures may vary on other architectures and distributions. Other systems may use the BSD-style <command>init</command>, where startup files are not split up into multiple <filename>/etc/rc&lt;LEVEL&gt;.d</filename> directories. It might also be possible that your system uses <filename>/etc/rc.d/init.d</filename> instead of <filename>/etc/init.d</filename>." 
    16531304msgstr "" 
    16541305 
    16551306#: ../chap4.xml:414(title) 
    16561307msgid "Init run levels" 
    1657 msgstr "" 
     1308msgstr "Níveis de execução do init" 
    16581309 
    16591310#: ../chap4.xml:415(para) 
    1660 msgid "" 
    1661 "The idea behind operating different<indexterm><primary>init</" 
    1662 "primary><secondary>run levels</secondary></indexterm> services at different " 
    1663 "run levels essentially revolves around the fact that different systems can " 
    1664 "be used in different ways. Some services cannot be used until the system is " 
    1665 "in a particular state, or <emphasis>mode</emphasis>, such as being ready for " 
    1666 "more than one user or having networking available." 
     1311msgid "The idea behind operating different<indexterm><primary>init</primary><secondary>run levels</secondary></indexterm> services at different run levels essentially revolves around the fact that different systems can be used in different ways. Some services cannot be used until the system is in a particular state, or <emphasis>mode</emphasis>, such as being ready for more than one user or having networking available." 
    16671312msgstr "" 
    16681313 
    16691314#: ../chap4.xml:416(para) 
    1670 msgid "" 
    1671 "There are times in which you may want to operate the system in a lower mode. " 
    1672 "Examples are fixing disk corruption problems in run level 1 so no other " 
    1673 "users can possibly be on the system, or leaving a server in run level 3 " 
    1674 "without an X session running. In these cases, running services that depend " 
    1675 "upon a higher system mode to function does not make sense because they will " 
    1676 "not work correctly anyway. By already having each service assigned to start " 
    1677 "when its particular run level is reached, you ensure an orderly start up " 
    1678 "process, and you can quickly change the mode of the machine without worrying " 
    1679 "about which services to manually start or stop." 
     1315msgid "There are times in which you may want to operate the system in a lower mode. Examples are fixing disk corruption problems in run level 1 so no other users can possibly be on the system, or leaving a server in run level 3 without an X session running. In these cases, running services that depend upon a higher system mode to function does not make sense because they will not work correctly anyway. By already having each service assigned to start when its particular run level is reached, you ensure an orderly start up process, and you can quickly change the mode of the machine without worrying about which services to manually start or stop." 
    16801316msgstr "" 
    16811317 
    16821318#: ../chap4.xml:418(para) 
    1683 msgid "" 
    1684 "Available run levels are generally described in <filename>/etc/inittab</" 
    1685 "filename>, which is partially shown below:" 
     1319msgid "Available run levels are generally described in <filename>/etc/inittab</filename>, which is partially shown below:" 
    16861320msgstr "" 
    16871321 
    … …  
    17101344 
    17111345#: ../chap4.xml:439(para) 
    1712 msgid "" 
    1713 "Feel free to configure unused run levels (commonly run level 4) as you see " 
    1714 "fit. Many users configure those run levels in a way that makes the most " 
    1715 "sense for them while leaving the standard run levels as they are by default. " 
    1716 "This allows them to quickly move in and out of their custom configuration " 
    1717 "without disturbing the normal set of features at the standard run levels." 
     1346msgid "Feel free to configure unused run levels (commonly run level 4) as you see fit. Many users configure those run levels in a way that makes the most sense for them while leaving the standard run levels as they are by default. This allows them to quickly move in and out of their custom configuration without disturbing the normal set of features at the standard run levels." 
    17181347msgstr "" 
    17191348 
    17201349#: ../chap4.xml:440(para) 
    1721 msgid "" 
    1722 "If your machine gets into a state where it will not boot due to a bad " 
    1723 "<filename>/etc/inittab</filename> or will not let you log in because you " 
    1724 "have a corrupted <filename>/etc/passwd</filename> file (or if you have " 
    1725 "simply forgotten your password), boot into single-user mode." 
     1350msgid "If your machine gets into a state where it will not boot due to a bad <filename>/etc/inittab</filename> or will not let you log in because you have a corrupted <filename>/etc/passwd</filename> file (or if you have simply forgotten your password), boot into single-user mode." 
    17261351msgstr "" 
    17271352 
    17281353#: ../chap4.xml:441(title) 
    17291354msgid "No graphics?" 
    1730 msgstr "" 
     1355msgstr "Sem gráficos?" 
    17311356 
    17321357#: ../chap4.xml:442(para) 
    1733 msgid "" 
    1734 "When you are working in text mode because you didn't get presented a " 
    1735 "graphical login screen on the console of your machine, you can normally " 
    1736 "switch to console 7 or up to have a graphical login. If this is not the " 
    1737 "case, check the current run level using the command <command>who <option>-r</" 
    1738 "option></command>. If it is set to something else than the original default " 
    1739 "from <filename>/etc/inittab</filename>, chances are that the system does not " 
    1740 "start up in graphical mode by default. Contact your system administrator or " 
    1741 "read <command>man init</command> in that case. Note that switching run " 
    1742 "levels<indexterm><primary>run levels</primary><secondary>switching</" 
    1743 "secondary></indexterm> is done preferably using the " 
    1744 "<command>telinit<indexterm><primary>telinit</primary></indexterm></command> " 
    1745 "command; switching from a text to a graphical console or vice versa does not " 
    1746 "involve a run level switch." 
     1358msgid "When you are working in text mode because you didn't get presented a graphical login screen on the console of your machine, you can normally switch to console 7 or up to have a graphical login. If this is not the case, check the current run level using the command <command>who <option>-r</option></command>. If it is set to something else than the original default from <filename>/etc/inittab</filename>, chances are that the system does not start up in graphical mode by default. Contact your system administrator or read <command>man init</command> in that case. Note that switching run levels<indexterm><primary>run levels</primary><secondary>switching</secondary></indexterm> is done preferably using the <command>telinit<indexterm><primary>telinit</primary></indexterm></command> command; switching from a text to a graphical console or vice versa does not involve a run level switch." 
    17471359msgstr "" 
    17481360 
    17491361#: ../chap4.xml:444(para) 
    1750 msgid "" 
    1751 "The discussion of run levels, scripts and configurations in this guide tries " 
    1752 "to be as general as possible. Lots of variations exist. For instance, Gentoo " 
    1753 "Linux stores scripts in <filename>/etc/run levels</filename>. Other systems " 
    1754 "might first run through (a) lower run level(s) and execute all the scripts " 
    1755 "in there before arriving at the final run level and executing those scripts. " 
    1756 "Refer to your system documentation for more information. You might also read " 
    1757 "through the scripts that are refered to in <filename>/etc/inittab</filename> " 
    1758 "to get a better comprehension of what happens on your system." 
     1362msgid "The discussion of run levels, scripts and configurations in this guide tries to be as general as possible. Lots of variations exist. For instance, Gentoo Linux stores scripts in <filename>/etc/run levels</filename>. Other systems might first run through (a) lower run level(s) and execute all the scripts in there before arriving at the final run level and executing those scripts. Refer to your system documentation for more information. You might also read through the scripts that are refered to in <filename>/etc/inittab</filename> to get a better comprehension of what happens on your system." 
    17591363msgstr "" 
    17601364 
    17611365#: ../chap4.xml:446(title) 
    17621366msgid "Tools" 
    1763 msgstr "" 
     1367msgstr "Ferramentas" 
    17641368 
    17651369#: ../chap4.xml:447(para) 
    1766 msgid "" 
    1767 "The <command>chkconfig<indexterm><primary>chkconfig</primary></indexterm></" 
    1768 "command> or <command>update-rc.d<indexterm><primary>update-rc.d</primary></" 
    1769 "indexterm></command> utilities, when installed on your system, provide a " 
    1770 "simple command-line tool for maintaining the <filename>/etc/init." 
    1771 "d<indexterm><primary>init.d</primary></indexterm></filename> directory " 
    1772 "hierarchy. These relieve<indexterm><primary>init scripts</" 
    1773 "primary><secondary>administration</secondary></indexterm> system " 
    1774 "administrators from having to directly manipulate the numerous symbolic " 
    1775 "links in the directories under <filename>/etc/rc[x].d</filename>." 
     1370msgid "The <command>chkconfig<indexterm><primary>chkconfig</primary></indexterm></command> or <command>update-rc.d<indexterm><primary>update-rc.d</primary></indexterm></command> utilities, when installed on your system, provide a simple command-line tool for maintaining the <filename>/etc/init.d<indexterm><primary>init.d</primary></indexterm></filename> directory hierarchy. These relieve<indexterm><primary>init scripts</primary><secondary>administration</secondary></indexterm> system administrators from having to directly manipulate the numerous symbolic links in the directories under <filename>/etc/rc[x].d</filename>." 
    17761371msgstr "" 
    17771372 
    17781373#: ../chap4.xml:448(para) 
    1779 msgid "" 
    1780 "In addition, some systems offer the " 
    1781 "<command>ntsysv<indexterm><primary>ntsysv</primary></indexterm></command> " 
    1782 "tool, which provides a text-based interface; you may find this easier to use " 
    1783 "than <command>chkconfig</command>'s command-line interface. On SuSE Linux, " 
    1784 "you will find the <command>yast<indexterm><primary>yast</primary></" 
    1785 "indexterm></command> and <command>insserv<indexterm><primary>insserv</" 
    1786 "primary></indexterm></command> tools. For Mandrake easy configuration, you " 
    1787 "may want to try <application>DrakConf<indexterm><primary>DrakConf</primary></" 
    1788 "indexterm></application>, which allows among other features switching " 
    1789 "between run levels 3 and 5. In Mandriva this became the " 
    1790 "<application>Mandriva Linux Control Center</application>." 
     1374msgid "In addition, some systems offer the <command>ntsysv<indexterm><primary>ntsysv</primary></indexterm></command> tool, which provides a text-based interface; you may find this easier to use than <command>chkconfig</command>'s command-line interface. On SuSE Linux, you will find the <command>yast<indexterm><primary>yast</primary></indexterm></command> and <command>insserv<indexterm><primary>insserv</primary></indexterm></command> tools. For Mandrake easy configuration, you may want to try <application>DrakConf<indexterm><primary>DrakConf</primary></indexterm></application>, which allows among other features switching between run levels 3 and 5. In Mandriva this became the <application>Mandriva Linux Control Center</application>." 
    17911375msgstr "" 
    17921376 
    17931377#: ../chap4.xml:450(para) 
    1794 msgid "" 
    1795 "Most distributions provide a graphical user interface for configuring " 
    1796 "processes, check with your system documentation." 
     1378msgid "Most distributions provide a graphical user interface for configuring processes, check with your system documentation." 
    17971379msgstr "" 
    17981380 
    17991381#: ../chap4.xml:452(para) 
    1800 msgid "" 
    1801 "All of these utilities must be run as root. The system administrator may " 
    1802 "also manually create the appropriate links in each run level directory in " 
    1803 "order to start or stop a service in a certain run level." 
     1382msgid "All of these utilities must be run as root. The system administrator may also manually create the appropriate links in each run level directory in order to start or stop a service in a certain run level." 
    18041383msgstr "" 
    18051384 
    18061385#: ../chap4.xml:456(title) 
    18071386msgid "Shutdown" 
    1808 msgstr "" 
     1387msgstr "Desligamento" 
    18091388 
    18101389#: ../chap4.xml:457(para) 
    1811 msgid "" 
    1812 "UNIX was not made to be shut down, but if you really must, use the " 
    1813 "<command>shutdown<indexterm><primary>shutdown</primary></indexterm></" 
    1814 "command> command. After completing the shutdown procedure, the <option>-h</" 
    1815 "option> option will halt the system, while <option>-r</option> will " 
    1816 "reboot<indexterm><primary>reboot</primary></indexterm> it." 
     1390msgid "UNIX was not made to be shut down, but if you really must, use the <command>shutdown<indexterm><primary>shutdown</primary></indexterm></command> command. After completing the shutdown procedure, the <option>-h</option> option will halt the system, while <option>-r</option> will reboot<indexterm><primary>reboot</primary></indexterm> it." 
    18171391msgstr "" 
    18181392 
    18191393#: ../chap4.xml:458(para) 
    1820 msgid "" 
    1821 "The <command>reboot</command> and <command>halt<indexterm><primary>halt</" 
    1822 "primary></indexterm></command> commands are now able to invoke " 
    1823 "<command>shutdown</command> if run when the system is in run levels 1-5, and " 
    1824 "thus ensure proper shutdown of the system,but it is a bad habit to get into, " 
    1825 "as not all UNIX/Linux versions have this feature." 
     1394msgid "The <command>reboot</command> and <command>halt<indexterm><primary>halt</primary></indexterm></command> commands are now able to invoke <command>shutdown</command> if run when the system is in run levels 1-5, and thus ensure proper shutdown of the system,but it is a bad habit to get into, as not all UNIX/Linux versions have this feature." 
    18261395msgstr "" 
    18271396 
    18281397#: ../chap4.xml:459(para) 
    1829 msgid "" 
    1830 "If your computer does not power itself down, you should not turn off the " 
    1831 "computer until you see a message indicating that the system is halted or " 
    1832 "finished shutting down, in order to give the system the time to unmount all " 
    1833 "partitions. Being impatient may cause data loss." 
     1398msgid "If your computer does not power itself down, you should not turn off the computer until you see a message indicating that the system is halted or finished shutting down, in order to give the system the time to unmount all partitions. Being impatient may cause data loss." 
    18341399msgstr "" 
    18351400 
    18361401#: ../chap4.xml:464(title) 
    18371402msgid "Managing processes" 
    1838 msgstr "" 
     1403msgstr "Gerenciando processos" 
    18391404 
    18401405#: ../chap4.xml:465(title) 
    18411406msgid "Work for the system admin" 
    1842 msgstr "" 
     1407msgstr "Trabalho para o administrador do sistema" 
    18431408 
    18441409#: ../chap4.xml:466(para) 
    1845 msgid "" 
    1846 "While managing system resources<indexterm><primary>processes</" 
    1847 "primary><secondary>managing</secondary></indexterm>, including processes, is " 
    1848 "a task for the local system administrator, it doesn't hurt a common user to " 
    1849 "know something about it, especially where his or her own processes and their " 
    1850 "optimal execution are concerned." 
     1410msgid "While managing system resources<indexterm><primary>processes</primary><secondary>managing</secondary></indexterm>, including processes, is a task for the local system administrator, it doesn't hurt a common user to know something about it, especially where his or her own processes and their optimal execution are concerned." 
    18511411msgstr "" 
    18521412 
    18531413#: ../chap4.xml:467(para) 
    1854 msgid "" 
    1855 "We will explain a little bit on a theoretical level about system " 
    1856 "performance, though not as far as hardware optimization and other advanced " 
    1857 "procedures. Instead, we will study the daily problems a common user is " 
    1858 "confronted with, and actions such a user can take to optimally use the " 
    1859 "resources available. As we learn in the next section, this is mainly a " 
    1860 "matter of thinking before acting." 
     1414msgid "We will explain a little bit on a theoretical level about system performance, though not as far as hardware optimization and other advanced procedures. Instead, we will study the daily problems a common user is confronted with, and actions such a user can take to optimally use the resources available. As we learn in the next section, this is mainly a matter of thinking before acting." 
    18611415msgstr "" 
    18621416 
    18631417#: ../chap4.xml:468(title) 
    18641418msgid "Can't you go faster?" 
    1865 msgstr "" 
     1419msgstr "Você não pode ir mais rápido?" 
    18661420 
    18671421#: ../chap4.xml:477(phrase) 
    1868 msgid "" 
    1869 "Man-powered computer: one person works the pedals, one person works with the " 
    1870 "comp." 
     1422msgid "Man-powered computer: one person works the pedals, one person works with the comp." 
    18711423msgstr "" 
    18721424 
    18731425#: ../chap4.xml:484(title) 
    18741426msgid "How long does it take?" 
    1875 msgstr "" 
     1427msgstr "Quanto tempo leva?" 
    18761428 
    18771429#: ../chap4.xml:485(para) 
    1878 msgid "" 
    1879 "Bash offers a built-in <command>time<indexterm><primary>time</primary></" 
    1880 "indexterm></command> command that displays how long a command takes to " 
    1881 "execute. The timing<indexterm><primary>processes</primary><secondary>timing</" 
    1882 "secondary></indexterm> is highly accurate and can be used on any command. In " 
    1883 "the example below, it takes about a minute and a half to make this book:" 
    1884 msgstr "" 
    1885  
    1886 #: ../chap4.xml:489(prompt) ../chap4.xml:501(prompt) 
     1430msgid "Bash offers a built-in <command>time<indexterm><primary>time</primary></indexterm></command> command that displays how long a command takes to execute. The timing<indexterm><primary>processes</primary><secondary>timing</secondary></indexterm> is highly accurate and can be used on any command. In the example below, it takes about a minute and a half to make this book:" 
     1431msgstr "" 
     1432 
     1433#: ../chap4.xml:489(prompt) 
     1434#: ../chap4.xml:501(prompt) 
    18871435msgid "tilly:~/xml/src&gt;" 
    1888 msgstr "" 
     1436msgstr "tilly:~/xml/src&gt;" 
    18891437 
    18901438#: ../chap4.xml:489(command) 
    18911439msgid "time make" 
    1892 msgstr "" 
     1440msgstr "time make" 
    18931441 
    18941442#: ../chap4.xml:488(screen) 
    … …  
    19061454 
    19071455#: ../chap4.xml:498(para) 
    1908 msgid "" 
    1909 "The GNU <command>time</command> command in <filename>/usr/bin</filename> (as " 
    1910 "opposed to the shell built-in version) displays more information that can be " 
    1911 "formatted in different ways. It also shows the exit status of the command, " 
    1912 "and the total elapsed time. The same command as the above using the " 
    1913 "independent <command>time</command> gives this output:" 
     1456msgid "The GNU <command>time</command> command in <filename>/usr/bin</filename> (as opposed to the shell built-in version) displays more information that can be formatted in different ways. It also shows the exit status of the command, and the total elapsed time. The same command as the above using the independent <command>time</command> gives this output:" 
    19141457msgstr "" 
    19151458 
    19161459#: ../chap4.xml:501(command) 
    19171460msgid "/usr/bin/time make" 
    1918 msgstr "" 
     1461msgstr "/usr/bin/time make" 
    19191462 
    19201463#: ../chap4.xml:500(screen) 
    … …  
    19341477#: ../chap4.xml:510(para) 
    19351478msgid "Refer again to the Info pages for all the information." 
    1936 msgstr "" 
     1479msgstr "Consulte novamente as páginas Info para acessar toda a informação." 
    19371480 
    19381481#: ../chap4.xml:513(title) 
    19391482msgid "Performance" 
    1940 msgstr "" 
     1483msgstr "Performance" 
    19411484 
    19421485#: ../chap4.xml:514(para) 
    1943 msgid "" 
    1944 "To a user, performance<indexterm><primary>system</" 
    1945 "primary><secondary>performance</secondary></indexterm> means quick execution " 
    1946 "of commands. To a system manager, on the other hand, it means much more: the " 
    1947 "system admin has to optimize system " 
    1948 "performance<indexterm><primary>performance</primary></indexterm> for the " 
    1949 "whole system, including users, all programs and daemons. System performance " 
    1950 "can depend on a thousand tiny things which are not accounted for with the " 
    1951 "<command>time</command> command:" 
     1486msgid "To a user, performance<indexterm><primary>system</primary><secondary>performance</secondary></indexterm> means quick execution of commands. To a system manager, on the other hand, it means much more: the system admin has to optimize system performance<indexterm><primary>performance</primary></indexterm> for the whole system, including users, all programs and daemons. System performance can depend on a thousand tiny things which are not accounted for with the <command>time</command> command:" 
    19521487msgstr "" 
    19531488 
    19541489#: ../chap4.xml:516(para) 
    1955 msgid "" 
    1956 "the program executing is badly written or doesn't use the computer " 
    1957 "appropriately" 
     1490msgid "the program executing is badly written or doesn't use the computer appropriately" 
    19581491msgstr "" 
    19591492 
    … …  
    19671500 
    19681501#: ../chap4.xml:519(para) 
    1969 msgid "" 
    1970 "amount of users on the system, amount of users actually working " 
    1971 "simultaneously" 
     1502msgid "amount of users on the system, amount of users actually working simultaneously" 
    19721503msgstr "" 
    19731504 
    … …  
    19851516 
    19861517#: ../chap4.xml:525(para) 
    1987 msgid "" 
    1988 "In short: the load<indexterm><primary>system</primary><secondary>load</" 
    1989 "secondary></indexterm> depends on what is normal<indexterm><primary>load</" 
    1990 "primary></indexterm> for your system. My old P133 running a firewall, SSH " 
    1991 "server, file server, a route daemon, a sendmail server, a proxy server and " 
    1992 "some other services doesn't complain with 7 users connected; the load is " 
    1993 "still 0 on average. Some (multi-CPU) systems I've seen were quite happy with " 
    1994 "a load of 67. There is only one way to find out - check the load regularly " 
    1995 "if you want to know what's normal. If you don't, you will only be able to " 
    1996 "measure system load from the response time of the command line, which is a " 
    1997 "very rough measurement since this speed is influenced by a hundred other " 
    1998 "factors." 
     1518msgid "In short: the load<indexterm><primary>system</primary><secondary>load</secondary></indexterm> depends on what is normal<indexterm><primary>load</primary></indexterm> for your system. My old P133 running a firewall, SSH server, file server, a route daemon, a sendmail server, a proxy server and some other services doesn't complain with 7 users connected; the load is still 0 on average. Some (multi-CPU) systems I've seen were quite happy with a load of 67. There is only one way to find out - check the load regularly if you want to know what's normal. If you don't, you will only be able to measure system load from the response time of the command line, which is a very rough measurement since this speed is influenced by a hundred other factors." 
    19991519msgstr "" 
    20001520 
    20011521#: ../chap4.xml:526(para) 
    2002 msgid "" 
    2003 "Keep in mind that different systems will behave different with the same load " 
    2004 "average. For example, a system with a graphics card supporting hardware " 
    2005 "acceleration will have no problem rendering 3D images, while the same system " 
    2006 "with a cheap VGA card will slow down tremendously while rendering. My old " 
    2007 "P133 will become quite uncomfortable when I start the X server, but on a " 
    2008 "modern system you hardly notice the difference in the system load." 
     1522msgid "Keep in mind that different systems will behave different with the same load average. For example, a system with a graphics card supporting hardware acceleration will have no problem rendering 3D images, while the same system with a cheap VGA card will slow down tremendously while rendering. My old P133 will become quite uncomfortable when I start the X server, but on a modern system you hardly notice the difference in the system load." 
    20091523msgstr "" 
    20101524 
    … …  
    20141528 
    20151529#: ../chap4.xml:529(para) 
    2016 msgid "" 
    2017 "A big environment can slow you down. If you have lots of environment " 
    2018 "variables set (instead of shell variables), long search paths that are not " 
    2019 "optimized (errors in setting the path environment variable) and more of " 
    2020 "those settings that are usually made <quote>on the fly</quote>, the system " 
    2021 "will need more time to search and read data." 
     1530msgid "A big environment can slow you down. If you have lots of environment variables set (instead of shell variables), long search paths that are not optimized (errors in setting the path environment variable) and more of those settings that are usually made <quote>on the fly</quote>, the system will need more time to search and read data." 
    20221531msgstr "" 
    20231532 
    20241533#: ../chap4.xml:530(para) 
    2025 msgid "" 
    2026 "In X, window managers and desktop environments can be real CPU-eaters. A " 
    2027 "really fancy desktop comes with a price, even when you can download it for " 
    2028 "free, since most desktops provide add-ons ad infinitum. Modesty is a virtue " 
    2029 "if you don't buy a new computer every year." 
     1534msgid "In X, window managers and desktop environments can be real CPU-eaters. A really fancy desktop comes with a price, even when you can download it for free, since most desktops provide add-ons ad infinitum. Modesty is a virtue if you don't buy a new computer every year." 
    20301535msgstr "" 
    20311536 
    20321537#: ../chap4.xml:531(title) 
    20331538msgid "Priority" 
    2034 msgstr "" 
     1539msgstr "Prioridade" 
    20351540 
    20361541#: ../chap4.xml:532(para) 
    2037 msgid "" 
    2038 "The priority<indexterm><primary>processes</primary><secondary>priority</" 
    2039 "secondary></indexterm> or importance of a job is defined by it's " 
    2040 "<emphasis>nice</emphasis> number<indexterm><primary>nice number</primary></" 
    2041 "indexterm>. A program with a high nice number is friendly to other programs, " 
    2042 "other users and the system; it is not an important job. The lower the nice " 
    2043 "number, the more important a job is and the more resources it will take " 
    2044 "without sharing them." 
     1542msgid "The priority<indexterm><primary>processes</primary><secondary>priority</secondary></indexterm> or importance of a job is defined by it's <emphasis>nice</emphasis> number<indexterm><primary>nice number</primary></indexterm>. A program with a high nice number is friendly to other programs, other users and the system; it is not an important job. The lower the nice number, the more important a job is and the more resources it will take without sharing them." 
    20451543msgstr "" 
    20461544 
    20471545#: ../chap4.xml:533(para) 
    2048 msgid "" 
    2049 "Making a job nicer by increasing its nice number is only useful for " 
    2050 "processes that use a lot of CPU time (compilers, math applications and the " 
    2051 "like). Processes that always use a lot of I/O time are automatically " 
    2052 "rewarded by the system and given a higher priority (a lower nice number), " 
    2053 "for example keyboard input always gets highest priority on a system." 
     1546msgid "Making a job nicer by increasing its nice number is only useful for processes that use a lot of CPU time (compilers, math applications and the like). Processes that always use a lot of I/O time are automatically rewarded by the system and given a higher priority (a lower nice number), for example keyboard input always gets highest priority on a system." 
    20541547msgstr "" 
    20551548 
    20561549#: ../chap4.xml:534(para) 
    2057 msgid "" 
    2058 "Defining the priority of a program is done with the " 
    2059 "<command>nice<indexterm><primary>nice</primary></indexterm></command> " 
    2060 "command." 
     1550msgid "Defining the priority of a program is done with the <command>nice<indexterm><primary>nice</primary></indexterm></command> command." 
    20611551msgstr "" 
    20621552 
    20631553#: ../chap4.xml:535(para) 
    2064 msgid "" 
    2065 "Most systems also provide the BSD <command>renice<indexterm><primary>renice</" 
    2066 "primary></indexterm></command> command, which allows you to change the " 
    2067 "<emphasis>niceness</emphasis> of a running command. Again, read the man page " 
    2068 "for your system-specific information." 
     1554msgid "Most systems also provide the BSD <command>renice<indexterm><primary>renice</primary></indexterm></command> command, which allows you to change the <emphasis>niceness</emphasis> of a running command. Again, read the man page for your system-specific information." 
    20691555msgstr "" 
    20701556 
    20711557#: ../chap4.xml:536(title) 
    20721558msgid "Interactive programs" 
    2073 msgstr "" 
     1559msgstr "Programas interativos" 
    20741560 
    20751561#: ../chap4.xml:537(para) 
    2076 msgid "" 
    2077 "It is NOT a good idea to <command>nice</command> or <command>renice</" 
    2078 "command> an interactive program or a job running in the foreground." 
     1562msgid "It is NOT a good idea to <command>nice</command> or <command>renice</command> an interactive program or a job running in the foreground." 
    20791563msgstr "" 
    20801564 
    20811565#: ../chap4.xml:538(para) 
    2082 msgid "" 
    2083 "Use of these commands is usually a task for the system administrator. Read " 
    2084 "the man page for more info on extra functionality available to the system " 
    2085 "administrator." 
     1566msgid "Use of these commands is usually a task for the system administrator. Read the man page for more info on extra functionality available to the system administrator." 
    20861567msgstr "" 
    20871568 
    20881569#: ../chap4.xml:540(title) 
    20891570msgid "CPU resources" 
    2090 msgstr "" 
     1571msgstr "Recursos de CPU" 
    20911572 
    20921573#: ../chap4.xml:541(para) 
    2093 msgid "" 
    2094 "On every Linux system, many programs want to use the " 
    2095 "CPU<indexterm><primary>system</primary><secondary>CPU resources</secondary></" 
    2096 "indexterm>(s) at the same time, even if you are the only user on the system. " 
    2097 "Every program needs a certain amount of cycles on the CPU to run. There may " 
    2098 "be times when there are not enough cycles because the CPU is too busy. The " 
    2099 "<command>uptime<indexterm><primary>uptime</primary></indexterm></command> " 
    2100 "command is wildly inaccurate (it only displays averages, you have to know " 
    2101 "what is normal), but far from being useless. There are some actions you can " 
    2102 "undertake if you think your CPU is to blame for the unresponsiveness of your " 
    2103 "system:" 
     1574msgid "On every Linux system, many programs want to use the CPU<indexterm><primary>system</primary><secondary>CPU resources</secondary></indexterm>(s) at the same time, even if you are the only user on the system. Every program needs a certain amount of cycles on the CPU to run. There may be times when there are not enough cycles because the CPU is too busy. The <command>uptime<indexterm><primary>uptime</primary></indexterm></command> command is wildly inaccurate (it only displays averages, you have to know what is normal), but far from being useless. There are some actions you can undertake if you think your CPU is to blame for the unresponsiveness of your system:" 
    21041575msgstr "" 
    21051576 
    21061577#: ../chap4.xml:543(para) 
    2107 msgid "" 
    2108 "Run heavy programs when the load is low. This may be the case on your system " 
    2109 "during the night. See next section for scheduling." 
     1578msgid "Run heavy programs when the load is low. This may be the case on your system during the night. See next section for scheduling." 
    21101579msgstr "" 
    21111580 
    21121581#: ../chap4.xml:544(para) 
    2113 msgid "" 
    2114 "Prevent the system from doing unnecessary work: stop daemons and programs " 
    2115 "that you don't use, use <command>locate</command> instead of a heavy " 
    2116 "<command>find</command>, ..." 
     1582msgid "Prevent the system from doing unnecessary work: stop daemons and programs that you don't use, use <command>locate</command> instead of a heavy <command>find</command>, ..." 
    21171583msgstr "" 
    21181584 
    21191585#: ../chap4.xml:545(para) 
    21201586msgid "Run big jobs with a low priority" 
    2121 msgstr "" 
     1587msgstr "Execute grandes tarefas com baixa prioridade" 
    21221588 
    21231589#: ../chap4.xml:547(para) 
    2124 msgid "" 
    2125 "If none of these solutions are an option in your particular situation, you " 
    2126 "may want to upgrade your CPU. On a UNIX machine this is a job for the system " 
    2127 "admin." 
     1590msgid "If none of these solutions are an option in your particular situation, you may want to upgrade your CPU. On a UNIX machine this is a job for the system admin." 
    21281591msgstr "" 
    21291592 
    21301593#: ../chap4.xml:549(title) 
    21311594msgid "Memory resources" 
    2132 msgstr "" 
     1595msgstr "Recursos de memória" 
    21331596 
    21341597#: ../chap4.xml:550(para) 
    2135 msgid "" 
    2136 "When the currently running processes<indexterm><primary>system</" 
    2137 "primary><secondary>memory resources</secondary></indexterm> expect more " 
    2138 "memory than the system has physically available, a Linux system will not " 
    2139 "crash; it will start paging, or " 
    2140 "<emphasis>swapping<indexterm><primary>swapping</primary></indexterm></" 
    2141 "emphasis>, meaning the process uses the memory on disk or in swap space, " 
    2142 "moving contents of the physical memory (pieces of running programs or entire " 
    2143 "programs in the case of swapping) to disk, thus reclaiming the physical " 
    2144 "memory to handle more processes. This slows the system down enormously since " 
    2145 "access to disk is much slower than access to memory. The " 
    2146 "<command>top<indexterm><primary>top</primary></indexterm></command> command " 
    2147 "can be used to display memory and swap use. Systems using glibc offer the " 
    2148 "<command>memusage</command> and <command>memusagestat</command> commands to " 
    2149 "visualize memory usage." 
     1598msgid "When the currently running processes<indexterm><primary>system</primary><secondary>memory resources</secondary></indexterm> expect more memory than the system has physically available, a Linux system will not crash; it will start paging, or <emphasis>swapping<indexterm><primary>swapping</primary></indexterm></emphasis>, meaning the process uses the memory on disk or in swap space, moving contents of the physical memory (pieces of running programs or entire programs in the case of swapping) to disk, thus reclaiming the physical memory to handle more processes. This slows the system down enormously since access to disk is much slower than access to memory. The <command>top<indexterm><primary>top</primary></indexterm></command> command can be used to display memory and swap use. Systems using glibc offer the <command>memusage</command> and <command>memusagestat</command> commands to visualize memory usage." 
    21501599msgstr "" 
    21511600 
    21521601#: ../chap4.xml:551(para) 
    2153 msgid "" 
    2154 "If you find that a lot of memory and swap space are being used, you can try:" 
     1602msgid "If you find that a lot of memory and swap space are being used, you can try:" 
    21551603msgstr "" 
    21561604 
    21571605#: ../chap4.xml:553(para) 
    2158 msgid "" 
    2159 "Killing, stopping or renicing those programs that use a big chunk of memory" 
     1606msgid "Killing, stopping or renicing those programs that use a big chunk of memory" 
    21601607msgstr "" 
    21611608 
    … …  
    21651612 
    21661613#: ../chap4.xml:555(para) 
    2167 msgid "" 
    2168 "Tuning system performance, which is beyond the scope of this document. See " 
    2169 "the reading list in <xref linkend=\"app1\"/> for more." 
     1614msgid "Tuning system performance, which is beyond the scope of this document. See the reading list in <xref linkend=\"app1\"/> for more." 
    21701615msgstr "" 
    21711616 
    21721617#: ../chap4.xml:558(title) 
    21731618msgid "I/O resources" 
    2174 msgstr "" 
     1619msgstr "Recursos de Entrada/Saída" 
    21751620 
    21761621#: ../chap4.xml:559(para) 
    2177 msgid "" 
    2178 "While I/O limitations<indexterm><primary>system</primary><secondary>I/O " 
    2179 "resources</secondary></indexterm> are a major cause of stress for system " 
    2180 "admins, the Linux system offers rather poor utilities to measure I/O " 
    2181 "performance. The <command>ps<indexterm><primary>ps</primary></indexterm></" 
    2182 "command>, <command>vmstat<indexterm><primary>vmstat</primary></indexterm></" 
    2183 "command> and <command>top<indexterm><primary>top</primary></indexterm></" 
    2184 "command> tools give some indication about how many programs are waiting for " 
    2185 "I/O; <command>netstat<indexterm><primary>netstat</primary></indexterm></" 
    2186 "command> displays network interface statistics, but there are virtually no " 
    2187 "tools available to measure the I/O response to system load, and the " 
    2188 "<command>iostat<indexterm><primary>iostat</primary></indexterm></command> " 
    2189 "command gives a brief overview of general I/O usage. Various graphical front-" 
    2190 "ends exist to put the output of these commands in a humanly understandable " 
    2191 "form." 
     1622msgid "While I/O limitations<indexterm><primary>system</primary><secondary>I/O resources</secondary></indexterm> are a major cause of stress for system admins, the Linux system offers rather poor utilities to measure I/O performance. The <command>ps<indexterm><primary>ps</primary></indexterm></command>, <command>vmstat<indexterm><primary>vmstat</primary></indexterm></command> and <command>top<indexterm><primary>top</primary></indexterm></command> tools give some indication about how many programs are waiting for I/O; <command>netstat<indexterm><primary>netstat</primary></indexterm></command> displays network interface statistics, but there are virtually no tools available to measure the I/O response to system load, and the <command>iostat<indexterm><primary>iostat</primary></indexterm></command> command gives a brief overview of general I/O usage. Various graphical front-ends exist to put the output of these commands in a humanly understandable form." 
    21921623msgstr "" 
    21931624 
    21941625#: ../chap4.xml:560(para) 
    2195 msgid "" 
    2196 "Each device has its own problems, but the bandwidth available to network " 
    2197 "interfaces and the bandwidth available to disks are the two primary causes " 
    2198 "of bottlenecks in I/O performance." 
     1626msgid "Each device has its own problems, but the bandwidth available to network interfaces and the bandwidth available to disks are the two primary causes of bottlenecks in I/O performance." 
    21991627msgstr "" 
    22001628 
    … …  
    22051633#: ../chap4.xml:563(para) 
    22061634msgid "Network overload:" 
    2207 msgstr "" 
     1635msgstr "Sobrecarga de rede:" 
    22081636 
    22091637#: ../chap4.xml:564(para) 
    2210 msgid "" 
    2211 "The amount of data transported over the network is larger than the network's " 
    2212 "capacity, resulting in slow execution of every network related task for all " 
    2213 "users. They can be solved by cleaning up the network (which mainly involves " 
    2214 "disabling protocols and services that you don't need) or by reconfiguring " 
    2215 "the network (for example use of subnets, replacing hubs with switches, " 
    2216 "upgrading interfaces and equipment)." 
     1638msgid "The amount of data transported over the network is larger than the network's capacity, resulting in slow execution of every network related task for all users. They can be solved by cleaning up the network (which mainly involves disabling protocols and services that you don't need) or by reconfiguring the network (for example use of subnets, replacing hubs with switches, upgrading interfaces and equipment)." 
    22171639msgstr "" 
    22181640 
    22191641#: ../chap4.xml:566(para) 
    22201642msgid "Network integrity problems:" 
    2221 msgstr "" 
     1643msgstr "Problemas de integridade de rede:" 
    22221644 
    22231645#: ../chap4.xml:567(para) 
    2224 msgid "" 
    2225 "Occurs when data is transferred incorrectly. Solving this kind of problem " 
    2226 "can only be done by isolating the faulty element and replacing it." 
     1646msgid "Occurs when data is transferred incorrectly. Solving this kind of problem can only be done by isolating the faulty element and replacing it." 
    22271647msgstr "" 
    22281648 
    22291649#: ../chap4.xml:571(para) 
    22301650msgid "Disk I/O problems:" 
    2231 msgstr "" 
     1651msgstr "Problemas de Entrada/Saída de disco:" 
    22321652 
    22331653#: ../chap4.xml:573(para) 
    … …  
    22441664 
    22451665#: ../chap4.xml:576(para) 
    2246 msgid "" 
    2247 "The maximum total bandwidth that the system can provide to all programs that " 
    2248 "run is not enough." 
     1666msgid "The maximum total bandwidth that the system can provide to all programs that run is not enough." 
    22491667msgstr "" 
    22501668 
    22511669#: ../chap4.xml:578(para) 
    2252 msgid "" 
    2253 "This kind of problem is more difficult to detect, and usually takes extra " 
    2254 "hardware in order to re-divide data streams over buses, controllers and " 
    2255 "disks, if overloaded hardware is cause of the problem. One solution to solve " 
    2256 "this is a RAID array configuration optimized for input and output actions. " 
    2257 "This way, you get to keep the same hardware. An upgrade to faster buses, " 
    2258 "controlers and disks is usually the other option." 
     1670msgid "This kind of problem is more difficult to detect, and usually takes extra hardware in order to re-divide data streams over buses, controllers and disks, if overloaded hardware is cause of the problem. One solution to solve this is a RAID array configuration optimized for input and output actions. This way, you get to keep the same hardware. An upgrade to faster buses, controlers and disks is usually the other option." 
    22591671msgstr "" 
    22601672 
    22611673#: ../chap4.xml:579(para) 
    2262 msgid "" 
    2263 "If overload is not the cause, maybe your hardware is gradually failing, or " 
    2264 "not well connected to the system. Check contacts, connectors and plugs to " 
    2265 "start with." 
     1674msgid "If overload is not the cause, maybe your hardware is gradually failing, or not well connected to the system. Check contacts, connectors and plugs to start with." 
    22661675msgstr "" 
    22671676 
    22681677#: ../chap4.xml:581(title) 
    22691678msgid "Users" 
    2270 msgstr "" 
     1679msgstr "Usuários" 
    22711680 
    22721681#: ../chap4.xml:582(para) 
    2273 msgid "" 
    2274 "Users can be divided in several classes, depending on their behavior with " 
    2275 "resource<indexterm><primary>users</primary><secondary>classification</" 
    2276 "secondary></indexterm> usage:" 
     1682msgid "Users can be divided in several classes, depending on their behavior with resource<indexterm><primary>users</primary><secondary>classification</secondary></indexterm> usage:" 
    22771683msgstr "" 
    22781684 
    22791685#: ../chap4.xml:584(para) 
    2280 msgid "" 
    2281 "Users who run a (large) number of small jobs: you, the beginning Linux user, " 
    2282 "for instance." 
     1686msgid "Users who run a (large) number of small jobs: you, the beginning Linux user, for instance." 
    22831687msgstr "" 
    22841688 
    22851689#: ../chap4.xml:585(para) 
    2286 msgid "" 
    2287 "Users who run relatively few but large jobs: users running simulations, " 
    2288 "calculations, emulators or other programs that eat a lot of memory, and " 
    2289 "usually these users have accompanying large data files." 
     1690msgid "Users who run relatively few but large jobs: users running simulations, calculations, emulators or other programs that eat a lot of memory, and usually these users have accompanying large data files." 
    22901691msgstr "" 
    22911692 
    22921693#: ../chap4.xml:586(para) 
    2293 msgid "" 
    2294 "Users who run few jobs but use a lot of CPU time (developers and the like)." 
     1694msgid "Users who run few jobs but use a lot of CPU time (developers and the like)." 
    22951695msgstr "" 
    22961696 
    22971697#: ../chap4.xml:588(para) 
    2298 msgid "" 
    2299 "You can see that system requirements may vary for each class of users, and " 
    2300 "that it can be hard to satisfy everyone. If you are on a multi-user system, " 
    2301 "it is useful (and fun) to find out habits of other users and the system, in " 
    2302 "order to get the most out of it for your specific purposes." 
     1698msgid "You can see that system requirements may vary for each class of users, and that it can be hard to satisfy everyone. If you are on a multi-user system, it is useful (and fun) to find out habits of other users and the system, in order to get the most out of it for your specific purposes." 
    23031699msgstr "" 
    23041700 
    23051701#: ../chap4.xml:590(title) 
    23061702msgid "Graphical tools" 
    2307 msgstr "" 
     1703msgstr "Ferramentas gráficas" 
    23081704 
    23091705#: ../chap4.xml:591(para) 
    2310 msgid "" 
    2311 "For the graphical environment, there are a whole bunch of " 
    2312 "monitoring<indexterm><primary>system</primary><secondary>monitoring</" 
    2313 "secondary></indexterm> tools available. Below is a screen shot of the " 
    2314 "<application>Gnome System Monitor<indexterm><primary>monitoring</primary></" 
    2315 "indexterm></application>, which has features for displaying and searching " 
    2316 "process information, and monitoring<indexterm><primary>Gnome System Monitor</" 
    2317 "primary></indexterm> system resources:" 
     1706msgid "For the graphical environment, there are a whole bunch of monitoring<indexterm><primary>system</primary><secondary>monitoring</secondary></indexterm> tools available. Below is a screen shot of the <application>Gnome System Monitor<indexterm><primary>monitoring</primary></indexterm></application>, which has features for displaying and searching process information, and monitoring<indexterm><primary>Gnome System Monitor</primary></indexterm> system resources:" 
    23181707msgstr "" 
    23191708 
    … …  
    23271716 
    23281717#: ../chap4.xml:604(para) 
    2329 msgid "" 
    2330 "There are also a couple of handy icons you can install in the task bar, such " 
    2331 "as a disk, memory and load monitor. <command>xload<indexterm><primary>xload</" 
    2332 "primary></indexterm></command> is another small X application for monitoring " 
    2333 "system load. Find your favorite!" 
     1718msgid "There are also a couple of handy icons you can install in the task bar, such as a disk, memory and load monitor. <command>xload<indexterm><primary>xload</primary></indexterm></command> is another small X application for monitoring system load. Find your favorite!" 
    23341719msgstr "" 
    23351720 
    … …  
    23391724 
    23401725#: ../chap4.xml:607(para) 
    2341 msgid "" 
    2342 "As a non-privileged user, you can only influence your own processes. We " 
    2343 "already saw how you can display processes and filter out processes that " 
    2344 "belong to a particular user, and what possible restrictions can occur. When " 
    2345 "you see that one of your processes is eating too much of the system's " 
    2346 "resources<indexterm><primary>processes</primary><secondary>manage load</" 
    2347 "secondary></indexterm>, there are two things that you can do:" 
     1726msgid "As a non-privileged user, you can only influence your own processes. We already saw how you can display processes and filter out processes that belong to a particular user, and what possible restrictions can occur. When you see that one of your processes is eating too much of the system's resources<indexterm><primary>processes</primary><secondary>manage load</secondary></indexterm>, there are two things that you can do:" 
    23481727msgstr "" 
    23491728 
    … …  
    23571736 
    23581737#: ../chap4.xml:612(para) 
    2359 msgid "" 
    2360 "In the case that you want the process to continue to run, but you also want " 
    2361 "to give the other processes on the system a chance, you can <command>renice</" 
    2362 "command> the process. Appart from using the <command>nice</command> or " 
    2363 "<command>renice</command> commands, <command>top<indexterm><primary>top</" 
    2364 "primary><secondary>changing process priority</secondary></indexterm></" 
    2365 "command> is an easy way of spotting the troublesome process(es) and reducing " 
    2366 "priority<indexterm><primary>processes</primary><secondary>changing priority</" 
    2367 "secondary></indexterm>." 
     1738msgid "In the case that you want the process to continue to run, but you also want to give the other processes on the system a chance, you can <command>renice</command> the process. Appart from using the <command>nice</command> or <command>renice</command> commands, <command>top<indexterm><primary>top</primary><secondary>changing process priority</secondary></indexterm></command> is an easy way of spotting the troublesome process(es) and reducing priority<indexterm><primary>processes</primary><secondary>changing priority</secondary></indexterm>." 
    23681739msgstr "" 
    23691740 
    23701741#: ../chap4.xml:613(para) 
    2371 msgid "" 
    2372 "Identify the process in the <quote>NI</quote> column, it will most likely " 
    2373 "have a negative priority. Type <command>r</command> and enter the process ID " 
    2374 "of the process that you want to renice. Then enter the nice value, for " 
    2375 "instance <quote>20</quote>. That means that from now on, this process will " 
    2376 "take 1/5 of the CPU cycles at the most." 
     1742msgid "Identify the process in the <quote>NI</quote> column, it will most likely have a negative priority. Type <command>r</command> and enter the process ID of the process that you want to renice. Then enter the nice value, for instance <quote>20</quote>. That means that from now on, this process will take 1/5 of the CPU cycles at the most." 
    23771743msgstr "" 
    23781744 
    23791745#: ../chap4.xml:614(para) 
    2380 msgid "" 
    2381 "Examples of processes that you want to keep on running are emulators, " 
    2382 "virtual machines, compilers and so on." 
     1746msgid "Examples of processes that you want to keep on running are emulators, virtual machines, compilers and so on." 
    23831747msgstr "" 
    23841748 
    23851749#: ../chap4.xml:616(para) 
    2386 msgid "" 
    2387 "If you want to stop a process because it hangs or is going totally berserk " 
    2388 "in the way of I/O consumption, file creation or use of other system " 
    2389 "resources, use the <command>kill</command> command. If you have the " 
    2390 "opportunity, first try to kill the process softly, sending it the " 
    2391 "<emphasis>SIGTERM<indexterm><primary>SIGTERM</primary></indexterm></" 
    2392 "emphasis> signal. This is an instruction to terminate whatever it is doing, " 
    2393 "according to procedures as described in the code of the " 
    2394 "program<indexterm><primary>kill</primary><secondary>example</secondary></" 
    2395 "indexterm>:" 
    2396 msgstr "" 
    2397  
    2398 #: ../chap4.xml:618(command) ../chap4.xml:626(command) 
     1750msgid "If you want to stop a process because it hangs or is going totally berserk in the way of I/O consumption, file creation or use of other system resources, use the <command>kill</command> command. If you have the opportunity, first try to kill the process softly, sending it the <emphasis>SIGTERM<indexterm><primary>SIGTERM</primary></indexterm></emphasis> signal. This is an instruction to terminate whatever it is doing, according to procedures as described in the code of the program<indexterm><primary>kill</primary><secondary>example</secondary></indexterm>:" 
     1751msgstr "" 
     1752 
     1753#: ../chap4.xml:618(command) 
     1754#: ../chap4.xml:626(command) 
    23991755#: ../chap4.xml:631(command) 
    24001756msgid "ps <placeholder-1/>" 
    2401 msgstr "" 
    2402  
    2403 #: ../chap4.xml:618(parameter) ../chap4.xml:626(parameter) 
     1757msgstr "ps <placeholder-1/>" 
     1758 
     1759#: ../chap4.xml:618(parameter) 
     1760#: ../chap4.xml:626(parameter) 
    24041761msgid "mozilla" 
    2405 msgstr "" 
    2406  
    2407 #: ../chap4.xml:618(command) ../chap4.xml:626(command) 
     1762msgstr "mozilla" 
     1763 
     1764#: ../chap4.xml:618(command) 
     1765#: ../chap4.xml:626(command) 
    24081766#: ../chap4.xml:631(command) 
    24091767msgid "grep <placeholder-1/>" 
    2410 msgstr "" 
     1768msgstr "grep <placeholder-1/>" 
    24111769 
    24121770#: ../chap4.xml:621(option) 
    24131771msgid "-15" 
    2414 msgstr "" 
     1772msgstr "-15" 
    24151773 
    24161774#: ../chap4.xml:621(parameter) 
    24171775msgid "25822" 
    2418 msgstr "" 
    2419  
    2420 #: ../chap4.xml:621(command) ../chap4.xml:629(command) 
     1776msgstr "25822" 
     1777 
     1778#: ../chap4.xml:621(command) 
     1779#: ../chap4.xml:629(command) 
    24211780msgid "kill <placeholder-1/><placeholder-2/>" 
    2422 msgstr "" 
     1781msgstr "kill <placeholder-1/><placeholder-2/>" 
    24231782 
    24241783#: ../chap4.xml:617(screen) 
    … …  
    24311790"<placeholder-4/> <placeholder-5/>\n" 
    24321791msgstr "" 
     1792"\n" 
     1793"<placeholder-1/> <placeholder-2/> | <placeholder-3/>\n" 
     1794"joe    25822\t1  0 Mar11 ?\t00:34:04 /usr/lib/mozilla-1.4.1/mozilla-\n" 
     1795"\n" 
     1796"<placeholder-4/> <placeholder-5/>\n" 
    24331797 
    24341798#: ../chap4.xml:623(para) 
    2435 msgid "" 
    2436 "In the example above, user <emphasis>joe</emphasis> stopped his Mozilla " 
    2437 "browser because it hung." 
     1799msgid "In the example above, user <emphasis>joe</emphasis> stopped his Mozilla browser because it hung." 
    24381800msgstr "" 
    24391801 
    24401802#: ../chap4.xml:624(para) 
    2441 msgid "" 
    2442 "Some processes are a little bit harder to get rid of. If you have the time, " 
    2443 "you might want to send them the SIGINT<indexterm><primary>SIGINT</primary></" 
    2444 "indexterm> signal to interrupt them. If that does not do the trick either, " 
    2445 "use the strongest signal, SIGKILL<indexterm><primary>SIGKILL</primary></" 
    2446 "indexterm>. In the example below, <emphasis>joe</emphasis> " 
    2447 "stops<indexterm><primary>kill</primary><secondary>example</secondary></" 
    2448 "indexterm> a <application>Mozilla</application> that is frozen:" 
     1803msgid "Some processes are a little bit harder to get rid of. If you have the time, you might want to send them the SIGINT<indexterm><primary>SIGINT</primary></indexterm> signal to interrupt them. If that does not do the trick either, use the strongest signal, SIGKILL<indexterm><primary>SIGKILL</primary></indexterm>. In the example below, <emphasis>joe</emphasis> stops<indexterm><primary>kill</primary><secondary>example</secondary></indexterm> a <application>Mozilla</application> that is frozen:" 
    24491804msgstr "" 
    24501805 
    24511806#: ../chap4.xml:629(option) 
    24521807msgid "-9" 
    2453 msgstr "" 
    2454  
    2455 #: ../chap4.xml:629(parameter) ../chap4.xml:631(parameter) 
     1808msgstr "-9" 
     1809 
     1810#: ../chap4.xml:629(parameter) 
     1811#: ../chap4.xml:631(parameter) 
    24561812msgid "25915" 
    2457 msgstr "" 
     1813msgstr "25915" 
    24581814 
    24591815#: ../chap4.xml:625(screen) 
    … …  
    24711827 
    24721828#: ../chap4.xml:634(para) 
    2473 msgid "" 
    2474 "In such cases, you might want to check that the process is really dead, " 
    2475 "using the <command>grep</command> filter again on the PID. If this only " 
    2476 "returns the <command>grep</command> process, you can be sure that you " 
    2477 "succeeded in stopping the process." 
     1829msgid "In such cases, you might want to check that the process is really dead, using the <command>grep</command> filter again on the PID. If this only returns the <command>grep</command> process, you can be sure that you succeeded in stopping the process." 
    24781830msgstr "" 
    24791831 
    24801832#: ../chap4.xml:635(para) 
    2481 msgid "" 
    2482 "Among processes that are hard to kill is your shell. And that is a good " 
    2483 "thing: if they would be easy to kill, you woud loose your shell every time " 
    2484 "you type <keycap>Ctrl</keycap>-<keycap>C</keycap> on the command line " 
    2485 "accidentally, since this is equivalent to sending a SIGINT." 
     1833msgid "Among processes that are hard to kill is your shell. And that is a good thing: if they would be easy to kill, you woud loose your shell every time you type <keycap>Ctrl</keycap>-<keycap>C</keycap> on the command line accidentally, since this is equivalent to sending a SIGINT." 
    24861834msgstr "" 
    24871835 
    … …  
    24911839 
    24921840#: ../chap4.xml:637(para) 
    2493 msgid "" 
    2494 "The usage of pipes (|) for using output of one command as input of another " 
    2495 "is explained in the next chapter, <xref linkend=\"chap_05\"/>." 
     1841msgid "The usage of pipes (|) for using output of one command as input of another is explained in the next chapter, <xref linkend=\"chap_05\"/>." 
    24961842msgstr "" 
    24971843 
    24981844#: ../chap4.xml:639(para) 
    2499 msgid "" 
    2500 "In a graphical environment, the <command>xkill<indexterm><primary>xkill</" 
    2501 "primary></indexterm></command> program is very easy to use. Just type the " 
    2502 "name of the command, followed by an <keycap>Enter</keycap> and select the " 
    2503 "window of the application that you want to stop. It is rather dangerous " 
    2504 "because it sends a SIGKILL by default, so only use it when an application " 
    2505 "hangs." 
     1845msgid "In a graphical environment, the <command>xkill<indexterm><primary>xkill</primary></indexterm></command> program is very easy to use. Just type the name of the command, followed by an <keycap>Enter</keycap> and select the window of the application that you want to stop. It is rather dangerous because it sends a SIGKILL by default, so only use it when an application hangs." 
    25061846msgstr "" 
    25071847 
    25081848#: ../chap4.xml:646(title) 
    25091849msgid "Use that idle time!" 
    2510 msgstr "" 
     1850msgstr "Use aquele tempo ocioso!" 
    25111851 
    25121852#: ../chap4.xml:647(para) 
    2513 msgid "" 
    2514 "A Linux system can have a lot to suffer from, but it usually " 
    2515 "suffers<indexterm><primary>processes</primary><secondary>scheduling</" 
    2516 "secondary></indexterm> only during office hours. Whether in an office " 
    2517 "environment, a server room or at home, most Linux systems are just idling " 
    2518 "away during the morning, the evening, the nights and weekends. Using this " 
    2519 "idle time can be a lot cheaper than buying those machines you'd absolutely " 
    2520 "need if you want everything done at the same time." 
     1853msgid "A Linux system can have a lot to suffer from, but it usually suffers<indexterm><primary>processes</primary><secondary>scheduling</secondary></indexterm> only during office hours. Whether in an office environment, a server room or at home, most Linux systems are just idling away during the morning, the evening, the nights and weekends. Using this idle time can be a lot cheaper than buying those machines you'd absolutely need if you want everything done at the same time." 
    25211854msgstr "" 
    25221855 
    25231856#: ../chap4.xml:648(para) 
    2524 msgid "" 
    2525 "There are three types<indexterm><primary>scheduling</" 
    2526 "primary><secondary>types</secondary></indexterm> of delayed execution:" 
     1857msgid "There are three types<indexterm><primary>scheduling</primary><secondary>types</secondary></indexterm> of delayed execution:" 
    25271858msgstr "" 
    25281859 
    25291860#: ../chap4.xml:650(para) 
    2530 msgid "" 
    2531 "Waiting a little while and then resuming job execution, using the " 
    2532 "<command>sleep<indexterm><primary>sleep</primary></indexterm></command> " 
    2533 "command. Execution time depends on the system time at the moment of " 
    2534 "submission." 
     1861msgid "Waiting a little while and then resuming job execution, using the <command>sleep<indexterm><primary>sleep</primary></indexterm></command> command. Execution time depends on the system time at the moment of submission." 
    25351862msgstr "" 
    25361863 
    25371864#: ../chap4.xml:651(para) 
    2538 msgid "" 
    2539 "Running a command at a specified<indexterm><primary>at</primary></indexterm> " 
    2540 "time, using the <command>at</command> command. Execution of the job(s) " 
    2541 "depends on system time, not the time of submission." 
     1865msgid "Running a command at a specified<indexterm><primary>at</primary></indexterm> time, using the <command>at</command> command. Execution of the job(s) depends on system time, not the time of submission." 
    25421866msgstr "" 
    25431867 
    25441868#: ../chap4.xml:652(para) 
    2545 msgid "" 
    2546 "Regularly running a command on a monthly, weekly, daily or hourly basis, " 
    2547 "using the <command>cron<indexterm><primary>cron</primary></indexterm></" 
    2548 "command> facilities." 
     1869msgid "Regularly running a command on a monthly, weekly, daily or hourly basis, using the <command>cron<indexterm><primary>cron</primary></indexterm></command> facilities." 
    25491870msgstr "" 
    25501871 
    … …  
    25551876#: ../chap4.xml:656(title) 
    25561877msgid "The sleep command" 
    2557 msgstr "" 
     1878msgstr "O comando sleep" 
    25581879 
    25591880#: ../chap4.xml:657(para) 
    2560 msgid "" 
    2561 "The Info page on sleep is probably one of the shortest there is. All " 
    2562 "<command>sleep<indexterm><primary>scheduling</primary><secondary>sleep</" 
    2563 "secondary></indexterm></command> does is wait. By default the time to wait " 
    2564 "is expressed in seconds." 
     1881msgid "The Info page on sleep is probably one of the shortest there is. All <command>sleep<indexterm><primary>scheduling</primary><secondary>sleep</secondary></indexterm></command> does is wait. By default the time to wait is expressed in seconds." 
    25651882msgstr "" 
    25661883 
    25671884#: ../chap4.xml:658(para) 
    2568 msgid "" 
    2569 "So why does it exist? Some practical examples<indexterm><primary>sleep</" 
    2570 "primary><secondary>examples</secondary></indexterm>:" 
     1885msgid "So why does it exist? Some practical examples<indexterm><primary>sleep</primary><secondary>examples</secondary></indexterm>:" 
    25711886msgstr "" 
    25721887 
    25731888#: ../chap4.xml:659(para) 
    2574 msgid "" 
    2575 "Somebody calls you on the phone, you say \"Yes I'll be with you in half an " 
    2576 "hour\" but you're about drowned in work as it is and bound to forget your " 
    2577 "lunch:" 
     1889msgid "Somebody calls you on the phone, you say \"Yes I'll be with you in half an hour\" but you're about drowned in work as it is and bound to forget your lunch:" 
    25781890msgstr "" 
    25791891 
    25801892#: ../chap4.xml:660(parameter) 
    25811893msgid "1800" 
    2582 msgstr "" 
     1894msgstr "1800" 
    25831895 
    25841896#: ../chap4.xml:660(parameter) 
    25851897msgid "\"Lunch time..\"" 
    2586 msgstr "" 
     1898msgstr "\"Hora do almoço..\"" 
    25871899 
    25881900#: ../chap4.xml:660(command) 
    25891901msgid "(sleep <placeholder-1/>; echo <placeholder-2/>) &amp;" 
    2590 msgstr "" 
     1902msgstr "(sleep <placeholder-1/>; echo <placeholder-2/>) &amp;" 
    25911903 
    25921904#: ../chap4.xml:661(para) 
    2593 msgid "" 
    2594 "When you can't use the <command>at</command> command for some reason, it's " 
    2595 "five o'clock, you want to go home but there's still work to do and right now " 
    2596 "somebody is eating system resources:" 
     1905msgid "When you can't use the <command>at</command> command for some reason, it's five o'clock, you want to go home but there's still work to do and right now somebody is eating system resources:" 
    25971906msgstr "" 
    25981907 
    25991908#: ../chap4.xml:662(parameter) 
    26001909msgid "10000" 
    2601 msgstr "" 
     1910msgstr "10000" 
    26021911 
    26031912#: ../chap4.xml:662(command) 
    … …  
    26061915 
    26071916#: ../chap4.xml:663(para) 
    2608 msgid "" 
    2609 "Make sure there's an auto-logout on your system, and that you log out or " 
    2610 "lock your desktop/office when submitting this kind of job, or run it in a " 
    2611 "<command>screen</command> session." 
     1917msgid "Make sure there's an auto-logout on your system, and that you log out or lock your desktop/office when submitting this kind of job, or run it in a <command>screen</command> session." 
    26121918msgstr "" 
    26131919 
    26141920#: ../chap4.xml:664(para) 
    2615 msgid "" 
    2616 "When you run a series of printouts of large files, but you want other users " 
    2617 "to be able to print in between:" 
     1921msgid "When you run a series of printouts of large files, but you want other users to be able to print in between:" 
    26181922msgstr "" 
    26191923 
    26201924#: ../chap4.xml:665(filename) 
    26211925msgid "lotoftext" 
    2622 msgstr "" 
     1926msgstr "muitotexto" 
    26231927 
    26241928#: ../chap4.xml:665(parameter) 
    26251929msgid "900" 
    2626 msgstr "" 
     1930msgstr "900" 
    26271931 
    26281932#: ../chap4.xml:665(filename) 
    26291933msgid "hugefile" 
    2630 msgstr "" 
     1934msgstr "arquivoimenso" 
    26311935 
    26321936#: ../chap4.xml:665(filename) 
    26331937msgid "anotherlargefile" 
    2634 msgstr "" 
     1938msgstr "outroarquivogrande" 
    26351939 
    26361940#: ../chap4.xml:665(command) 
    2637 msgid "" 
    2638 "lp <placeholder-1/>; sleep <placeholder-2/>; lp <placeholder-3/>; sleep " 
    2639 "<placeholder-4/>; lp <placeholder-5/>" 
    2640 msgstr "" 
     1941msgid "lp <placeholder-1/>; sleep <placeholder-2/>; lp <placeholder-3/>; sleep <placeholder-4/>; lp <placeholder-5/>" 
     1942msgstr "lp <placeholder-1/>; sleep <placeholder-2/>; lp <placeholder-3/>; sleep <placeholder-4/>; lp <placeholder-5/>" 
    26411943 
    26421944#: ../chap4.xml:666(para) 
    … …  
    26451947 
    26461948#: ../chap4.xml:667(para) 
    2647 msgid "" 
    2648 "Programmers often use the sleep command to halt script or program execution " 
    2649 "for a certain time." 
     1949msgid "Programmers often use the sleep command to halt script or program execution for a certain time." 
    26501950msgstr "" 
    26511951 
    26521952#: ../chap4.xml:669(title) 
    26531953msgid "The at command" 
    2654 msgstr "" 
     1954msgstr "O comando at" 
    26551955 
    26561956#: ../chap4.xml:670(para) 
    2657 msgid "" 
    2658 "The <command>at</command> command<indexterm><primary>scheduling</" 
    2659 "primary><secondary>at</secondary></indexterm> executes commands at a given " 
    2660 "time, using your default shell unless you tell the command otherwise (see " 
    2661 "the man page)." 
     1957msgid "The <command>at</command> command<indexterm><primary>scheduling</primary><secondary>at</secondary></indexterm> executes commands at a given time, using your default shell unless you tell the command otherwise (see the man page)." 
    26621958msgstr "" 
    26631959 
    26641960#: ../chap4.xml:671(para) 
    2665 msgid "" 
    2666 "The options to <command>at</command> are rather user-friendly, which is " 
    2667 "demonstrated in the examples<indexterm><primary>at</" 
    2668 "primary><secondary>example</secondary></indexterm> below:" 
    2669 msgstr "" 
    2670  
    2671 #: ../chap4.xml:673(prompt) ../chap4.xml:683(prompt) 
     1961msgid "The options to <command>at</command> are rather user-friendly, which is demonstrated in the examples<indexterm><primary>at</primary><secondary>example</secondary></indexterm> below:" 
     1962msgstr "" 
     1963 
     1964#: ../chap4.xml:673(prompt) 
     1965#: ../chap4.xml:683(prompt) 
    26721966msgid "steven@home:~&gt;" 
    2673 msgstr "" 
     1967msgstr "steven@home:~&gt;" 
    26741968 
    26751969#: ../chap4.xml:673(command) 
    26761970msgid "at tomorrow + 2 days" 
    2677 msgstr "" 
    2678  
    2679 #: ../chap4.xml:676(prompt) ../chap4.xml:677(prompt) ../chap4.xml:686(prompt) 
    2680 #: ../chap4.xml:687(prompt) ../chap4.xml:688(prompt) 
     1971msgstr "at tomorrow + 2 days" 
     1972 
     1973#: ../chap4.xml:676(prompt) 
     1974#: ../chap4.xml:677(prompt) 
     1975#: ../chap4.xml:686(prompt) 
     1976#: ../chap4.xml:687(prompt) 
     1977#: ../chap4.xml:688(prompt) 
    26811978msgid "at&gt;" 
    2682 msgstr "" 
     1979msgstr "at&gt;" 
    26831980 
    26841981#: ../chap4.xml:676(command) 
    26851982msgid "cat reports | mail myboss@mycompany" 
    2686 msgstr "" 
     1983msgstr "cat relatorios | mail meuchefe@minhaempresa" 
    26871984 
    26881985#: ../chap4.xml:672(screen) 
    … …  
    26991996 
    27001997#: ../chap4.xml:680(para) 
    2701 msgid "" 
    2702 "Typing <keycap>Ctrl</keycap>+<keycap>D</keycap> quits the <command>at</" 
    2703 "command> utility and generates the <quote>EOT</quote> message." 
     1998msgid "Typing <keycap>Ctrl</keycap>+<keycap>D</keycap> quits the <command>at</command> utility and generates the <quote>EOT</quote> message." 
    27041999msgstr "" 
    27052000 
    27062001#: ../chap4.xml:681(para) 
    2707 msgid "" 
    2708 "User <emphasis>steven</emphasis> does a strange thing here combining two " 
    2709 "commands; we will study this sort of practice in <xref linkend=\"chap_05\"/" 
    2710 ">, Redirecting Input and Output." 
     2002msgid "User <emphasis>steven</emphasis> does a strange thing here combining two commands; we will study this sort of practice in <xref linkend=\"chap_05\"/>, Redirecting Input and Output." 
    27112003msgstr "" 
    27122004 
    27132005#: ../chap4.xml:683(command) 
    27142006msgid "at 0237" 
    2715 msgstr "" 
     2007msgstr "at 0237" 
    27162008 
    27172009#: ../chap4.xml:686(command) 
    27182010msgid "cd new-programs" 
    2719 msgstr "" 
     2011msgstr "cd programas-novos" 
    27202012 
    27212013#: ../chap4.xml:687(command) 
    27222014msgid "./configure; make" 
    2723 msgstr "" 
     2015msgstr "./configure; make" 
    27242016 
    27252017#: ../chap4.xml:682(screen) 
    … …  
    27372029 
    27382030#: ../chap4.xml:691(para) 
    2739 msgid "" 
    2740 "The <option>-m</option> option sends mail to the user when the job is done, " 
    2741 "or explains when a job can't be done. The command <command>atq</command> " 
    2742 "lists jobs; perform this command before submitting jobs in order prevent " 
    2743 "them from starting at the same time as others. With the <command>atrm</" 
    2744 "command> command you can remove scheduled jobs if you change your mind." 
     2031msgid "The <option>-m</option> option sends mail to the user when the job is done, or explains when a job can't be done. The command <command>atq</command> lists jobs; perform this command before submitting jobs in order prevent them from starting at the same time as others. With the <command>atrm</command> command you can remove scheduled jobs if you change your mind." 
    27452032msgstr "" 
    27462033 
    27472034#: ../chap4.xml:692(para) 
    2748 msgid "" 
    2749 "It is a good idea to pick strange execution<indexterm><primary>scheduling</" 
    2750 "primary><secondary>execution time</secondary></indexterm> times, because " 
    2751 "system jobs are often run at <quote>round</quote> hours, as you can see in " 
    2752 "<xref linkend=\"sect_04_04_04\"/> the next section. For example, jobs are " 
    2753 "often run at exactly 1 o'clock in the morning (e.g. system indexing to " 
    2754 "update a standard locate database), so entering a time of 0100 may easily " 
    2755 "slow your system down rather than fire it up. To prevent jobs from running " 
    2756 "all at the same time, you may also use the " 
    2757 "<command>batch<indexterm><primary>scheduling</primary><secondary>batch</" 
    2758 "secondary></indexterm></command> command, which queues processes and feeds " 
    2759 "the work in the queue to the system in an evenly balanced way, preventing " 
    2760 "excessive bursts of system resource usage. See the Info pages for more " 
    2761 "information." 
     2035msgid "It is a good idea to pick strange execution<indexterm><primary>scheduling</primary><secondary>execution time</secondary></indexterm> times, because system jobs are often run at <quote>round</quote> hours, as you can see in <xref linkend=\"sect_04_04_04\"/> the next section. For example, jobs are often run at exactly 1 o'clock in the morning (e.g. system indexing to update a standard locate database), so entering a time of 0100 may easily slow your system down rather than fire it up. To prevent jobs from running all at the same time, you may also use the <command>batch<indexterm><primary>scheduling</primary><secondary>batch</secondary></indexterm></command> command, which queues processes and feeds the work in the queue to the system in an evenly balanced way, preventing excessive bursts of system resource usage. See the Info pages for more information." 
    27622036msgstr "" 
    27632037 
    27642038#: ../chap4.xml:696(title) 
    27652039msgid "Cron and crontab" 
    2766 msgstr "" 
     2040msgstr "Cron e crontab" 
    27672041 
    27682042#: ../chap4.xml:697(para) 
    2769 msgid "" 
    2770 "The cron system is managed by the <command>cron</command> " 
    2771 "daemon<indexterm><primary>daemons</primary><secondary>cron</secondary></" 
    2772 "indexterm>. It gets information about which programs and when they should " 
    2773 "run from the system's and users' crontab<indexterm><primary>scheduling</" 
    2774 "primary><secondary>cron</secondary></indexterm> entries. Only the root user " 
    2775 "has access to the system crontabs, while each user should only have access " 
    2776 "to his own crontabs. On some systems (some) users may not have access to the " 
    2777 "cron facility." 
     2043msgid "The cron system is managed by the <command>cron</command> daemon<indexterm><primary>daemons</primary><secondary>cron</secondary></indexterm>. It gets information about which programs and when they should run from the system's and users' crontab<indexterm><primary>scheduling</primary><secondary>cron</secondary></indexterm> entries. Only the root user has access to the system crontabs, while each user should only have access to his own crontabs. On some systems (some) users may not have access to the cron facility." 
    27782044msgstr "" 
    27792045 
    27802046#: ../chap4.xml:698(para) 
    2781 msgid "" 
    2782 "At system startup the cron daemon searches <filename>/var/spool/cron/</" 
    2783 "filename> for crontab entries which are named after accounts in <filename>/" 
    2784 "etc/passwd</filename>, it searches <filename>/etc/cron.d/" 
    2785 "<indexterm><primary>cron.d</primary></indexterm></filename> and it searches " 
    2786 "<filename>/etc/crontab<indexterm><primary>crontab</primary></indexterm></" 
    2787 "filename>, then uses this information every minute to check if there is " 
    2788 "something to be done. It executes commands as the user who owns the crontab " 
    2789 "file and mails any output of commands to the owner." 
     2047msgid "At system startup the cron daemon searches <filename>/var/spool/cron/</filename> for crontab entries which are named after accounts in <filename>/etc/passwd</filename>, it searches <filename>/etc/cron.d/<indexterm><primary>cron.d</primary></indexterm></filename> and it searches <filename>/etc/crontab<indexterm><primary>crontab</primary></indexterm></filename>, then uses this information every minute to check if there is something to be done. It executes commands as the user who owns the crontab file and mails any output of commands to the owner." 
    27902048msgstr "" 
    27912049 
    27922050#: ../chap4.xml:699(para) 
    2793 msgid "" 
    2794 "On systems using <application>Vixie<indexterm><primary>cron</" 
    2795 "primary><secondary>Vixie cron</secondary></indexterm></application> cron, " 
    2796 "jobs that occur hourly, daily, weekly and monthly are kept in separate " 
    2797 "directories in <filename>/etc</filename> to keep an overview, as opposed to " 
    2798 "the standard UNIX cron function, where all tasks are entered into one big " 
    2799 "file." 
     2051msgid "On systems using <application>Vixie<indexterm><primary>cron</primary><secondary>Vixie cron</secondary></indexterm></application> cron, jobs that occur hourly, daily, weekly and monthly are kept in separate directories in <filename>/etc</filename> to keep an overview, as opposed to the standard UNIX cron function, where all tasks are entered into one big file." 
    28002052msgstr "" 
    28012053 
    28022054#: ../chap4.xml:700(para) 
    2803 msgid "" 
    2804 "Example of a <application>Vixie</application> " 
    2805 "crontab<indexterm><primary>crontab</primary><secondary>example</secondary></" 
    2806 "indexterm> file:" 
     2055msgid "Example of a <application>Vixie</application> crontab<indexterm><primary>crontab</primary><secondary>example</secondary></indexterm> file:" 
    28072056msgstr "" 
    28082057 
    28092058#: ../chap4.xml:702(prompt) 
    28102059msgid "[root@blob /etc]#" 
    2811 msgstr "" 
     2060msgstr "[root@blob /etc]#" 
    28122061 
    28132062#: ../chap4.xml:702(command) 
    28142063msgid "more crontab" 
    2815 msgstr "" 
     2064msgstr "mais crontab" 
    28162065 
    28172066#: ../chap4.xml:701(screen) 
    … …  
    28382087#: ../chap4.xml:718(title) 
    28392088msgid "Alternative" 
    2840 msgstr "" 
     2089msgstr "Alternativa" 
    28412090 
    28422091#: ../chap4.xml:719(para) 
    2843 msgid "" 
    2844 "You could also use the <command>crontab <option>-l</option></command> " 
    2845 "command to display crontabs." 
     2092msgid "You could also use the <command>crontab <option>-l</option></command> command to display crontabs." 
    28462093msgstr "" 
    28472094 
    28482095#: ../chap4.xml:721(para) 
    2849 msgid "" 
    2850 "Some variables are set, and after that there's the actual scheduling, one " 
    2851 "line per job, starting with 5 time<indexterm><primary>cron</" 
    2852 "primary><secondary>crontab syntax</secondary></indexterm> and date fields. " 
    2853 "The first field contains the minutes (from 0 to 59), the second defines the " 
    2854 "hour of execution (0-23), the third is day of the month (1-31), then the " 
    2855 "number of the month (1-12), the last is day of the week (0-7, both 0 and 7 " 
    2856 "are Sunday). An asterisk in these fields represents the total acceptable " 
    2857 "range for the field. Lists are allowed; to execute a job from Monday to " 
    2858 "Friday enter 1-5 in the last field, to execute a job on Monday, Wednesday " 
    2859 "and Friday enter 1,3,5." 
     2096msgid "Some variables are set, and after that there's the actual scheduling, one line per job, starting with 5 time<indexterm><primary>cron</primary><secondary>crontab syntax</secondary></indexterm> and date fields. The first field contains the minutes (from 0 to 59), the second defines the hour of execution (0-23), the third is day of the month (1-31), then the number of the month (1-12), the last is day of the week (0-7, both 0 and 7 are Sunday). An asterisk in these fields represents the total acceptable range for the field. Lists are allowed; to execute a job from Monday to Friday enter 1-5 in the last field, to execute a job on Monday, Wednesday and Friday enter 1,3,5." 
    28602097msgstr "" 
    28612098 
    28622099#: ../chap4.xml:722(para) 
    2863 msgid "" 
    2864 "Then comes the user who should run the processes which are listed in the " 
    2865 "last column. The example above is from a Vixie cron configuration where root " 
    2866 "runs the program <command>run-parts<indexterm><primary>run-parts</primary></" 
    2867 "indexterm></command> on regular intervals<indexterm><primary>cron</" 
    2868 "primary><secondary>run-parts</secondary></indexterm>, with the appropriate " 
    2869 "directories as options. In these directories, the actual jobs to be executed " 
    2870 "at the scheduled time are stored as shell scripts, like this little script " 
    2871 "that is run daily to update the database used by the <command>locate</" 
    2872 "command> command:" 
     2100msgid "Then comes the user who should run the processes which are listed in the last column. The example above is from a Vixie cron configuration where root runs the program <command>run-parts<indexterm><primary>run-parts</primary></indexterm></command> on regular intervals<indexterm><primary>cron</primary><secondary>run-parts</secondary></indexterm>, with the appropriate directories as options. In these directories, the actual jobs to be executed at the scheduled time are stored as shell scripts, like this little script that is run daily to update the database used by the <command>locate</command> command:" 
    28732101msgstr "" 
    28742102 
    … …  
    28932121 
    28942122#: ../chap4.xml:730(para) 
    2895 msgid "" 
    2896 "Users are supposed to edit their crontabs<indexterm><primary>cron</" 
    2897 "primary><secondary>edit crontab</secondary></indexterm> in a safe way using " 
    2898 "the <command>crontab <option>-e</option></command> " 
    2899 "command<indexterm><primary>crontab</primary></indexterm>. This will prevent " 
    2900 "a user from accidentally opening more than one copy of his/her crontab file. " 
    2901 "The default editor is <command>vi</command> (see <xref linkend=\"chap_06\"/" 
    2902 ">, but you can use any text editor, such as <command>gvim</command> or " 
    2903 "<command>gedit</command> if you feel more comfortable with a GUI editor." 
     2123msgid "Users are supposed to edit their crontabs<indexterm><primary>cron</primary><secondary>edit crontab</secondary></indexterm> in a safe way using the <command>crontab <option>-e</option></command> command<indexterm><primary>crontab</primary></indexterm>. This will prevent a user from accidentally opening more than one copy of his/her crontab file. The default editor is <command>vi</command> (see <xref linkend=\"chap_06\"/>, but you can use any text editor, such as <command>gvim</command> or <command>gedit</command> if you feel more comfortable with a GUI editor." 
    29042124msgstr "" 
    29052125 
    29062126#: ../chap4.xml:731(para) 
    2907 msgid "" 
    2908 "When you quit, the system will tell you that a new crontab is installed." 
     2127msgid "When you quit, the system will tell you that a new crontab is installed." 
    29092128msgstr "" 
    29102129 
    29112130#: ../chap4.xml:732(para) 
    2912 msgid "" 
    2913 "This crontab entry reminds <emphasis>billy</emphasis> to go to his sports " 
    2914 "club every Thursday night:" 
     2131msgid "This crontab entry reminds <emphasis>billy</emphasis> to go to his sports club every Thursday night:" 
    29152132msgstr "" 
    29162133 
    29172134#: ../chap4.xml:734(command) 
    29182135msgid "crontab -l" 
    2919 msgstr "" 
     2136msgstr "crontab -l" 
    29202137 
    29212138#: ../chap4.xml:733(screen) 
    … …  
    29312148 
    29322149#: ../chap4.xml:740(para) 
    2933 msgid "" 
    2934 "After adding a new scheduled task, the system will tell you that a new " 
    2935 "crontab is installed. You do not need to restart the <command>cron</command> " 
    2936 "daemon for the changes to take effect. In the example, <emphasis>billy</" 
    2937 "emphasis> added a new line pointing to a backup script:" 
     2150msgid "After adding a new scheduled task, the system will tell you that a new crontab is installed. You do not need to restart the <command>cron</command> daemon for the changes to take effect. In the example, <emphasis>billy</emphasis> added a new line pointing to a backup script:" 
    29382151msgstr "" 
    29392152 
    29402153#: ../chap4.xml:742(command) 
    29412154msgid "crontab -e" 
    2942 msgstr "" 
     2155msgstr "crontab -e" 
    29432156 
    29442157#: ../chap4.xml:741(screen) 
    … …  
    29582171 
    29592172#: ../chap4.xml:752(para) 
    2960 msgid "" 
    2961 "The <filename>backup.sh</filename> script is executed every Thursday and " 
    2962 "Sunday. See <xref linkend=\"sect_07_02_07\"/> for an introduction to shell " 
    2963 "scripting. Keep in mind that output of commands, if any, is mailed to the " 
    2964 "owner of the crontab file. If no mail service is configured, you might find " 
    2965 "the output of your commands in your local mailbox, <filename>/var/spool/mail/" 
    2966 "&lt;your_username&gt;</filename>, a plain text file." 
     2173msgid "The <filename>backup.sh</filename> script is executed every Thursday and Sunday. See <xref linkend=\"sect_07_02_07\"/> for an introduction to shell scripting. Keep in mind that output of commands, if any, is mailed to the owner of the crontab file. If no mail service is configured, you might find the output of your commands in your local mailbox, <filename>/var/spool/mail/&lt;your_username&gt;</filename>, a plain text file." 
    29672174msgstr "" 
    29682175 
    29692176#: ../chap4.xml:753(title) 
    29702177msgid "Who runs my commands?" 
    2971 msgstr "" 
     2178msgstr "Quem executa meus comandos?" 
    29722179 
    29732180#: ../chap4.xml:754(para) 
    2974 msgid "" 
    2975 "You don't have to specify the user who should run the commands. They are " 
    2976 "executed with the user's own permissions by default." 
     2181msgid "You don't have to specify the user who should run the commands. They are executed with the user's own permissions by default." 
    29772182msgstr "" 
    29782183 
    29792184#: ../chap4.xml:759(title) 
    29802185msgid "Summary" 
    2981 msgstr "" 
     2186msgstr "Resumo" 
    29822187 
    29832188#: ../chap4.xml:760(para) 
    2984 msgid "" 
    2985 "Linux is a multi-user, multi-tasking operating system that has a UNIX-like " 
    2986 "way of handling processes. Execution speed of commands can depend on a " 
    2987 "thousand tiny things. Among others, we learned a lot of new commands to " 
    2988 "visualize and handle processes. Here's a list:" 
     2189msgid "Linux is a multi-user, multi-tasking operating system that has a UNIX-like way of handling processes. Execution speed of commands can depend on a thousand tiny things. Among others, we learned a lot of new commands to visualize and handle processes. Here's a list:" 
    29892190msgstr "" 
    29902191 
    29912192#: ../chap4.xml:761(title) 
    29922193msgid "New commands in chapter 4: Processes" 
    2993 msgstr "" 
     2194msgstr "Novos comandos no capítudo 4: Processos" 
    29942195 
    29952196#: ../chap4.xml:765(entry) 
    29962197msgid "Command" 
    2997 msgstr "" 
     2198msgstr "Comando" 
    29982199 
    29992200#: ../chap4.xml:770(command) 
    30002201msgid "at" 
    3001 msgstr "" 
     2202msgstr "at" 
    30022203 
    30032204#: ../chap4.xml:770(entry) 
    30042205msgid "Queue jobs for later execution." 
    3005 msgstr "" 
     2206msgstr "Põe tarefas em uma fila para executar mais tarde" 
    30062207 
    30072208#: ../chap4.xml:773(command) 
    30082209msgid "atq" 
    3009 msgstr "" 
     2210msgstr "atq" 
    30102211 
    30112212#: ../chap4.xml:773(entry) 
    30122213msgid "Lists the user's pending jobs." 
    3013 msgstr "" 
     2214msgstr "Lista as tarefas pendentes do usuário" 
    30142215 
    30152216#: ../chap4.xml:776(command) 
    30162217msgid "atrm" 
    3017 msgstr "" 
     2218msgstr "atrm" 
    30182219 
    30192220#: ../chap4.xml:776(entry) 
    30202221msgid "Deletes jobs, determined by their job number." 
    3021 msgstr "" 
     2222msgstr "Remove tarefas, determinadas pelo número da tarefa." 
    30222223 
    30232224#: ../chap4.xml:779(command) 
    30242225msgid "batch" 
    3025 msgstr "" 
     2226msgstr "batch" 
    30262227 
    30272228#: ../chap4.xml:779(entry) 
    30282229msgid "Executes commands when system load level permits." 
    3029 msgstr "" 
     2230msgstr "Executa comandos quando o nível de carga do sistema permite." 
    30302231 
    30312232#: ../chap4.xml:782(command) 
    30322233msgid "crontab" 
    3033 msgstr "" 
     2234msgstr "crontab" 
    30342235 
    30352236#: ../chap4.xml:782(entry) 
    30362237msgid "Maintain crontab files for individual users." 
    3037 msgstr "" 
     2238msgstr "Mantém arquivos do crontab para usuários individuais." 
    30382239 
    30392240#: ../chap4.xml:785(command) 
    30402241msgid "halt" 
    3041 msgstr "" 
    3042  
    3043 #: ../chap4.xml:785(entry) ../chap4.xml:815(entry) 
     2242msgstr "halt" 
     2243 
     2244#: ../chap4.xml:785(entry) 
     2245#: ../chap4.xml:815(entry) 
    30442246msgid "Stop the system." 
    3045 msgstr "" 
     2247msgstr "Pára o sistema." 
    30462248 
    30472249#: ../chap4.xml:788(parameter) 
    30482250msgid "run level" 
    3049 msgstr "" 
     2251msgstr "nível de execução" 
    30502252 
    30512253#: ../chap4.xml:788(command) 
    30522254msgid "init <placeholder-1/>" 
    3053 msgstr "" 
     2255msgstr "init <placeholder-1/>" 
    30542256 
    30552257#: ../chap4.xml:788(entry) 
    30562258msgid "Process control initialization." 
    3057 msgstr "" 
     2259msgstr "Inicialização do controle de processo" 
    30582260 
    30592261#: ../chap4.xml:791(entry) 
    30602262msgid "Lists currently executing jobs." 
    3061 msgstr "" 
     2263msgstr "Lista tarefas atualmente em execução." 
    30622264 
    30632265#: ../chap4.xml:794(entry) 
    30642266msgid "Terminate a process." 
    3065 msgstr "" 
     2267msgstr "Termina um processo." 
    30662268 
    30672269#: ../chap4.xml:797(command) 
    30682270msgid "mesg" 
    3069 msgstr "" 
     2271msgstr "mesg" 
    30702272 
    30712273#: ../chap4.xml:797(entry) 
    30722274msgid "Control write access to your terminal." 
    3073 msgstr "" 
     2275msgstr "Controla o acesso a escrita no seu terminal." 
    30742276 
    30752277#: ../chap4.xml:800(command) 
    30762278msgid "netstat" 
    3077 msgstr "" 
     2279msgstr "netstat" 
    30782280 
    30792281#: ../chap4.xml:800(entry) 
    3080 msgid "" 
    3081 "Display network connections, routing tables, interface statistics, " 
    3082 "masquerade connections and multicast memberships." 
    3083 msgstr "" 
     2282msgid "Display network connections, routing tables, interface statistics, masquerade connections and multicast memberships." 
     2283msgstr "Exibe conexões de rede, tabelas de rota, estatísticas de dispositivo, conexões mascaradas e associações de multicast." 
    30842284 
    30852285#: ../chap4.xml:803(command) 
    30862286msgid "nice" 
    3087 msgstr "" 
     2287msgstr "nice" 
    30882288 
    30892289#: ../chap4.xml:803(entry) 
    30902290msgid "Run a program with modified scheduling priority." 
    3091 msgstr "" 
     2291msgstr "Executa um programa com uma prioridade de agendamento modificada." 
    30922292 
    30932293#: ../chap4.xml:806(command) 
    30942294msgid "pgrep" 
    3095 msgstr "" 
     2295msgstr "pgrep" 
    30962296 
    30972297#: ../chap4.xml:806(entry) 
    30982298msgid "Display processes." 
    3099 msgstr "" 
     2299msgstr "Exibe processos." 
    31002300 
    31012301#: ../chap4.xml:809(entry) 
    31022302msgid "Report process status." 
    3103 msgstr "" 
     2303msgstr "Relata status de processos." 
    31042304 
    31052305#: ../chap4.xml:812(entry) 
    31062306msgid "Display a tree of processes." 
    3107 msgstr "" 
     2307msgstr "Exibe uma árvore de processos." 
    31082308 
    31092309#: ../chap4.xml:815(command) 
    31102310msgid "reboot" 
    3111 msgstr "" 
     2311msgstr "reboot" 
    31122312 
    31132313#: ../chap4.xml:818(command) 
    31142314msgid "renice" 
    3115 msgstr "" 
     2315msgstr "renice" 
    31162316 
    31172317#: ../chap4.xml:818(entry) 
    31182318msgid "Alter priority of running processes." 
    3119 msgstr "" 
     2319msgstr "Altera prioridade dos processos em execução." 
    31202320 
    31212321#: ../chap4.xml:821(command) 
    31222322msgid "shutdown" 
    3123 msgstr "" 
     2323msgstr "shutdown" 
    31242324 
    31252325#: ../chap4.xml:821(entry) 
    31262326msgid "Bring the system down." 
    3127 msgstr "" 
     2327msgstr "Desliga o sistema." 
    31282328 
    31292329#: ../chap4.xml:824(command) 
    31302330msgid "sleep" 
    3131 msgstr "" 
     2331msgstr "sleep" 
    31322332 
    31332333#: ../chap4.xml:824(entry) 
    31342334msgid "Delay for a specified time." 
    3135 msgstr "" 
     2335msgstr "Suspende por um tempo específico." 
    31362336 
    31372337#: ../chap4.xml:827(command) 
    31382338msgid "time" 
    3139 msgstr "" 
     2339msgstr "time" 
    31402340 
    31412341#: ../chap4.xml:827(entry) 
    31422342msgid "Time a command or report resource usage." 
    3143 msgstr "" 
     2343msgstr "Marca o tempo de um comando ou relata o consumo de recursos." 
    31442344 
    31452345#: ../chap4.xml:830(command) 
    31462346msgid "top" 
    3147 msgstr "" 
     2347msgstr "top" 
    31482348 
    31492349#: ../chap4.xml:830(entry) 
    31502350msgid "Display top CPU processes." 
    3151 msgstr "" 
     2351msgstr "Exibe os processos da CPU que estão no topo." 
    31522352 
    31532353#: ../chap4.xml:833(entry) 
    31542354msgid "Show how long the system has been running." 
    3155 msgstr "" 
     2355msgstr "Mostra quanto tempo o sistema esteve operando." 
    31562356 
    31572357#: ../chap4.xml:836(command) 
    31582358msgid "vmstat" 
    3159 msgstr "" 
     2359msgstr "vmstat" 
    31602360 
    31612361#: ../chap4.xml:836(entry) 
    31622362msgid "Report virtual memory statistics." 
    3163 msgstr "" 
     2363msgstr "Relata estatísticas de memória virtual." 
    31642364 
    31652365#: ../chap4.xml:839(command) 
    31662366msgid "w" 
    3167 msgstr "" 
     2367msgstr "w" 
    31682368 
    31692369#: ../chap4.xml:839(entry) 
    31702370msgid "Show who is logged on and what they are doing." 
    3171 msgstr "" 
     2371msgstr "Mostra quem está conectado e o que estão fazendo." 
    31722372 
    31732373#: ../chap4.xml:842(command) 
    31742374msgid "wall" 
    3175 msgstr "" 
     2375msgstr "wall" 
    31762376 
    31772377#: ../chap4.xml:842(entry) 
    31782378msgid "Send a message to everybody's terminals." 
    3179 msgstr "" 
     2379msgstr "Envia uma mensagem os terminais de todos." 
    31802380 
    31812381#: ../chap4.xml:845(entry) 
    31822382msgid "Show who is logged on." 
    3183 msgstr "" 
     2383msgstr "Mostra quem está conectado." 
    31842384 
    31852385#: ../chap4.xml:848(command) 
    31862386msgid "write" 
    3187 msgstr "" 
     2387msgstr "write" 
    31882388 
    31892389#: ../chap4.xml:848(entry) 
    31902390msgid "Send a message to another user." 
    3191 msgstr "" 
     2391msgstr "Envia uma mensagem para outro usuário." 
    31922392 
    31932393#: ../chap4.xml:856(title) 
    31942394msgid "Exercises" 
    3195 msgstr "" 
     2395msgstr "Exercícios" 
    31962396 
    31972397#: ../chap4.xml:857(para) 
    3198 msgid "" 
    3199 "These are some exercises that will help you get the feel for processes " 
    3200 "running on your system." 
     2398msgid "These are some exercises that will help you get the feel for processes running on your system." 
    32012399msgstr "" 
    32022400 
    … …  
    32062404 
    32072405#: ../chap4.xml:860(para) 
    3208 msgid "" 
    3209 "Run <command>top</command> in one terminal while you do the exercises in " 
    3210 "another." 
     2406msgid "Run <command>top</command> in one terminal while you do the exercises in another." 
    32112407msgstr "" 
    32122408 
    … …  
    32202416 
    32212417#: ../chap4.xml:863(para) 
    3222 msgid "" 
    3223 "Run the command <command>find <filename>/</filename></command>. What effect " 
    3224 "does it have on system load? Stop this command." 
     2418msgid "Run the command <command>find <filename>/</filename></command>. What effect does it have on system load? Stop this command." 
    32252419msgstr "" 
    32262420 
    32272421#: ../chap4.xml:864(para) 
    3228 msgid "" 
    3229 "In graphical mode, start the <command>xclock</command> program in the " 
    3230 "foreground. Then let it run in the background. Stop the program using the " 
    3231 "<command>kill</command> command." 
     2422msgid "In graphical mode, start the <command>xclock</command> program in the foreground. Then let it run in the background. Stop the program using the <command>kill</command> command." 
    32322423msgstr "" 
    32332424 
    32342425#: ../chap4.xml:865(para) 
    3235 msgid "" 
    3236 "Run the <command>xcalc</command> directly in the background, so that the " 
    3237 "prompt of the issuing terminal is released." 
     2426msgid "Run the <command>xcalc</command> directly in the background, so that the prompt of the issuing terminal is released." 
    32382427msgstr "" 
    32392428 
    … …  
    32432432 
    32442433#: ../chap4.xml:867(para) 
    3245 msgid "" 
    3246 "Open two terminals or terminal windows again and use <command>write</" 
    3247 "command> to send a message from one to the other." 
     2434msgid "Open two terminals or terminal windows again and use <command>write</command> to send a message from one to the other." 
    32482435msgstr "" 
    32492436 
    … …  
    32532440 
    32542441#: ../chap4.xml:869(para) 
    3255 msgid "" 
    3256 "How long does it take to execute <command>ls</command> in the current " 
    3257 "directory?" 
     2442msgid "How long does it take to execute <command>ls</command> in the current directory?" 
    32582443msgstr "" 
    32592444 
    32602445#: ../chap4.xml:870(para) 
    3261 msgid "" 
    3262 "Based on process entries in <filename>/proc</filename>, owned by your UID, " 
    3263 "how would you work to find out which processes these actually represent?" 
     2446msgid "Based on process entries in <filename>/proc</filename>, owned by your UID, how would you work to find out which processes these actually represent?" 
    32642447msgstr "" 
    32652448 
    … …  
    32732456 
    32742457#: ../chap4.xml:873(para) 
    3275 msgid "" 
    3276 "Name 3 processes that couldn't have had <command>init</command> as an " 
    3277 "initial parent." 
     2458msgid "Name 3 processes that couldn't have had <command>init</command> as an initial parent." 
    32782459msgstr "" 
    32792460 
    … …  
    32832464 
    32842465#: ../chap4.xml:875(para) 
    3285 msgid "" 
    3286 "Name the commands that are generally causing the highest load on your system." 
     2466msgid "Name the commands that are generally causing the highest load on your system." 
    32872467msgstr "" 
    32882468 
    … …  
    32962476 
    32972477#: ../chap4.xml:881(para) 
    3298 msgid "" 
    3299 "According to your current run level, name the steps that are taken during " 
    3300 "shutdown." 
     2478msgid "According to your current run level, name the steps that are taken during shutdown." 
    33012479msgstr "" 
    33022480 
    33032481#: ../chap4.xml:882(para) 
    3304 msgid "" 
    3305 "How do you change the system run level? Switch from your default run level " 
    3306 "to run level 1 and vice versa." 
     2482msgid "How do you change the system run level? Switch from your default run level to run level 1 and vice versa." 
    33072483msgstr "" 
    33082484 
    33092485#: ../chap4.xml:883(para) 
    3310 msgid "" 
    3311 "Make a list of all the services and daemons that are started up when your " 
    3312 "system has booted." 
     2486msgid "Make a list of all the services and daemons that are started up when your system has booted." 
    33132487msgstr "" 
    33142488 
    … …  
    33182492 
    33192493#: ../chap4.xml:885(para) 
    3320 msgid "" 
    3321 "Suppose you have to start some exotic server at boot time. Up until now, you " 
    3322 "logged in after booting the system and started this server manually using a " 
    3323 "script named <filename>deliver_pizza</filename> in your home directory. What " 
    3324 "do you have to do in order to have the service start up automatically in run " 
    3325 "level 4, which you defined for this purpose only?" 
     2494msgid "Suppose you have to start some exotic server at boot time. Up until now, you logged in after booting the system and started this server manually using a script named <filename>deliver_pizza</filename> in your home directory. What do you have to do in order to have the service start up automatically in run level 4, which you defined for this purpose only?" 
    33262495msgstr "" 
    33272496 
    … …  
    33312500 
    33322501#: ../chap4.xml:890(para) 
    3333 msgid "" 
    3334 "Use <command>sleep</command> to create a reminder that your pasta is ready " 
    3335 "in ten minutes." 
     2502msgid "Use <command>sleep</command> to create a reminder that your pasta is ready in ten minutes." 
    33362503msgstr "" 
    33372504 
    33382505#: ../chap4.xml:891(para) 
    3339 msgid "" 
    3340 "Create an <command>at</command> job that copies all files in your home " 
    3341 "directory to <filename>/var/tmp</filename> within half an hour. You may want " 
    3342 "to create a sub-directory in <filename>/var/tmp</filename>." 
     2506msgid "Create an <command>at</command> job that copies all files in your home directory to <filename>/var/tmp</filename> within half an hour. You may want to create a sub-directory in <filename>/var/tmp</filename>." 
    33432507msgstr "" 
    33442508 
    … …  
    33522516 
    33532517#: ../chap4.xml:894(para) 
    3354 msgid "" 
    3355 "Make a mistake in the crontab entry, like issuing the nonexistent command " 
    3356 "<command>coppy</command> instead of <command>cp</command>. What happens upon " 
    3357 "execution of the task?" 
     2518msgid "Make a mistake in the crontab entry, like issuing the nonexistent command <command>coppy</command> instead of <command>cp</command>. What happens upon execution of the task?" 
    33582519msgstr "" 
    33592520 
    … …  
    33622523msgid "translator-credits" 
    33632524msgstr "" 
     2525