Your message dated Sat, 16 Aug 2025 13:17:23 +0100
with message-id 
<caj3buoqg3rfqulznkhv+jhtp54d1lj4aok_uzaqncd9cujf...@mail.gmail.com>
and subject line Re: RFE: logtail locking
has caused the Debian Bug report #383289,
regarding RFE: logtail locking
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
383289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=383289
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: logtail
Version: 1.2.47

It would be good if logtail supports locking.

I can't add locking in the script that parses the output from logtail, because 
that would be too late.

Thanks!

--------------------------------------------------------------------------
Get a spam free email account - Visit http://www.bluebottle.com



--- End Message ---
--- Begin Message ---
On Sun, 12 May 2024 16:42:31 +0100 Richard Lewis
<[email protected]> wrote:
> On Wed, 16 Aug 2006 05:33:26 -0500 bingo <[email protected]> wrote:
>
> > It would be good if logtail supports locking.
>
> I think we need some more information if this bug is to be action-ed.
> logcheck uses logtail2 now (and syslog is not the default):so perhaps
> it is not relevant after nearly 20 years (there were other replies
> requesting patches in the intervening period, and no-one has provided
> them -- so perhaps we should just close this as no longer relevant).
>
> If the issue is that rsyslog might still be writing to the file, when
> logtail runs, surely all that might happen is that the same entries
> might be re-checked on the next run?
> (and I dont think it would be sensible for logtail to try and stop
> rsyslog writing while logtail runs)


A year later: closing as it's not clear what the benefit of "locking"
would be. I suspect most computers are sufficiently faster that this
isnt needed any more. But If there is a use for this, please re-open,
(Nb that logcheck itself does use a form of "logcking" to avoid itself
running twice)

--- End Message ---

Reply via email to