Wietse Venema wrote:
Please file a ZFS bug reportug. As per POSIX, when the O_CREAT is
specified to open(),
The third argument does not affect whether the file is open
for reading, writing or for both.
In other words, read/write access is controlled with the O_RDWR flags,
not
On Fri, 18 Feb 2011, Wietse Venema wrote:
Please file a ZFS bug reportug. As per POSIX, when the O_CREAT is
specified to open(),
The third argument does not affect whether the file is open
for reading, writing or for both.
In other words, read/write access is controlled with the
Matthias Andree:
On Fri, 18 Feb 2011, Wietse Venema wrote:
Please file a ZFS bug reportug. As per POSIX, when the O_CREAT is
specified to open(),
The third argument does not affect whether the file is open
for reading, writing or for both.
In other words, read/write
: truncate before-queue filter speed-adjust log: Permission denied
Other than that, everything looks normal. There are no leftover files
in the spool area, and mail is delivered normally.
I took a liberty to let smtpd_proxy.c log a path of the log stream,
added a printout of the path just after a file
[3620]:
warning: truncate before-queue filter speed-adjust log: Permission denied
Other than that, everything looks normal. There are no leftover files
in the spool area, and mail is delivered normally.
I took a liberty to let smtpd_proxy.c log a path of the log stream,
added a printout
Wietse Venema wrote:
Please file a ZFS bug reportug. As per POSIX, when the O_CREAT is
specified to open(),
The third argument does not affect whether the file is open
for reading, writing or for both.
In other words, read/write access is controlled with the O_RDWR flags,
not the
