Re^4: Why can't some of my modules do log output to a file?

Instead of closing the file handle, you could just release the lock. flock $fh, LOCK_UN or die "flock can't release lock $!";

Note from the docs: "To avoid the possibility of miscoordination, Perl now flushes FILEHANDLE before locking or unlocking it."
So, lock, write, unlock will cause 2 flushes. There is no need to explicitly seek or flush.

Comment on Re^4: Why can't some of my modules do log output to a file? Download Code

Replies are listed 'Best First'.
Re^5: Why can't some of my modules do log output to a file? by haukex (Archbishop) on Oct 11, 2022 at 06:20 UTC
Instead of closing the file handle, you could just release the lock. That's what LanX and I both said. So, lock, write, unlock will cause 2 flushes. That's why I wrote "lock-seek-write-flush-unlock" and not "flock-seek-print-flock", because I was referring to the underlying operations. There is no need to explicitly seek That is very wrong unless you know for sure that `O_APPEND` semantics are guaranteed. For example, if the file was opened with `'+<'` instead of `>>` or on NFS filesystems, you definitely need the seek or you will corrupt your data.	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^5: Why can't some of my modules do log output to a file?
by haukex (Archbishop) on Oct 11, 2022 at 06:20 UTC

Instead of closing the file handle, you could just release the lock.

That's what LanX and I both said.

So, lock, write, unlock will cause 2 flushes.

That's why I wrote "lock-seek-write-flush-unlock" and not "flock-seek-print-flock", because I was referring to the underlying operations.

There is no need to explicitly seek

That is very wrong unless you know for sure that O_APPEND semantics are guaranteed. For example, if the file was opened with '+<' instead of >> or on NFS filesystems, you definitely need the seek or you will corrupt your data.

[reply]
[d/l]
[select]