Skip to content

Pipe fifo file removal #121

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Feb 19, 2025
Merged

Pipe fifo file removal #121

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
155ab67
Added note about required restart when making a new fifo file.
zsoltgyulai94 Aug 22, 2024
680d6fa
Modified note wording.
zsoltgyulai94 Aug 22, 2024
ec239a1
Update doc/_admin-guide/060_Sources/110_Pipe/README.md
zsoltgyulai94 Aug 26, 2024
86ea2f6
Update doc/_admin-guide/060_Sources/110_Pipe/README.md
zsoltgyulai94 Oct 10, 2024
8617fc1
Merge branch 'master' into doc-pipe-fifo
zsoltgyulai94 Feb 19, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions doc/_admin-guide/060_Sources/110_Pipe/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,6 +28,9 @@ differences, for example, pipe() opens its argument in read-write mode,
therefore it is not recommended to be used on special files like
/proc/kmsg.

**NOTE:** If the `fifo` file is deleted, syslog-ng OSE automatically recreates it. When a new `pipe()` is created, syslog-ng OSE continues to use the old file until the system is restarted.
Copy link
Contributor

@kovgeri01 kovgeri01 Aug 22, 2024 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry my wording was a little bit confusing in the issue. I tried to describe the following scenario, but it was unclear. The process flows like this:

  • The file is deleted.
  • Then someone recreates the file (syslog-ng will not automatically recreate it).
  • After the file is recreated syslog-ng will not read it even if there are no remaining writer on the old FIFO syslog-ng will still try to read the old one regardless until restart

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for clarifying, I modified the note. Hopefully it's correct now.

{: .notice--info}

>![]({{ site.baseurl}}/assets/images/caution.png) **CAUTION:**
>
>- It is not recommended to use pipe() on anything else than real pipes.
Expand Down