mirror of
https://github.com/Dasharo/systemd.git
synced 2026-03-06 15:02:31 -08:00
tree-wide: use normal spelling of "reopen"
It's a commonly used verb meaning "to open again".
This commit is contained in:
@@ -352,10 +352,10 @@
|
||||
|
||||
<para>When this option is used the original file descriptors <command>systemd-run</command> receives are passed
|
||||
to the service processes as-is. If the service runs with different privileges than
|
||||
<command>systemd-run</command>, this means the service might not be able to re-open the passed file
|
||||
<command>systemd-run</command>, this means the service might not be able to reopen the passed file
|
||||
descriptors, due to normal file descriptor access restrictions. If the invoked process is a shell script that
|
||||
uses the <command>echo "hello" >/dev/stderr</command> construct for writing messages to stderr, this might
|
||||
cause problems, as this only works if stderr can be re-opened. To mitigate this use the construct <command>echo
|
||||
cause problems, as this only works if stderr can be reopened. To mitigate this use the construct <command>echo
|
||||
"hello" >&2</command> instead, which is mostly equivalent and avoids this pitfall.</para>
|
||||
|
||||
<xi:include href="version-info.xml" xpointer="v235"/></listitem>
|
||||
|
||||
@@ -3017,7 +3017,7 @@ SystemCallErrorNumber=EPERM</programlisting>
|
||||
the kernel log buffer, the unit will implicitly gain a dependency of type <varname>After=</varname>
|
||||
on <filename>systemd-journald.socket</filename> (also see the "Implicit Dependencies" section
|
||||
above). Also note that in this case stdout (or stderr, see below) will be an
|
||||
<constant>AF_UNIX</constant> stream socket, and not a pipe or FIFO that can be re-opened. This means
|
||||
<constant>AF_UNIX</constant> stream socket, and not a pipe or FIFO that can be reopened. This means
|
||||
when executing shell scripts the construct <command>echo "hello" > /dev/stderr</command> for
|
||||
writing text to stderr will not work. To mitigate this use the construct <command>echo "hello"
|
||||
>&2</command> instead, which is mostly equivalent and avoids this pitfall.</para>
|
||||
|
||||
@@ -303,7 +303,7 @@ EFI_STATUS chunked_read(EFI_FILE *file, size_t *size, void *buf) {
|
||||
* Some broken firmwares cannot handle large file reads and will instead return
|
||||
* an error. As a workaround, read such files in small chunks.
|
||||
* Note that we cannot just try reading the whole file first on such firmware as
|
||||
* that will permanently break the handle even if it is re-opened.
|
||||
* that will permanently break the handle even if it is reopened.
|
||||
*
|
||||
* https://github.com/systemd/systemd/issues/25911 */
|
||||
|
||||
|
||||
@@ -502,7 +502,7 @@ static void test_sequence_numbers_one(void) {
|
||||
test_close(one);
|
||||
|
||||
/* If the machine-id is not initialized, the header file verification
|
||||
* (which happens when re-opening a journal file) will fail. */
|
||||
* (which happens when reopening a journal file) will fail. */
|
||||
if (sd_id128_get_machine(NULL) >= 0) {
|
||||
/* restart server */
|
||||
seqnum = 0;
|
||||
|
||||
@@ -270,7 +270,7 @@ int inhibitor_load(Inhibitor *i) {
|
||||
if (i->fifo_path) {
|
||||
_cleanup_close_ int fd = -EBADF;
|
||||
|
||||
/* Let's re-open the FIFO on both sides, and close the writing side right away */
|
||||
/* Let's reopen the FIFO on both sides, and close the writing side right away */
|
||||
fd = inhibitor_create_fifo(i);
|
||||
if (fd < 0)
|
||||
return log_error_errno(fd, "Failed to reopen FIFO: %m");
|
||||
|
||||
@@ -695,7 +695,7 @@ int pty_forward_new(
|
||||
else {
|
||||
/* If we shall be invoked in interactive mode, let's switch on non-blocking mode, so that we
|
||||
* never end up staving one direction while we block on the other. However, let's be careful
|
||||
* here and not turn on O_NONBLOCK for stdin/stdout directly, but of re-opened copies of
|
||||
* here and not turn on O_NONBLOCK for stdin/stdout directly, but of reopened copies of
|
||||
* them. This has two advantages: when we are killed abruptly the stdin/stdout fds won't be
|
||||
* left in O_NONBLOCK state for the next process using them. In addition, if some process
|
||||
* running in the background wants to continue writing to our stdout it can do so without
|
||||
|
||||
@@ -1580,7 +1580,7 @@ static int fd_set_attribute(
|
||||
|
||||
procfs_fd = fd_reopen(fd, O_RDONLY|O_CLOEXEC|O_NOATIME);
|
||||
if (procfs_fd < 0)
|
||||
return log_error_errno(procfs_fd, "Failed to re-open '%s': %m", path);
|
||||
return log_error_errno(procfs_fd, "Failed to reopen '%s': %m", path);
|
||||
|
||||
unsigned previous, current;
|
||||
r = chattr_full(procfs_fd, NULL, f, item->attribute_mask, &previous, ¤t, CHATTR_FALLBACK_BITWISE);
|
||||
@@ -1732,7 +1732,7 @@ static int create_file(
|
||||
* fd_set_perms() report the error if the perms need to be modified. */
|
||||
fd = openat(dir_fd, bn, O_NOFOLLOW|O_CLOEXEC|O_PATH, i->mode);
|
||||
if (fd < 0)
|
||||
return log_error_errno(errno, "Failed to re-open file %s: %m", path);
|
||||
return log_error_errno(errno, "Failed to reopen file %s: %m", path);
|
||||
|
||||
if (fstat(fd, &stbuf) < 0)
|
||||
return log_error_errno(errno, "stat(%s) failed: %m", path);
|
||||
@@ -1815,7 +1815,7 @@ static int truncate_file(
|
||||
"Cannot create file %s on a read-only file system.",
|
||||
path);
|
||||
|
||||
return log_error_errno(errno, "Failed to re-open file %s: %m", path);
|
||||
return log_error_errno(errno, "Failed to reopen file %s: %m", path);
|
||||
}
|
||||
|
||||
erofs = true;
|
||||
|
||||
Reference in New Issue
Block a user