diff options
Diffstat (limited to 'po/de/man2/read.2.po')
| -rw-r--r-- | po/de/man2/read.2.po | 96 |
1 files changed, 76 insertions, 20 deletions
diff --git a/po/de/man2/read.2.po b/po/de/man2/read.2.po index ea5cdc32..c9da3b1e 100644 --- a/po/de/man2/read.2.po +++ b/po/de/man2/read.2.po @@ -7,9 +7,9 @@ # Helge Kreutzmann <debian@helgefjell.de>, 2012, 2014, 2016-2018. msgid "" msgstr "" -"Project-Id-Version: manpages-de\n" -"POT-Creation-Date: 2024-03-01 17:05+0100\n" -"PO-Revision-Date: 2023-01-12 20:16+0100\n" +"Project-Id-Version: manpages-l10n 4.22\n" +"POT-Creation-Date: 2024-06-01 06:14+0200\n" +"PO-Revision-Date: 2024-03-29 17:41+0100\n" "Last-Translator: Mario Blättermann <mario.blaettermann@gmail.com>\n" "Language-Team: German <debian-l10n-german@lists.debian.org>\n" "Language: de\n" @@ -27,16 +27,16 @@ msgid "read" msgstr "read" #. type: TH -#: archlinux fedora-40 fedora-rawhide mageia-cauldron +#: archlinux debian-unstable opensuse-tumbleweed #, no-wrap -msgid "2023-10-31" -msgstr "31. Oktober 2023" +msgid "2024-05-02" +msgstr "2. Mai 2024" #. type: TH -#: archlinux fedora-40 fedora-rawhide mageia-cauldron +#: archlinux debian-unstable #, no-wrap -msgid "Linux man-pages 6.06" -msgstr "Linux man-pages 6.06" +msgid "Linux man-pages 6.8" +msgstr "Linux man-pages 6.8" #. type: SH #: archlinux debian-bookworm debian-unstable fedora-40 fedora-rawhide @@ -469,17 +469,17 @@ msgstr "" #. Date: Mon Mar 3 09:36:58 2014 -0800 #. vfs: atomic f_pos accesses as per POSIX #. type: Plain text -#: archlinux debian-bookworm debian-unstable fedora-40 fedora-rawhide -#: mageia-cauldron opensuse-leap-15-6 opensuse-tumbleweed +#: archlinux debian-unstable fedora-rawhide opensuse-tumbleweed msgid "" "Among the APIs subsequently listed are B<read>() and B<readv>(2). And " "among the effects that should be atomic across threads (and processes) are " "updates of the file offset. However, before Linux 3.14, this was not the " "case: if two processes that share an open file description (see B<open>(2)) " "perform a B<read>() (or B<readv>(2)) at the same time, then the I/O " -"operations were not atomic with respect updating the file offset, with the " -"result that the reads in the two processes might (incorrectly) overlap in " -"the blocks of data that they obtained. This problem was fixed in Linux 3.14." +"operations were not atomic with respect to updating the file offset, with " +"the result that the reads in the two processes might (incorrectly) overlap " +"in the blocks of data that they obtained. This problem was fixed in Linux " +"3.14." msgstr "" "Unter den im Folgenden aufgeführten APIs sind B<read>() und B<readv>(2). Und " "unter den Effekten, die über Threads (und Prozesse) hinweg atomar sein " @@ -532,20 +532,76 @@ msgstr "" "Die Typen I<size_t> und I<ssize_t> sind, respektive, vorzeichenlose und " "vorzeichenbehaftete Ganzzahldatentypen, wie durch POSIX.1 spezifiziert." +#. http://thread.gmane.org/gmane.linux.kernel/1649458 +#. From: Michael Kerrisk (man-pages <mtk.manpages <at> gmail.com> +#. Subject: Update of file offset on write() etc. is non-atomic with I/O +#. Date: 2014-02-17 15:41:37 GMT +#. Newsgroups: gmane.linux.kernel, gmane.linux.file-systems +#. commit 9c225f2655e36a470c4f58dbbc99244c5fc7f2d4 +#. Author: Linus Torvalds <torvalds@linux-foundation.org> +#. Date: Mon Mar 3 09:36:58 2014 -0800 +#. vfs: atomic f_pos accesses as per POSIX +#. type: Plain text +#: debian-bookworm fedora-40 mageia-cauldron opensuse-leap-15-6 +msgid "" +"Among the APIs subsequently listed are B<read>() and B<readv>(2). And " +"among the effects that should be atomic across threads (and processes) are " +"updates of the file offset. However, before Linux 3.14, this was not the " +"case: if two processes that share an open file description (see B<open>(2)) " +"perform a B<read>() (or B<readv>(2)) at the same time, then the I/O " +"operations were not atomic with respect updating the file offset, with the " +"result that the reads in the two processes might (incorrectly) overlap in " +"the blocks of data that they obtained. This problem was fixed in Linux 3.14." +msgstr "" +"Unter den im Folgenden aufgeführten APIs sind B<read>() und B<readv>(2). Und " +"unter den Effekten, die über Threads (und Prozesse) hinweg atomar sein " +"sollten, ist die Aktualisierung des Dateiversatzes. Unter Linux vor Version " +"3.14 war das allerdings nicht der Fall: Falls zwei Prozesse, die eine offene " +"Dateideskription gemeinsam nutzten (siehe B<open>(2)) gleichzeitig einen " +"B<read>() (oder B<readv>(2)) durchführten, waren die E/A-Aktionen im " +"Hinblick auf die Aktualisierung des Dateiversatzes nicht atomar. Das " +"Ergebnis war, dass beim Lesen erhaltene Datenblöcken in den zwei Prozessen " +"sich (inkorrekterweise) überlappten. Dieses Problem wurde in Linux 3.14 " +"behoben." + #. type: TH -#: debian-unstable opensuse-leap-15-6 opensuse-tumbleweed +#: fedora-40 mageia-cauldron #, no-wrap -msgid "2023-04-03" -msgstr "3. April 2023" +msgid "2023-10-31" +msgstr "31. Oktober 2023" + +#. type: TH +#: fedora-40 mageia-cauldron +#, no-wrap +msgid "Linux man-pages 6.06" +msgstr "Linux man-pages 6.06" + +#. type: TH +#: fedora-rawhide +#, no-wrap +msgid "2024-03-12" +msgstr "12. März 2024" #. type: TH -#: debian-unstable opensuse-tumbleweed +#: fedora-rawhide #, no-wrap -msgid "Linux man-pages 6.05.01" -msgstr "Linux man-pages 6.05.01" +msgid "Linux man-pages 6.7" +msgstr "Linux man-pages 6.7" + +#. type: TH +#: opensuse-leap-15-6 +#, no-wrap +msgid "2023-04-03" +msgstr "3. April 2023" #. type: TH #: opensuse-leap-15-6 #, no-wrap msgid "Linux man-pages 6.04" msgstr "Linux-Handbuchseiten 6.04" + +#. type: TH +#: opensuse-tumbleweed +#, no-wrap +msgid "Linux man-pages (unreleased)" +msgstr "Linux man-pages (unveröffentlicht)" |