| 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 "" |
| | 113 | msgid "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." |
| | 114 | msgstr "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." |
| 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 "" |
| | 117 | msgid "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." |
| | 118 | msgstr "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." |
| 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 "" |
| | 129 | msgid "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." |
| | 130 | msgstr "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." |
| 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 "" |
| | 133 | msgid "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." |
| | 134 | msgstr "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." |
| 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 "" |
| | 137 | msgid "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." |
| | 138 | msgstr "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." |
| 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) |
| | 141 | msgid "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:" |
| | 142 | msgstr "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) |
| 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 "" |
| | 184 | msgid "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>:" |
| | 185 | msgstr "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>:" |
| 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 "" |
| | 309 | msgid "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." |
| | 310 | msgstr "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." |
| 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 "" |
| | 313 | msgid "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." |
| | 314 | msgstr "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." |
| 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 "" |
| | 321 | msgid "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:" |
| | 322 | msgstr "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:" |
| 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 "" |
| | 329 | msgid "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." |
| | 330 | msgstr "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." |
| 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 "" |
| | 337 | msgid "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." |
| | 338 | msgstr "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." |
| 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 "" |
| | 341 | msgid "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:" |
| | 342 | msgstr "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>:" |
| 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 |
| | 354 | msgid "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)." |
| | 355 | msgstr "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)." |
| 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) |
| | 362 | msgid "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>:" |
| | 363 | msgstr "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) |
| 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 "" |
| | 412 | msgid "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." |
| | 413 | msgstr "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>." |
| 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 "" |
| | 416 | msgid "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." |
| | 417 | msgstr "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." |
| 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 "" |
| | 424 | msgid "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." |
| | 425 | msgstr "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." |
| 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) |
| | 428 | msgid "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>:" |
| | 429 | msgstr "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) |
| 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) |
| | 452 | msgid "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:" |
| | 453 | msgstr "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) |
| | 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" |
| 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 "" |
| | 508 | msgid "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." |
| | 509 | msgstr "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>." |
| 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 "" |
| | 512 | msgid "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 (-)." |
| | 513 | msgstr "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 (-)." |
| 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 "" |
| | 524 | msgid "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." |
| | 525 | msgstr "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." |
| 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 "" |
| | 528 | msgid "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>:" |
| | 529 | msgstr "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." |
| | 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< 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" |
| 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 "" |
| | 612 | msgid "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." |
| | 613 | msgstr "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." |
| 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 "" |
| | 758 | msgid "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>." |
| | 759 | msgstr "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)." |
| 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 "" |
| | 762 | msgid "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." |
| | 763 | msgstr "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)." |
| 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 "" |
| | 766 | msgid "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." |
| | 767 | msgstr "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>." |
| 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 "" |
| | 778 | msgid "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." |
| | 779 | msgstr "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." |
| 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 "" |
| | 782 | msgid "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." |
| | 783 | msgstr "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." |
| 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 "" |
| | 786 | msgid "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>." |
| | 787 | msgstr "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>." |
| 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 |
| | 795 | msgid "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." |
| | 796 | msgstr "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." |
| 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 "" |
| | 799 | msgid "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." |
| | 800 | msgstr "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." |
| 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 "" |
| | 807 | msgid "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>:" |
| | 808 | msgstr "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>:" |
| 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 "" |
| | 891 | msgid "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:" |
| | 892 | msgstr "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:" |
| 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 "" |
| | 920 | msgid "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:" |
| | 921 | msgstr "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:" |
| 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) |
| | 943 | msgid "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:" |
| | 944 | msgstr "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) |
| 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 "" |
| | 977 | msgid "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." |
| | 978 | msgstr "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." |
| 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 "" |
| | 981 | msgid "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." |
| | 982 | msgstr "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> " |
| 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 "" |
| | 985 | msgid "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." |
| | 986 | msgstr "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." |
| 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) |
| | 989 | msgid "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." |
| | 990 | msgstr "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) |
| | 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" |
| 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 "" |
| | 1097 | msgid "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." |
| | 1098 | msgstr "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." |
| 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 "" |
| | 1117 | msgid "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." |
| | 1118 | msgstr "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." |
| 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 "" |
| | 1121 | msgid "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." |
| | 1122 | msgstr "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." |
| 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 "" |
| | 1125 | msgid "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." |
| | 1126 | msgstr "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." |
| 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 "" |
| | 1133 | msgid "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." |
| | 1134 | msgstr "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." |
| 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 "" |
| | 1137 | msgid "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." |
| | 1138 | msgstr "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." |
| 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 "" |
| | 1141 | msgid "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." |
| | 1142 | msgstr "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." |
| 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 "" |
| | 1149 | msgid "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." |
| | 1150 | msgstr "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" |
| 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 "" |
| | 1153 | msgid "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." |
| | 1154 | msgstr "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." |
| 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 "" |
| | 1165 | msgid "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." |
| | 1166 | msgstr "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." |
| 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 "" |
| | 1173 | msgid "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>." |
| | 1174 | msgstr "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>." |
| 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 "" |
| | 1181 | msgid "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." |
| | 1182 | msgstr "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>." |
| 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 "" |
| | 1185 | msgid "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." |
| | 1186 | msgstr "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." |
| 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 "" |
| | 1189 | msgid "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." |
| | 1190 | msgstr "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." |
| 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." |
| | 1224 | msgid "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." |
| 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<x>.d</filename>. Rather, all of the files in <filename>/etc/rc<" |
| 1532 | | "x>.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." |
| | 1236 | msgid "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<x>.d</filename>. Rather, all of the files in <filename>/etc/rc<x>.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." |
| | 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" |
| 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." |
| | 1275 | msgid "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." |
| 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." |
| | 1279 | msgid "<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." |
| 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." |
| | 1283 | msgid "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." |
| 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>." |
| | 1287 | msgid "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>." |
| 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." |
| | 1291 | msgid "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." |
| 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<LEVEL>.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>." |
| | 1303 | msgid "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<LEVEL>.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>." |
| 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." |
| | 1311 | msgid "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." |
| 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." |
| | 1315 | msgid "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." |
| 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." |
| | 1358 | msgid "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." |
| 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." |
| | 1362 | msgid "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." |
| 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>." |
| | 1370 | msgid "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>." |
| 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>." |
| | 1374 | msgid "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>." |
| 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." |
| | 1390 | msgid "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." |
| 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." |
| | 1394 | msgid "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." |
| 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." |
| | 1410 | msgid "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." |
| 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." |
| | 1414 | msgid "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." |
| 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) |
| | 1430 | msgid "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:" |
| | 1431 | msgstr "" |
| | 1432 | |
| | 1433 | #: ../chap4.xml:489(prompt) |
| | 1434 | #: ../chap4.xml:501(prompt) |
| 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:" |
| | 1456 | msgid "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:" |
| 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:" |
| | 1486 | msgid "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:" |
| 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." |
| | 1518 | msgid "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." |
| 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." |
| | 1522 | msgid "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." |
| 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." |
| | 1530 | msgid "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." |
| 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." |
| | 1534 | msgid "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." |
| 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." |
| | 1542 | msgid "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." |
| 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." |
| | 1546 | msgid "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." |
| 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:" |
| | 1574 | msgid "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:" |
| 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." |
| | 1598 | msgid "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." |
| 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." |
| | 1622 | msgid "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." |
| 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)." |
| | 1638 | msgid "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)." |
| 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." |
| | 1670 | msgid "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." |
| 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." |
| | 1698 | msgid "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." |
| 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:" |
| | 1706 | msgid "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:" |
| 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:" |
| | 1726 | msgid "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:" |
| 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>." |
| | 1738 | msgid "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>." |
| 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." |
| | 1742 | msgid "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." |
| 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) |
| | 1750 | msgid "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>:" |
| | 1751 | msgstr "" |
| | 1752 | |
| | 1753 | #: ../chap4.xml:618(command) |
| | 1754 | #: ../chap4.xml:626(command) |
| 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:" |
| | 1803 | msgid "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:" |
| 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." |
| | 1829 | msgid "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." |
| 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." |
| | 1845 | msgid "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." |
| 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." |
| | 1853 | msgid "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." |
| 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) |
| | 1961 | msgid "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:" |
| | 1962 | msgstr "" |
| | 1963 | |
| | 1964 | #: ../chap4.xml:673(prompt) |
| | 1965 | #: ../chap4.xml:683(prompt) |
| 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." |
| | 2031 | msgid "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." |
| 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." |
| | 2035 | msgid "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." |
| 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." |
| | 2043 | msgid "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." |
| 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." |
| | 2047 | msgid "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." |
| 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." |
| | 2051 | msgid "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." |
| 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." |
| | 2096 | msgid "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." |
| 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:" |
| | 2100 | msgid "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:" |
| 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." |
| | 2123 | msgid "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." |
| 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 | | "<your_username></filename>, a plain text file." |
| | 2173 | msgid "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/<your_username></filename>, a plain text file." |
| 3080 | | msgid "" |
| 3081 | | "Display network connections, routing tables, interface statistics, " |
| 3082 | | "masquerade connections and multicast memberships." |
| 3083 | | msgstr "" |
| | 2282 | msgid "Display network connections, routing tables, interface statistics, masquerade connections and multicast memberships." |
| | 2283 | msgstr "Exibe conexões de rede, tabelas de rota, estatÃsticas de dispositivo, conexões mascaradas e associações de multicast." |
| 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?" |
| | 2494 | msgid "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?" |
