All active links contained in this email were disabled. Please verify the identity of the sender, and confirm the authenticity of all links contained within the message prior to copying and pasting the address to a Web browser.
Hi,
As Laci pointed out, this is an expected behavior.
Named pipes are not regular files, the "file size" is always 0 byte.
From Caution-https://linux.die.net/man/4/fifo < Caution-https://linux.die.net/man/4/fifo > :
When processes are exchanging data via the FIFO, the kernel passes all data internally without writing it to the file system.
If you are interested in the capacity of named pipes, you can read about this here:
Caution-https://linux.die.net/man/7/pipe < Caution-https://linux.die.net/man/7/pipe > (Chapter name: Pipe capacity)
--
László Várady
On Fri, Oct 27, 2017 at 4:56 PM Amin, Jitesh CTR (US) <jitesh.amin.ctr@mail.mil < Caution-mailto:jitesh.amin.ctr@mail.mil > > wrote:
Hi Laci,
So we can create named pipe object with filename successfully.
But the then the file always shows 0 bytes in size even after data is being written to this file. Additionally the timestamp on this file never changes (as new data get's written and so I would assume that modify date on file would also be updated).
Thanks
Jitesh
From: syslog-ng [syslog-ng-bounces@lists.balabit.hu < Caution-mailto:syslog-ng-bounces@lists.balabit.hu > ] on behalf of Szemere, László [laszlo.szemere@balabit.com < Caution-mailto:laszlo.szemere@balabit.com > ]
Sent: Friday, October 27, 2017 9:46 AM
To: Syslog-ng users' and developers' mailing list
Subject: [Non-DoD Source] Re: [syslog-ng] Syslog 3.5 (pipe file issue)
All active links contained in this email were disabled. Please verify the identity of the sender, and confirm the authenticity of all links contained within the message prior to copying and pasting the address to a Web browser.
Hello Jitesh,
I am afraid I can not clearly understand your problem. Since OSE 3.0.2, a named pipe destination creates a new pipe object automatically with the predefined filename. (Caution-Caution-https://www.balabit.com/documents/syslog-ng-ose-3.11-guides/en/syslog-ng-ose-guide-admin/html-single/index.html#configuring-destinations-pipe < Caution-https://www.balabit.com/documents/syslog-ng-ose-3.11-guides/en/syslog-ng-ose-guide-admin/html-single/index.html#configuring-destinations-pipe > < Caution-Caution-https://www.balabit.com/documents/syslog-ng-ose-3.11-guides/en/syslog-ng-ose-guide-admin/html-single/index.html#configuring-destinations-pipe < Caution-https://www.balabit.com/documents/syslog-ng-ose-3.11-guides/en/syslog-ng-ose-guide-admin/html-single/index.html#configuring-destinations-pipe > > )
For me, this is the expected behavior of named pipes (man page: Caution-Caution-http://man7.org/linux/man-pages/man1/mkfifo.1.html < Caution-http://man7.org/linux/man-pages/man1/mkfifo.1.html > < Caution-Caution-http://man7.org/linux/man-pages/man1/mkfifo.1.html < Caution-http://man7.org/linux/man-pages/man1/mkfifo.1.html > >
further information on level 3: Caution-Caution-http://man7.org/linux/man-pages/man3/mkfifo.3.html < Caution-http://man7.org/linux/man-pages/man3/mkfifo.3.html > < Caution-Caution-http://man7.org/linux/man-pages/man3/mkfifo.3.html < Caution-http://man7.org/linux/man-pages/man3/mkfifo.3.html > > ).
Please try to rephrase your question, to give us more understanding about your use case.
Br,
Laci
______________________________________________________________________________
Member info: Caution-https://lists.balabit.hu/mailman/listinfo/syslog-ng < Caution-https://lists.balabit.hu/mailman/listinfo/syslog-ng >
Documentation: Caution-http://www.balabit.com/support/documentation/?product=syslog-ng < Caution-http://www.balabit.com/support/documentation/?product=syslog-ng >
FAQ: Caution-http://www.balabit.com/wiki/syslog-ng-faq < Caution-http://www.balabit.com/wiki/syslog-ng-faq >