Please sign in to see the alerts.

Overview

Project website docs.freebsd.org/en
Translation license BSD 2-Clause "Simplified" License
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Only chosen users can contribute.
  • The translation uses bilingual files.
File mask documentation/content/*/books/developers-handbook/sockets/_index.po

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 4,641 115,821 694,484
Source 273 6,813 40,852
Translated 6% 321 6% 7,096 6% 42,523
Needs editing 1% 59 2% 2,542 2% 15,337
Read-only 5% 273 5% 6,813 5% 40,852
Failing checks 1% 87 2% 3,229 2% 20,106
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 91% 4,261 91% 106,183 91% 636,624
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 3 changes 0 changes 276 changes 277 changes 3 changes 321 changes 0 changes 2 changes 0 changes 0 changes 0 changes 6 changes 276 changes 0 changes 0 changes
Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug

Quick numbers

115 k
Hosted words
4,641
Hosted strings
6%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+6%
—
Contributors
+100%
User avatar None

Committed changes

Documentation / books/developers-handbook/sockets/_index — Portuguese

Committed changes 2 months ago
User avatar None

New strings to translate

Documentation / books/developers-handbook/sockets/_index — Portuguese

273 new strings to translate appeared to the translation. 2 months ago
User avatar None

Resource update

Documentation / books/developers-handbook/sockets/_index — Portuguese

File documentation/content/pt/books/developers-handbook/sockets/_index.po was added. 2 months ago
User avatar None

String updated in the repository

Documentation / books/developers-handbook/sockets/_index — Portuguese

That is why our flowchart now contains a _process signals_ box, which is not connected to any other box. By the way, many servers also process SIGHUP, and typically interpret as the signal from the superuser that they should reread their configuration files. This allows us to change settings without having to kill and restart these servers.
 
2 months ago
User avatar None

String updated in the repository

Documentation / books/developers-handbook/sockets/_index — Portuguese

For that reason, the _daemon process_ needs to set _signal handlers_ in its _initialize daemon_ phase. At least a SIGCHLD signal has to be processed, so the daemon can remove the zombie return values from the system and release the system resources they are taking up.
 
2 months ago
User avatar None

String updated in the repository

Documentation / books/developers-handbook/sockets/_index — Portuguese

Under UNIX(R), a process does not really _exit_. Instead, it _returns_ to its parent. Typically, a parent process ``wait``s for its child process, and obtains a return value. However, our _daemon process_ cannot simply stop and wait. That would defeat the whole purpose of creating additional processes. But if it never does `wait`, its children will become _zombies_-no longer functional but still roaming around.
 
2 months ago
User avatar None

String updated in the repository

Documentation / books/developers-handbook/sockets/_index — Portuguese

After the _server process_ is done serving, it should close the _accepted socket_. Instead of returning to `accept`, it now exits.
 
2 months ago
User avatar None

String updated in the repository

Documentation / books/developers-handbook/sockets/_index — Portuguese

However, the _server process_ does not need this socket and should `close` it immediately. Similarly, the _daemon process_ no longer needs the _accepted socket_, and not only should, but _must_ `close` it-otherwise, it will run out of available _file descriptors_ sooner or later.
 
2 months ago
User avatar None

String updated in the repository

Documentation / books/developers-handbook/sockets/_index — Portuguese

We moved the _serve_ from the _daemon process_ to its own _server process_. However, because each child process inherits all open files (and a socket is treated just like a file), the new process inherits not only the _"accepted handle,"_ i.e., the socket returned by the `accept` call, but also the _top socket_, i.e., the one opened by the top process right at the beginning.
 
2 months ago
User avatar None

String updated in the repository

Documentation / books/developers-handbook/sockets/_index — Portuguese

serv2.png
 
2 months ago
Browse all component changes